| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FileInput Node issue - java.lang.NoClassDefFoundError: com.i |
« View previous topic :: View next topic » |
| Author |
Message
|
| mqxplorer |
 Posted: Wed Jan 30, 2013 8:42 am Post subject: FileInput Node issue - java.lang.NoClassDefFoundError: com.i |
 |
|
Master
Joined: 22 Jun 2009
Posts: 206
|
Hi All,
We are getting the following exception for a flow with FileInput node.
| Code: |
2013-01-30 10:40:52.526392 113 Error BIP2628E: Exception condition detected on input node 'MF_StdntEnrollUpdActiveDate.File Input'.
The input node 'MF_StdntEnrollUpdActiveDate.File Input' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2013-01-30 10:40:52.527928 113 RecoverableException BIP4367E: The method ''readData'' in Java node ''File Input'' has thrown the following exception: 'java.lang.NoClassDefFoundError: com.ibm.broker.remote.RemoteFactory (initialization failure)'.
The method ''readData'' of the Java node has thrown an exception. Examine previous error messages for details of the cause of the problem.
This error is generated by the Java node API. It can occur in a Java Compute node or a Java user-defined node. If the node is a user-defined node, contact the node provider for further details.
2013-01-30 10:40:52.527948 113 RecoverableException BIP4395E: Java exception: ''java.lang.NoClassDefFoundError''; thrown from class name: ''java.lang.J9VMInternals'', method name: ''initialize'', file: ''J9VMInternals.java'', line: '140'
The message contains that data associated with a Java exception.
No user action required. |
We were not facing any issues with this flow till we recently applied the Fxipack 5. There is one more thing that is interesting.. we are getting this issue only in QA not in DEV and we tried applying this on one of the staging brokers to see if this is something to do with the FP and it turned out that we don't see this issue in Staging box where we applied the FP5. I guess, the FileInput node is not even trying to get the file from the directory where it is supposed to get it from. It keeps on filling our syslogs. Can anybody suggest a solution for this? Should we have to approach IBM or we can do something about this exception?
Thanks
mqxplorer |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jan 30, 2013 8:53 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
reapply the fix pack.
Then open a PMR. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
