| Author |
Message
|
| wyatt |
 Posted: Wed Nov 09, 2005 8:18 am Post subject: ESQL verses Java Compute Node |
 |
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
Please share your experiences with using the java compute node verses using ESQL to perform message transformation.
Does mixing java and ESQL in your broker environment complicate maintenance/support.
Did you have any any troubles with capturing/handling java exceptions in your broker environment. How do you pass in java system variables (-D), Can you easily modify the JRE. Did you use log4j? If connecting to DB did you use JNDI
Your thoughts/comments? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Nov 09, 2005 8:32 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Java compute nodes are less than a month or so old for general usage.
Why don't you document your experiences for the rest of us?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wyatt |
| Posted: Thu Nov 10, 2005 8:12 am Post subject: Mixed feelings |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
Well, the java compute node samples provided work as advertised. But I'm finding it difficult to get answers to questions like:
- How to pass in a java system property; normally you might pass this to your JVM like java -Dmy.property=test
- When I introduce log4j statements like
"private static Logger logger = Logger.getLogger("foo");" into a working java compute node the subsequent deploy generates unhelpful error like
BIP4500E: Failed to deploy Java code resource 'somefile.jar'. The Java stack trace is: 'com.ibm.broker.javacompute.MbRuntimeJavaComputeNode.createJavaComputeNode(Native Method) com.ibm.broker.javacompute.MbRuntimeJavaComputeNode.updateNodeClass(MbRuntimeJavaComputeNode.java:205) com.ibm.broker.javacompute.MbRuntimeJavaComputeNode.javaResourceUpdated(MbRuntimeJavaComputeNode.java:234) com.ibm.broker.classloading.JavaResourceClassLoader.javaResourceUpdated(JavaResourceClassLoader.java:201) com.ibm.broker.javacompute.MbJarFileManager.createJar(MbJarFileManager.java:104)'
The Java JAR file deployment to the broker failed.
This is an internal error. Contact your IBM support center. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 10, 2005 8:33 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
- How to pass in a java system property; normally you might pass this to your JVM like java -Dmy.property=test
|
The equivalent would be using a "User Defined Property" and the getUserDefiniedAttribute method.
And you probably want to use logError, logWarning, logInformation methods of the MBService instad of log4j 
_________________
-wayne |
|
| Back to top |
|
|
| wyatt |
| Posted: Fri Nov 11, 2005 11:32 am Post subject: Java vs ESQL |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
Cool, I didnt realize you could create your own variables using "UDP".
.. Im porting an existing java applications (currently triggered) with as few changes as possible so I'm still on the hunt for passing java system properties to the broker - I remember seeing something about MQSIJVERBOSE=-Dfoo=bar. Some undocumented feature. |
|
| Back to top |
|
|
| wyatt |
| Posted: Mon Nov 14, 2005 2:19 pm Post subject: |
|
|
Voyager
Joined: 28 Nov 2004
Posts: 76
|
If your working with java and experience the following error
| Quote: |
BIP4500E: Failed to deploy Java code resource 'yourfile.jar'. The Java stack trace is:
The Java JAR file deployment to the broker failed.
This is an internal error. Contact your IBM support center.
|
You can resolve this problem by placing supporting jar files (like log4j) in ..Program Files\IBM\MQSI\6.0\jre\lib\ext. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Nov 15, 2005 3:40 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| I've received that same deployment error; in my case, I was able to fix it by doing a Project -> Clean... -> All Projects in the toolkit, before adding the artefacts back into the BAR and redeploying. |
|
| Back to top |
|
|
|
|
