| Author |
Message
|
| Dio |
 Posted: Wed Jan 18, 2006 1:54 am Post subject: Custom node using XML parsers problem (WMB CSD5 and higher) |
 |
|
Novice
Joined: 18 Jan 2006
Posts: 11
Location: Moscow, Russia
|
I've got several custom nodes written in Java that works fine on different mashines under message broker 5 with CSD4 or CSD3 installed. When I try to use it on MB with CSD5 or CSD6 each execution group (even if there is no message flow using this custom node) throws error message into system event log
| Code: |
Event Type: Error
Event Source: BIPv500
Event Category: None
Event ID: 4371
Date: 29.12.2005
Time: 14:34:57
User: N/A
Computer: KS14A
Description:
( MBROKER3.EPW ) Failure to locate Java class ru.xxx.wbimb.plugin.nodes.docnode.DocXMLCorrelIDNode
The Java class ru.xxx.wbimb.plugin.nodes.docnode.DocXMLCorrelIDNode could not be found by the Java API framework.
This is an internal error. Contact your IBM support center.
Data:
0000: 35 00 36 00 35 00 32 00 5.6.5.2.
0008: 00 00 4d 00 42 00 52 00 ..M.B.R.
0010: 4f 00 4b 00 45 00 52 00 O.K.E.R.
0018: 33 00 2e 00 31 00 63 00 3...1.c.
0020: 32 00 37 00 63 00 62 00 2.7.c.b.
0028: 37 00 35 00 2d 00 30 00 7.5.-.0.
0030: 38 00 30 00 31 00 2d 00 8.0.1.-.
0038: 30 00 30 00 30 00 30 00 0.0.0.0.
0040: 2d 00 30 00 30 00 38 00 -.0.0.8.
0048: 30 00 2d 00 39 00 62 00 0.-.9.b.
0050: 64 00 30 00 62 00 34 00 d.0.b.4.
0058: 30 00 37 00 62 00 62 00 0.7.b.b.
0060: 65 00 30 00 00 00 63 00 e.0...c.
0068: 6f 00 6d 00 2e 00 69 00 o.m...i.
0070: 62 00 6d 00 2e 00 62 00 b.m...b.
0078: 72 00 6f 00 6b 00 65 00 r.o.k.e.
0080: 72 00 2e 00 70 00 6c 00 r...p.l.
0088: 75 00 67 00 69 00 6e 00 u.g.i.n.
0090: 2e 00 4d 00 62 00 4e 00 ..M.b.N.
0098: 6f 00 64 00 65 00 44 00 o.d.e.D.
00a0: 69 00 72 00 65 00 63 00 i.r.e.c.
00a8: 74 00 6f 00 72 00 00 00 t.o.r...
00b0: 30 00 00 00 72 00 65 00 0...r.e.
00b8: 67 00 69 00 73 00 74 00 g.i.s.t.
00c0: 65 00 72 00 41 00 6c 00 e.r.A.l.
00c8: 6c 00 4e 00 6f 00 64 00 l.N.o.d.
00d0: 65 00 73 00 00 00 00 00 e.s.....
00d8: 00 00 .. |
If I comment all usages of org.apache.xerces.*, org.w3c.doc.*, javax.xml.* classes errors disappear. If I try write the same code in standalone application using jars only from MB/classes directory there is not errors.
The only idea how to remove this problem is to take xerces, xalan source code, change package to my own and try to use it in my nodes instead of standart packages. But I don't like this way.
Any other ideas what to check or what to change? |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Wed Jan 18, 2006 2:11 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Dio,
It is difficult to believe that you tested this scenario with each CSD 
Anyway, since you say that it is working with CSD3 and 4 and not with 5 and 6, you could raise a PMR.
But before that, you could try importing the jars of all the parsers u mentioned into ur workspace....Since commenting the code is working, that means it is not able to reference the jars, so make sure they are.
Regards. |
|
| Back to top |
|
|
| Dio |
| Posted: Wed Jan 18, 2006 2:19 am Post subject: |
|
|
Novice
Joined: 18 Jan 2006
Posts: 11
Location: Moscow, Russia
|
| elvis_gn wrote: |
| It is difficult to believe that you tested this scenario with each CSD |
yes Mostly checks was made on CSD5. On CSD3-4 there is not errors so there's nothing to check.
| elvis_gn wrote: |
Anyway, since you say that it is working with CSD3 and 4 and not with 5 and 6, you could raise a PMR.
|
It's done but I can't wait for a long time.
| elvis_gn wrote: |
| But before that, you could try importing the jars of all the parsers u mentioned into ur workspace.... |
Hm, I wrote I did it (or I don't understand what exactly do you mean)
| elvis_gn wrote: |
Since commenting the code is working, that means it is not able to reference the jars, so make sure they are.
|
How? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 18, 2006 4:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Confirm that your jar file is accurately built and contains what you think it contains.
I would also suggest rebuilding the plugins completely in the newer CSD toolkit, and building your jar file using the command line rather than the Toolkit.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Dio |
| Posted: Wed Jan 18, 2006 4:51 am Post subject: |
|
|
Novice
Joined: 18 Jan 2006
Posts: 11
Location: Moscow, Russia
|
| jefflowrey wrote: |
Confirm that your jar file is accurately built and contains what you think it contains.
I would also suggest rebuilding the plugins completely in the newer CSD toolkit, and building your jar file using the command line rather than the Toolkit. |
My jar file contens only node classes, nothing more.
Jar file built with jar.exe from command line on the same mashine where broker is installed. I tried to make project from the begining on toolkit on the same mashine. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jan 18, 2006 6:20 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Try compiling your java node classes using the command line - you'll have to screw around with classpaths to make sure you include jplugin.jar and others - and see if the resulting files are different in size from the ones in your jar.
You're sure your jar file has the class files in the right paths?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Dio |
| Posted: Wed Jan 18, 2006 6:51 am Post subject: |
|
|
Novice
Joined: 18 Jan 2006
Posts: 11
Location: Moscow, Russia
|
| jefflowrey wrote: |
| You're sure your jar file has the class files in the right paths? |
Yes
remember, it's working fine on lower CSD |
|
| Back to top |
|
|
| Dio |
| Posted: Thu Jan 19, 2006 5:38 am Post subject: Re: Custom node using XML parsers problem (WMB CSD5 and high |
|
|
Novice
Joined: 18 Jan 2006
Posts: 11
Location: Moscow, Russia
|
I've found it! He-he, it's a bug
http://www-1.ibm.com/support/docview.wss?uid=swg1IY75122
| Quote: |
IY75122: BIP4371S CLASS NOT FOUND ERRORS AFTER UPGRADE TO FP5
APAR status
Closed as program error.
Error description
Plugins developeed before BP05 using the xalan.jar, brokerXerces
jar and xml-apis.jar files need to add them explicitly to the
classpath after applying FP05
Local fix
Add xalan.jar, xml-apis.jar and brokerXerces.jar to the
classpath if the plugin uses methods from these classes
Problem summary
****************************************************************
* USERS AFFECTED: All Users *
****************************************************************
* PROBLEM DESCRIPTION: BIP4371S error for java plugins after *
* upgrading to FP5. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
Any plugin that was developed before FP5 using the shipped
xalan.jar, brokerXerces.jar or xml-apis.jar works fine on
earlier FP levels but fails with the BIP4371S error upon FP5
installation.
Problem conclusion
The workaround for this is to include these jars in the
classpath after FP installation. In this APAR the broker JVM
Classpath is modified appropriately so that the classpath for
these need not be set explicitly.
Temporary fix
Comments
APAR information
APAR number IY75122
Reported component name WBI MB AIX
Reported component ID 5724E2600
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2005-08-10
Closed date 2005-08-30
Last modified date 2005-08-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Fix information
Fixed component name WBI MB AIX
Fixed component ID 5724E2600
Applicable component levels
R500 PSY UP |
|
|
| Back to top |
|
|
|
|
