| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issue with Java compute node |
« View previous topic :: View next topic » |
| Author |
Message
|
| neeha_kashyap120 |
 Posted: Mon Feb 20, 2012 1:26 pm Post subject: Issue with Java compute node |
 |
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
We are using following env
MQ - 7.0.1.3
WMB - 7.0
Windows 2003.
We applied a fix given by IBM for file nodes, which is a par file we need to copy to MQSI\bin folder. mqsifile.par
We have a flow which uses a Java compute node, which was working fine before the fix was applied. But after the fix was applied, the flow stopped running though it shows as running in toolkit, and I am unable to stop the flow. Recycling the broker did not help. Below is the error we are getting
-- (Broker.TestEG ) A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type ''ComIbmJavaComputeNode'' in message flow 'Testflow'.
The broker received an instruction to create a message flow node of type ''ComIbmJavaComputeNode'', in message flow 'Testflow'. The broker cannot create nodes of this type because an implementation library for this node type does not exist in the LIL path.
Ensure that the LIL path is correct, and that it contains all the required node implementation libraries, including those supplied by IBM. The node name is case sensitive, therefore check that the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode', ensure that when the node was registered with the toolkit the name registered did not end in 'Node'.
Also ensure that you have saved the message flow, and any nested message flows. Redeploy the new configuration to the broker, specifying a complete configuration. If the LIL file is correct, check that the message node type is correct.
-- (Broker.TestEG ) Error loading message flow ''b46d6983-2e01-0000-0080-8facd9bc376c''.
The broker's internal record for the message flow with internal ID ''b46d6983-2e01-0000-0080-8facd9bc376c'' is not valid. The active broker state might not be as expected.
See the subsequent message or messages for further details of the error. Restart the broker in a refreshed mqsiprofile environment. If you can identify the failing message flow from the subsequent messages, redeploy the message flow. If the problem persists, contact your IBM Support Center for assistance.
-- ( Broker.TestEG ) Resource name ''ComIbmFileStatsManager'' for use in library ''ComIbmFileStatsManager'': name already registered in library ''ComIbmFileStatsManager''.
The message broker detected the resource in loadable implementation library ''ComIbmFileStatsManager'' attempting to register the resource name ''ComIbmFileStatsManager'', but this name has already been registered with the broker by the resource in the library ''ComIbmFileStatsManager''.
[/img]
Please help me troubleshoot this issue
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 20, 2012 1:36 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| If you got an APAR and it caused further problems, you need to report this to the PMR team, they will fix the APAR. |
|
| Back to top |
|
|
| neeha_kashyap120 |
| Posted: Mon Feb 20, 2012 1:48 pm Post subject: |
|
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
We did raise a PMR. This is what they said
Websphere Message Broker Level 2 Defect Support has received your PMR regarding the errors you are seeing after applying the fix mentioned in your update.
Looking at the fix, I do not see anything in the fix that would cause the error you are seeing.
Since the issue points to a missing lil file, could you verify that the lil files that are being used by the java compute node are present in the shared class directory?
=================================================
Since the flow was working in QA, I checked all the lil files on both servers, QA and Prod and none of the files are missing. Can you tell me how to check the lil files being used by Java compute node?
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
|
| neeha_kashyap120 |
| Posted: Mon Feb 20, 2012 3:16 pm Post subject: |
|
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
Hi All
I resolved the issue, and I didnt know it mattered. When i applied the fix, I copied the backup of the .par file which was part of the fix in the same MQSI\bin folder, so when Broker tried to startup it was trying to load the backup file and failing. Once I moved the backed up file out of bin, worked like a charm
Thanks
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| 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
|
|
|
|
