| Author |
Message
|
| madi |
 Posted: Thu Feb 15, 2007 7:57 am Post subject: BIP2241E: |
 |
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Hi all
i am getting this lil not found error
this is for the XMLValidator which i got from a support pack ........ i've been using this for some months now but did not have a problem ...... yesterday i added some more plugins (cache nodes from a diff support pack)
just extracted the diff file for the cache nodes into diff directories like jplugin and shared classes and stuff
but now when i try to deploy a flow it says
| Quote: |
BIP2241E: Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type 'XMLValidatorNode' in message flow 'IBUS_ARCH3_Common_Flow'.
The message broker received an instruction to create a message flow node of type 'XMLValidatorNode', in message flow 'IBUS_ARCH3_Common_Flow'. 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. |
and this flow does not even have the new cache node !!!
how can adding a new jar file to the jplugin cause problems with the already existing xmlValidator node jar file 
any help is appreciated
thanks
madi |
|
| Back to top |
|
 |
| au@kosa |
| Posted: Mon Feb 19, 2007 3:53 am Post subject: |
|
|
Centurion
Joined: 04 Jan 2007
Posts: 103
Location: pune
|
Hi,
The XMLValidator node is implemented as a Java plug-in node. So, at the end we are putting the *.jar file into the MQSI/6.0/bin folder (runtime environment setting). Please check the name of the jar file coming along with cache nodes. It is possible that it is fiddling with the XMLValidator jar file.
Regards,
Amit Upadhyaya |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 19, 2007 4:41 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| au@kosa wrote: |
| we are putting the *.jar file into the MQSI/6.0/bin folder |
That's a horrible idea.
Java plugins go in jplugin. Support classes for Java plugins go in shared-classes.
no user code should go in bin.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| madi |
| Posted: Mon Feb 19, 2007 8:20 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
so jeff, what do u think might be the problem
thanks for reply amit but jeff is right user code does not go into bin
--madi |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Feb 19, 2007 8:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
These two support packs *shouldn't* conflict with each other.
And they're both Cat 2, so you can't open a PMR...
I just dug through the jar files that come with these support packs, and I didn't see anything obvious.
I'd review everything that's in jplugin again, and make sure that permissions and etc. are fine.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| madi |
| Posted: Mon Mar 05, 2007 9:28 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
I couldnt figure out what is causing the cache node jar files to not work with my broker
these are the errors im getting when i extract the jar files into their respective locations and restart the broker
| Quote: |
( WBRK6_DEFAULT_BROKER.Arch3_SFE ) Java exception: ''java.lang.reflect.InvocationTargetException''; thrown from class name: ''sun.reflect.NativeMethodAccessorImpl'', method name: ''invoke0'', file: ''NativeMethodAccessorImpl.java'', line: '-2'
The message contains that data associated with a Java exception.
No user action required.
( WBRK6_DEFAULT_BROKER.Arch3_SFE ) The method ''registerAllPlugins'' has thrown the following exception: 'java.lang.reflect.InvocationTargetException'.
The Java API framework has caught an unhandled Java exception.
Contact the node provider for further details.
( WBRK6_DEFAULT_BROKER.Arch3_SFE ) Exception caught whilst loading file ''C:\Program Files\IBM\MQSI\6.0\bin/imbjplug2.lil'', the broker will operate with reduced capability.
The message broker caught an exception whilst loading the implementation file ''C:\Program Files\IBM\MQSI\6.0\bin/imbjplug2.lil''. The broker will continue to operate but with reduced capabilities. See the following messages for details of the error.
See your system log for other messages associated with this one to establish and correct the cause of the problem.
|
these error repeated for each exec group that i have in the broker
can you guys think of anything that might cause this??
--madi |
|
| Back to top |
|
|
| bbburson |
| Posted: Mon Mar 05, 2007 10:53 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
May or may not have anything to do with your problem, but the mixed slashes in
| Quote: |
| ''C:\Program Files\IBM\MQSI\6.0\bin/imbjplug2.lil'' |
look mighty strange to me. |
|
| Back to top |
|
|
| madi |
| Posted: Mon Mar 05, 2007 11:24 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
that looked strange to me at the first look too but i thought that was an internal path that broker was using .... i will go to fixpack 3 today and see if this problem goes away
thanks
madi |
|
| Back to top |
|
|
| madi |
| Posted: Mon Mar 05, 2007 1:52 pm Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
upgraded to fixpack 3 but still having the same problem 
--madi |
|
| Back to top |
|
|
| prasad.edlabadkar |
| Posted: Wed May 02, 2007 2:01 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2006
Posts: 21
Location: Pune, India
|
Put the CacheNode.jar, XMLValidator.jar,CacheShared.jar
_________________
Thanks and Regards
Prasad Edlabadkar
Tech Lead - Websphere Business Integration |
|
| Back to top |
|
|
| prasad.edlabadkar |
| Posted: Wed May 02, 2007 2:02 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2006
Posts: 21
Location: Pune, India
|
Sorry....hit enter by mistake
Put the CacheNode.jar, XMLValidator.jar,CacheShared.jar in the System classpath
_________________
Thanks and Regards
Prasad Edlabadkar
Tech Lead - Websphere Business Integration |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 02, 2007 2:04 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| prasad.edlabadkar wrote: |
Sorry....hit enter by mistake
Put the CacheNode.jar, XMLValidator.jar,CacheShared.jar in the System classpath |
No.
Follow the instructions supplied with the SupportPack exactly.
You need to put one file in messages, one file in shared-classes, and one file in jplugin.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| prasad.edlabadkar |
| Posted: Wed May 02, 2007 2:08 pm Post subject: |
|
|
Novice
Joined: 10 Feb 2006
Posts: 21
Location: Pune, India
|
| jefflowrey wrote: |
| prasad.edlabadkar wrote: |
Sorry....hit enter by mistake
Put the CacheNode.jar, XMLValidator.jar,CacheShared.jar in the System classpath |
No.
Follow the instructions supplied with the SupportPack exactly.
You need to put one file in messages, one file in shared-classes, and one file in jplugin. |
I tried that...but still it was not able to load the plugin. Putting the jar in the classpath resolved the issue.
_________________
Thanks and Regards
Prasad Edlabadkar
Tech Lead - Websphere Business Integration |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed May 02, 2007 2:19 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| prasad.edlabadkar wrote: |
| I tried that...but still it was not able to load the plugin. Putting the jar in the classpath resolved the issue. |
But may have introduced other problems, as now stuff is loaded by an entirely different classloader.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
