| Author |
Message
|
| kmidderigh |
 Posted: Wed Dec 11, 2013 4:21 am Post subject: bar file deploys on broker A but fails on Broker B in IIBv9 |
 |
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
hi,
I'm having trouble deploying a bar file to an IIBv9 broker. I have two brokers which should be set up identically both on the same server.
Deploying to the first broker 50A is fine but when trying the deploy to 50B - to an EG of the same name i receive the following errors :
BIP4366E: Unable to create Java node 'com/fidintl/bs/activatefee/flows/SubRetrieveFeeSubscription#FCMComposite_1_2' of type 'ComIbmMSLMappingNode'.
An exception has occurred during the creation of the Java node: java.lang.NoClassDefFoundError: com.ibm.xml.xci.type.SchemaResolver
Contact the node provider for further details.
BIP4395E: Java exception: 'java.lang.NoClassDefFoundError'; thrown from class name: 'java.lang.J9VMInternals', method name: 'verifyImpl', file: 'J9VMInternals.java', line: '-2'
The message contains that data associated with a Java exception.
No user action required.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.
From the /var/mqsi/ logs :
Dec 11 09:54:22 ukx02123 user:err|error IIB[41091276]: IBM Integration Bus v9000 (WMBHUBD50B.RET_SERVICES_COMPOSITION) [Thread 6428] (Msg 2/3) BIP4366E: Unable to create Java node 'com/fidintl/bs/activatefee/flows/SubRetrieveFeeSubscription#FCMComposite_1_2' of type 'ComIbmMSLMappingNode'.
Dec 11 09:54:22 ukx02123 user:err|error IIB[41091276]: IBM Integration Bus v9000 (WMBHUBD50B.RET_SERVICES_COMPOSITION) [Thread 6428] (Msg 3/3) BIP4395E: Java exception: 'java.lang.NoClassDefFoundError'; thrown from class name: 'java.lang.J9VMInternals', method name: 'verifyImpl', file: 'J9VMInternals.java', line: '-2'
Dec 11 09:54:22 ukx02123 user:info IIB[41091276]: IBM Integration Bus v9000 (WMBHUBD50B.RET_SERVICES_COMPOSITION) [Thread 6428] (Msg 1/1) BIP2154I: Execution group finished with Configuration message.
I'm struggling to find a cause for this - what are the possible reasons ?
Thanks,
Kevin |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Dec 12, 2013 10:41 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you parsing or verifying an XML schema using standard xml parser (like Xerces?). Looks to me like this would be because of a missing implementation of this parser....
Why not use the broker provided facilities for this task?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Dec 12, 2013 11:21 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
|
| Back to top |
|
|
| stoney |
| Posted: Fri Dec 13, 2013 2:25 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2013
Posts: 140
|
As part of the deployment, you are deploying a V8+ mapping node and the mapping node cannot seem to find one of the classes it uses internally. Have you tried restarting the broker to see if that resolves the problem?
If these brokers are on the same server, are they using the same IIBv9 installation or do you have a separate installation for each broker? If they are using separate installations, then it's possible the installation for broker 50B has somehow been corrupted or is missing required files.
If they're using the same installation, then something odd is going on and it's worth raising a PMR so that IBM can investigate. |
|
| Back to top |
|
|
| kmidderigh |
| Posted: Fri Dec 13, 2013 6:05 am Post subject: solved... |
|
|
Apprentice
Joined: 21 Apr 2009
Posts: 26
|
Thanks for your replies - raised a PMR for this and the cause is simple when you now what it is ! ......we are using redirected temp file locations to prevent the broker filling up the default /tmp location.
on broker 50B that wasnt working the permissions on the alternative temp location were not quite correct and this was preventing the broker writing to this location and hence completing the deployment. Once the permissions were corrected it worked fine.
I would have liked to see a better error message for this issue as it would have made the resolution a lot quicker... |
|
| Back to top |
|
|
|
|
