| Author |
Message
|
| Trainee |
 Posted: Tue May 29, 2007 4:59 am Post subject: Loadable Implementation Library (.lil, .jar or .par) |
 |
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
I am getting the following error while deploying the message flows but actually it worked before as I remember.
Can any one suggest what I have to do to fix the following error.
BIP2241E: Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type 'ComIbmXslMqsiNode' in message flow 'EWDOSS'.
The message broker received an instruction to create a message flow node of type 'ComIbmXslMqsiNode', in message flow 'EWDOSS'. The broker does not have the capability to create nodes of this type because an implementation library for this node type was not found in the LIL path.
Ensure that the LIL path is correct and contains all the necessary node implementation libraries, including those supplied by IBM. The node name is case sensitive so ensure the toolkit and runtime names match. If the broker is trying to create a node type that ends in 'NodeNode' then ensure that when the node was registered with the toolkit the name registered didn't end in 'Node'. Then ensure that the message flow and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
Thank you
Trainee |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue May 29, 2007 5:06 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
You have of course checked that the path is correct.....? 
(At the risk of being a little obvious!)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Trainee |
| Posted: Tue May 29, 2007 5:46 am Post subject: |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
mqsiprofile path is correct...not clear what else need to check
Thanks
Trainee |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue May 29, 2007 10:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you're sure it worked "before" then find out what changed between "before" and "now.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Trainee |
| Posted: Tue May 29, 2007 12:54 pm Post subject: |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
Jeff,
We did try that one before posting it here.Just Opened a PMR and working on it.
Thanks guys
Trainee |
|
| Back to top |
|
|
| Trainee |
| Posted: Thu May 31, 2007 10:41 am Post subject: |
|
|
Centurion
Joined: 27 Oct 2006
Posts: 124
|
IBM said that /tmp doesn't have space and created tmp in another directory and set the variable TMPDIR =/ new location of/ tmp directoryto the mqsi profile and it solved the issue.
This is what IBM said:
The issue is most likely fixed by the changing the tmp space.
the jar files are expanded using tmp and
hence need enough space to run the broker when using any Java
node including the XMLT node. |
|
| Back to top |
|
|
| dk27 |
| Posted: Fri Mar 13, 2009 9:04 am Post subject: |
|
|
Acolyte
Joined: 28 Apr 2008
Posts: 51
|
I have exact same problem. I tried to resolve with the solution given but problem is not getting resolved.
Any other suggestions please? |
|
| Back to top |
|
|
|
|
