|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
BIP2241E: After going to MQ 9.3 |
« View previous topic :: View next topic » |
Author |
Message
|
bdaoust |
Posted: Tue May 28, 2024 1:35 pm Post subject: BIP2241E: After going to MQ 9.3 |
|
|
Centurion
Joined: 23 Sep 2010 Posts: 130
|
Hi everyone.
I got pulled into an issue because on our broker server, the version of MQ was updated 9.3 but the toolkit wasn't changed. Now we are getting this error:
BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type 'ComIbmMQHeaderNode' in message flow
I haven't supported this flow in years, but word got out I had some toolkit knowledge and experience with this particular flow. Sure enough I imported the Project Interchange file and I do see the MQHeader node is used.
Isn't (or wasn't) the MQHeaderNode just a standard node ? I understand the error is saying that it can't be found and we should check or LIL path, but since the MQHeader node is a standard node, wouldn't I see similar errors for other nodes (like FileInput for instance) if the LIL path wasn't set properly after the upgrade of the MQ version. I'm not certain of the version of MQ they went to, but I do know that the toolkit I have is 9.0.0.1.
Our admin (who won't touch code) indicates he opened an IBM PMR, but they said they no longer support 9.0.0.1 since it very outdated. (Yes, our MQ team needs to update to ACE at some point)
I will say looking at logs, other flows that do not use the MQHeader node seem to be functioning as expected, so I'm really puzzled why just the MqHeader node is impacted. Did the 9.3 deprecate that version of the node or something?
Any advice getting this flow to work without updating the toolkit or rolling back the MQ version would be appreciate.
PS - I'm looking at the flow and the MQ Header node is just setting the MQMD messageID, correlationID and message format. I tried removing the MQHeader node and use a Compute node to write some ESQL to set those three properties, but that didn't seem to work.
Thanks,
Brian |
|
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
|
|
|
|