ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP2241E: A Loadable Implementation Library (.lil, .jar, or

Post new topic  Reply to topic
 BIP2241E: A Loadable Implementation Library (.lil, .jar, or « View previous topic :: View next topic » 
Author Message
dogorsy
PostPosted: Wed Mar 13, 2013 5:33 am    Post subject: BIP2241E: A Loadable Implementation Library (.lil, .jar, or Reply with quote

Knight

Joined: 13 Mar 2013
Posts: 553
Location: Home Office

Hi,
I am trying to deploy a bar file using the mqsideploy command ( from a perl script ). The flow has been deployed to production (from the toolkit ) and is working fine. I am setting up a test environment, Linux , wmb 6.1 FP2, followed the instructions of installation in the IA91 doc. But when I try to deploy the same bar file that was deployed to production I get
BIP2241E: A Loadable Implementation Library (.lil, .jar, or .par) is not found for message flow node type ''CachePutNode'' in message flow 'FROM_RETEK'
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, etc.

I have deployed other flows using the script, they all deployed ok.
a bit more background: I start from scratch, ie, create configmgr, create broker, create execution group ( with the -f flag to let the configmgr know ), then deploy a couple of flows which work fine, then I try to deploy the flow with the Cache Nodes and fails. This is all done with the perl script.

I have the CacheShared.jar in the shared-classes, both under install_dir and workpath, I even added the install_dir/shared-classes/CacheShared.jar to the CLASSPATH

Any ideas please !!

Update: I have now run the deploy with the -v option and got a trace that confirms /var/mqsi/shared-classes/CacheShared.jar is in the classpath, as well as the relevant mq jars, as seen below ( only an extract of the classpath )

/data02/mqsi/6.1/classes/config.jar::/opt/mqm/java/lib/com.ibm.mqjms.jar:/opt/mqm/java/lib/jms.jar:/var/mqsi/shared-classes/CacheShared.jar

Permissions to the directories and files checked.

I have also tried the mqsideploy command from the command line with the same results.
Back to top
View user's profile Send private message
dogorsy
PostPosted: Fri Mar 15, 2013 2:55 am    Post subject: Reply with quote

Knight

Joined: 13 Mar 2013
Posts: 553
Location: Home Office

I had the same problem running in my windows laptop. The deployment would fail, either running the mqsideploy command or using the toolkit. In desperation, I deleted the broker and recreated using the -w flag ( workpath ). Rerun the mqsideploy command and it worked, the toolkit also worked. Waiting to get access to the Linux box to see if that also solves the problem in Linux
Back to top
View user's profile Send private message
goffinf
PostPosted: Fri Mar 15, 2013 3:58 am    Post subject: Reply with quote

Chevalier

Joined: 05 Nov 2005
Posts: 401

Did you set the LILPath ?

mqsichangebroker YOUR_BROKER -l <location of your JAR>
Back to top
View user's profile Send private message
dogorsy
PostPosted: Fri Mar 15, 2013 4:51 am    Post subject: Reply with quote

Knight

Joined: 13 Mar 2013
Posts: 553
Location: Home Office

The ia91 installation instructions say nothing about changing the lil path, so I did not.
Back to top
View user's profile Send private message
dogorsy
PostPosted: Thu Apr 04, 2013 11:27 pm    Post subject: Reply with quote

Knight

Joined: 13 Mar 2013
Posts: 553
Location: Home Office

yes, after lots of investigation I found out that the workpath was not pointing to the default location, so using the -w flag in when creating the broker was solving the problem, although this solution would not work if you cannot delete and recreate the broker, so you need to make sure what workpath is the broker really using.
Back to top
View user's profile Send private message
marko.pitkanen
PostPosted: Fri Apr 05, 2013 12:56 am    Post subject: Reply with quote

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland

... which can be easily checked with for example mqsireportbroker or mqsiservice commands.

--
Marko
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » BIP2241E: A Loadable Implementation Library (.lil, .jar, or
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.