| Author |
Message
|
| pvsp |
 Posted: Tue Sep 03, 2013 3:50 am Post subject: Integration Bus v9: not found for message flow node type 'Co |
 |
|
Apprentice
Joined: 17 Feb 2008
Posts: 36
Location: Warsaw, PL
|
Hi,
I have installed Integration Bus v9 on:
[root@iibdev141 lil]# lsb_release -a
LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch
Distributor ID: CentOS
Description: CentOS release 5.9 (Final)
Release: 5.9
Codename: Final
After that, I have created simple flow that uses MQ Header Node and I got error like below:
BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type 'ComIbmMQHeaderNode' in message flow 'test.Flow2'.
The broker received an instruction to create a message flow node of type 'ComIbmMQHeaderNode', in message flow 'test.Flow2'. 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.
I checked lil path and it is set:
MQSI_LILPATH=/opt/ibm/mqsi/9.0.0.0/lil:/opt/ibm/mqsi/9.0.0.0/jplugin |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Sep 03, 2013 4:04 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
This may be caused by the fact that toolkit no longer in-lines resources. You should be building your bar from a script, not deploying the bar (or flows) directly from toolkit.
Use Ant or similar to script your mqsipackagebar command. Be sure to select the compile and in-line resources option in Prepare > Build Options with the appropriate command-line switch.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| pvsp |
| Posted: Tue Sep 03, 2013 4:34 am Post subject: |
|
|
Apprentice
Joined: 17 Feb 2008
Posts: 36
Location: Warsaw, PL
|
I have found problem, in linux system log:
eded 'false'; brokerUUID '800c3fe2-0ee5-11e3-a0a9-7f0000010000'; filePath '/opt/ibm/mqsi/9.0.0.0'; workPath '/var/mqsi'; ICU Converter Path ''; ordinality '1'.
Sep 3 10:52:05 iibdev141 IIB[1761]: IBM Integration Bus v9000 (BROKER_DEV1.EGZ1) [Thread 1761] (Msg 1/1) BIP4516S: Failed to find all the required WebSphere MQ java classes. Class 'com.ibm.mq.MQException' n
ot found in CLASSPATH '/opt/mqm/java/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/connector.jar:/opt/mqm/java/lib/com.ibm.mq.pcf.jar:/opt/mqm/java/lib/com.ibm.mq.jmqi.jar:/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm
/java/lib/com.ibm.mq.headers.jar:/opt/mqm/java/lib/com.ibm.mq.commonservices.jar:/opt/mqm/java/lib/com.ibm.mq.jms.Nojndi.jar:/opt/mqm/java/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/connector.jar:/opt/mqm/java/
lib/com.ibm.mq.pcf.jar:/opt/mqm/java/lib/com.ibm.mq.jmqi.jar:/opt/mqm/java/lib/com.ibm.mq.jar:/opt/mqm/java/lib/com.ibm.mq.headers.jar:/opt/mqm/java/lib/com.ibm.mq.commonservices.jar:/opt/mqm/java/lib/com.ib
m.mq.jms.Nojndi.jar:/opt/ibm/mqsi/9.0.0.0/messages:/opt/ibm/mqsi/9.0.0.0/classes:/opt/ibm/mqsi/9.0.0.0/classes/ConfigManagerProxy.jar:/opt/ibm/mqsi/9.0.0.0/classes/brokerutil.jar:/var/mqsi/common/wsrr
Sep 3 10:52:05 iibdev141 IIB[1761]: IBM Integration Bus v9000 (BROKER_DEV1.EGZ1) [Thread 1761] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: com.ibm.mq.MQException was thrown while loading Java user-d
and, next I installed MQSeriesJava_1-7.5.0-1.x86_64.rpm and works fine  |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 03, 2013 4:38 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
This may be caused by the fact that toolkit no longer in-lines resources. You should be building your bar from a script, not deploying the bar (or flows) directly from toolkit.
Use Ant or similar to script your mqsipackagebar command. Be sure to select the compile and in-line resources option in Prepare > Build Options with the appropriate command-line switch. |
No, no, and thrice no.
You can spend hours building the scripts for mqsipackagebar if you want to OR if you are using a CI type of environment. But do you really want to imply that all this expensive (in disk and memory) tooling can't build a simple deployable object?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 4:43 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
This may be caused by the fact that toolkit no longer in-lines resources. You should be building your bar from a script, not deploying the bar (or flows) directly from toolkit.
Use Ant or similar to script your mqsipackagebar command. Be sure to select the compile and in-line resources option in Prepare > Build Options with the appropriate command-line switch. |
No, no, and thrice no.
You can spend hours building the scripts for mqsipackagebar if you want to OR if you are using a CI type of environment. But do you really want to imply that all this expensive (in disk and memory) tooling can't build a simple deployable object? |
My statement relates to the change in behavior of the toolkit. The error occurred due to that lack of in-lining code modules and the fact that the flows were deployed without a consistent way to build the deployable object.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 4:45 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| pvsp wrote: |
I have found problem, in linux system log:
and, next I installed MQSeriesJava_1-7.5.0-1.x86_64.rpm and works fine |
1. USE CODE TAGS.
2. MQSeriesJava_1-7.5.0-1.x86_64.rpm has nothing to do with in-lining code modules.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Sep 03, 2013 4:45 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
My statement relates to the change in behavior of the toolkit. The error occurred due to that lack of in-lining code modules and the fact that the flows were deployed without a consistent way to build the deployable object. |
How does that relate to the solution found by the OP? IMHO, it does not.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 4:47 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
My statement relates to the change in behavior of the toolkit. The error occurred due to that lack of in-lining code modules and the fact that the flows were deployed without a consistent way to build the deployable object. |
How does that relate to the solution found by the OP? IMHO, it does not. |
You are correct. The correct solution is to inline code modules. Installation of the rpm was not needed. IIB provides its own libraries and reliance of external libraries is not ideal.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 03, 2013 5:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| smdavies99 wrote: |
| lancelotlinc wrote: |
My statement relates to the change in behavior of the toolkit. The error occurred due to that lack of in-lining code modules and the fact that the flows were deployed without a consistent way to build the deployable object. |
How does that relate to the solution found by the OP? IMHO, it does not. |
You are correct. The correct solution is to inline code modules. Installation of the rpm was not needed. IIB provides its own libraries and reliance of external libraries is not ideal. |
no, no, and thrice no.
First off, the error mentioned by the original poster was a RUNTIME ERROR, not a TOOLKIT error.
Second of all, there isn't remotely enough information in this thread to make ANY reasonable diagnosis.
Thirdly, "inlining resources" is a strawman, and has nothing to do with whether you build the bar file using the Toolkit, mqsicreatebar, or mqsipackagebar.
It has even less to do with whether you run mqsicreatebar/mqsipackagebar interactively or from a script.
Guess what, there is NO CORRECT SOLUTION TO THIS PROBLEM AS STATED. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 5:17 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqjeff wrote: |
| lancelotlinc wrote: |
| smdavies99 wrote: |
| lancelotlinc wrote: |
My statement relates to the change in behavior of the toolkit. The error occurred due to that lack of in-lining code modules and the fact that the flows were deployed without a consistent way to build the deployable object. |
How does that relate to the solution found by the OP? IMHO, it does not. |
You are correct. The correct solution is to inline code modules. Installation of the rpm was not needed. IIB provides its own libraries and reliance of external libraries is not ideal. |
no, no, and thrice no.
First off, the error mentioned by the original poster was a RUNTIME ERROR, not a TOOLKIT error.
Second of all, there isn't remotely enough information in this thread to make ANY reasonable diagnosis.
Thirdly, "inlining resources" is a strawman, and has nothing to do with whether you build the bar file using the Toolkit, mqsicreatebar, or mqsipackagebar.
It has even less to do with whether you run mqsicreatebar/mqsipackagebar interactively or from a script.
Guess what, there is NO CORRECT SOLUTION TO THIS PROBLEM AS STATED. |
http://www-01.ibm.com/support/docview.wss?uid=swg21623466
| Quote: |
Resolving the problem
Follow the following steps to deploy a BAR file:
Manually create a BAR file in WMBTK that contains the message flows required.
Select the Compile and in-line resources option in Prepare > Build Options and then click Build and Save... button.
Deploy the BAR file.
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 03, 2013 5:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 5:29 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
From personal experience, in-lining the compilation of the code and using a script to build the bar the same way every time addresses the ComIbmMQHeaderNode issue in the same way.
My suggestions are offered without warranty. If someone wants to try them, more power to them.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Sep 03, 2013 5:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
In my experience, any indication of a failure involving product libraries for a built-in node means the original install was done wrong.
But again, not enough information was given.
It's a matter of phrasing. You said "this is the correct solution". That's wrong.
If you'd said "I've done this and it worked", that's different. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Sep 03, 2013 6:10 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqjeff wrote: |
In my experience, any indication of a failure involving product libraries for a built-in node means the original install was done wrong.
But again, not enough information was given.
It's a matter of phrasing. You said "this is the correct solution". That's wrong.
If you'd said "I've done this and it worked", that's different. |
@mqjeff.
Ok, I agree with you. It is quite possible the OP did not install the product in accordance with the step-by-step instructions. It's also possible the OP did not patch to latest, if one is available.
I will reword my answer for you: If you get an error like "A Loadable Implementation Library (.lil, .jar, or .par) is not found" for an in-built node type , please try in-lining the code as you build the bar, and use a script (like Ant) to build the bar so you get a consistent result every time. In my experience, this may resolve the issue of not finding an in-built node type during deployment. Does this pass your muster ?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| dogorsy |
| Posted: Tue Sep 03, 2013 9:32 pm Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| lancelotlinc wrote: |
| My suggestions are offered without warranty. If someone wants to try them, more power to them. |
You should add:
"All rights REVERSED"  |
|
| Back to top |
|
|
|
|
