| Author |
Message
|
| mvarghese |
 Posted: Wed Apr 22, 2009 8:59 am Post subject: Java Plugin Contains Msg flows: Deployment issues |
 |
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Apr 22 19:55:37 mp007e1 user:info WebSphere Broker v6103[864464]: (EEAX901I.Temp01)[7968]BIP4374S: An unexpected exception has occurred in the Java API framework. : EEAX901I.b80fefcc-2001-0000-0080-ab59979f6898: /build/S610_P/src/DataFlowEngine/PluginInterface/ImbJniNode.cpp: 472: ImbJniNode::setAttribute: :
Apr 22 19:55:44 mp007e1 user:info WebSphere Broker v6103[864464]: (EEAX901I.Temp01)[1]BIP2204I: Execution group using process '864464' thread '1' stopped. : EEAX901I.b80fefcc-2001-0000-0080-ab59979f6898: /build/S610_P/src/DataFlowEngine/ImbMain.cpp: 1102: ImbMain::start: :
Any one come across similar issue, help!!!
So unable to deploy this message flow. Above exception written in syslog Broker 6.1 on AIX
_________________
Jain Varghese |
|
| Back to top |
|
 |
| WMBDEV1 |
| Posted: Wed Apr 22, 2009 9:02 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Do you get any abends created?
Some clues for us to work with?
Are you sure this occurs when you deploy the flow as you seemed to suggest? |
|
| Back to top |
|
|
| mvarghese |
| Posted: Wed Apr 22, 2009 9:11 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
yes:
2009-04-22 16:21:50.444334 Execution group started. UUID is: 'fb3b2ccc-2001-0000-0080-ab59979f6898'. Broker is: EEAX901I
ftok OS JNI: A file or directory in the path name does not exist.
Exception in thread "Thread-10" java.lang.NoClassDefFoundError: org.apache.xml.security.signature.XMLSignatureException
at java.lang.Class.getDeclaredMethodsImpl(Native Method)
at java.lang.Class.getDeclaredMethods(Class.java:664)
at java.beans.Introspector$1.run(Introspector.java:1294)
at java.security.AccessController.doPrivileged(AccessController.java:197)
at java.beans.Introspector.getPublicDeclaredMethods(Introspector.java:1292)
at java.beans.Introspector.getTargetMethodInfo(Introspector.java:1158)
at java.beans.Introspector.getBeanInfo(Introspector.java:416)
at java.beans.Introspector.getBeanInfo(Introspector.java:188)
at com.ibm.broker.plugin.MbNode.getWriteMethod(MbNode.java:797)
***********************
Location:/var/mqsi/components/EEAX901I/fb3b2ccc-2001-0000-0080-ab59979f6898
***lil path setting
$ more LilPath
/opt/IBM/mqsi/6.1/lil:/opt/IBM/mqsi/6.1/lil32:/opt/IBM/mqsi/6.1/jplugin
$ pwd
/var/mqsi/registry/EEAX901I/CurrentVersion
_________________
Jain Varghese |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 22, 2009 10:55 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Did you deploy the plugin first, before trying to deploy the flow that uses it? |
|
| Back to top |
|
|
| vairavan |
| Posted: Wed Apr 22, 2009 4:18 pm Post subject: |
|
|
Apprentice
Joined: 22 Apr 2008
Posts: 42
|
Once you put all your plugins...
Step1: Stop the Broker.
Step2: Delete all the files from /var/mqsi/components/EEAX901I/fb3b2ccc-2001-0000-0080-ab59979f6898
Step3: Place all the jar files which are required for your message flow in /var/mqsi/shared-classes folder.
Step4: Now start the broker.
Step5: Deploy the bar file.
Now you should not get any problems while deploying... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Apr 22, 2009 6:09 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| vairavan wrote: |
| Step2: Delete all the files from /var/mqsi/components/EEAX901I/fb3b2ccc-2001-0000-0080-ab59979f6898 |
No.
Do not do this. Even if your Broker is named EEAX901I and has that UUID.
And only put things in shared-classes if that is the correct location for them, such that they are supposed to be loaded by the shared classloader.
Ideally your Java user defined plugins are packaged as PAR files and deployed to a custom LIL directory that you have added to the lil path with mqsichangebroker. |
|
| Back to top |
|
|
| mvarghese |
| Posted: Thu Apr 23, 2009 12:12 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Tried all the options mentioned above, till the condition looks same.
Any alternative.
_________________
Jain Varghese |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Apr 23, 2009 12:37 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
Is the jar file that contains the missing class accessible to the broker (be it in the shared classes or execution group)?
Please confirm this for me and tell me the name of the jar and where it is to be found. |
|
| Back to top |
|
|
| mvarghese |
| Posted: Thu Apr 23, 2009 12:55 am Post subject: |
|
|
Centurion
Joined: 27 Sep 2006
Posts: 141
|
Apr 23 11:49:02 mp007e1 user:err|error WebSphere Broker v6103[1069160]: (EEAX901I.Temp01)[7968]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '7968'. : EEAX901I.b80fefcc-2001-0000-0080-ab59979f6898: /build/S610_P/src/CommonServices/rios_aix_4/ImbOsThread.cpp: 252: ImbOsThread::threadBootStrap: :
Apr 23 11:49:02 mp007e1 user:info WebSphere Broker v6103[1069160]: (EEAX901I.Temp01)[7968]BIP4374S: An unexpected exception has occurred in the Java API framework. : EEAX901I.b80fefcc-2001-0000-0080-ab59979f6898: /build/S610_P/src/DataFlowEngine/PluginInterface/ImbJniNode.cpp: 472: ImbJniNode::setAttribute: :
*****************************
It works fine in production Env ( MB5), we are trying to deploy in new Integration Mb6.1.
_________________
Jain Varghese |
|
| Back to top |
|
|
|
|
