MQSeries.net :: View topic

goffinf · Posted: Wed Feb 18, 2009 8:05 am Post subject: Creating a PAR file

Version 6.1.

I have a set of custom nodes that we having been using inside Broker for quite some time. They are packaged as a JAR and that JAR is on the LILPATH. The custom nodes also use a number of external JARs. These are each declared on the CLASSPATH. Everything works .... but ..

Reading through the documentation I see it is possible to put all of these together into a single PAR file. Sounds good I thought, but I just can't seem to get it to work, so obviously I doing something wrong or have missed something. Here's what I've done and the results :-

All of the classes that relate to the custom nodes are sitting in a directory :-

classes/com/aviva/messagebroker/nodes/class1.class
classes/com/aviva/messagebroker/nodes/class2.class
....

All of the dependant JARs are in :-

lib/log4j-1.2.13.jar
lib/dom4j-1.6.1.jar
...

I created the PAR using this command-line :-

jar cvf myNodes.par classes lib

A PAR file was successfully created which has an internal structure which starts classes/com/aviva/messagebroker/nodes/class1.class or lib/log4j-1.2.13.jar etc...

So it looks like the way it is described in the InfoCentre.

I drop the PAR into the LILPATH folder, REMOVE the entries from the CLASSPATH for the dependant JARs and the JARs themselevs (there all in the PAR now so I shouldn't need them right) and restart the Broker.
Now the trouble starts :-

I have seen a range of different exceptions in the event log, these include :-

( WBRK61_DEFAULT_BROKER.default ) An unexpected exception has occurred in the Java API framework.

An internal processing error has occurred.

This is an internal error. Contact your IBM support center.

( WBRK61_DEFAULT_BROKER.default ) The thread bootstrap code caught an unhandled exception on thread '3424'.

An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The exception was issued on thread '3424'. Further information may be in the exception information associated with this message.

Restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur, then contact your IBM support center.

I tried removing everything from the execution group and redeploying. A flow without custom nodes is fine, but when one contains one all hell breaks loose, even to the point of crashing the EG.

I'm really not sure whats going on (you're getting that right

.

I put everything back the way it was and everythings fine. So what do I need to do to get the PAR file to cooperate ?

Many Thanks

Fraser.