| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JavaCompute nodes, JNI errors and debug trace |
« View previous topic :: View next topic » |
| Author |
Message
|
| international |
 Posted: Tue Jun 20, 2006 1:04 am Post subject: JavaCompute nodes, JNI errors and debug trace |
 |
|
Apprentice
Joined: 19 Jun 2006
Posts: 37
|
Hello.
I've got two problems, really.
1) I'm getting "Error occured in the JNI layer during flow debugging" when using the flow debugger with JavaCompute nodes. It was working yesterday but, after a reboot, its not working today. Does anyone have a reason/solution for this problem?
2) I'm reduced to using debug trace! How do you get debug trace to show the Java line by line (like ESQL is shown)? Is there a special setting (akin to the JVM debug port for flow debugging)?
cheers
Tony
PS Running on XP, broker and toolkit are v6 fixpack 1. |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Tue Jun 20, 2006 1:19 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi international,
What version of agent controller are u using....which version of broker ?
I had the same problems with v6.0.1 of agent controller and so moved back to 5.0.2....now things work perfectly.
Anyway the error has to do with the flow being still in deployment....you should remove it from the broker, restart the services and clean the queues.
Regards. |
|
| Back to top |
|
|
| international |
| Posted: Tue Jun 20, 2006 2:10 am Post subject: |
|
|
Apprentice
Joined: 19 Jun 2006
Posts: 37
|
Thanks for that. I reverted to RAC v5.0.2 and the JNI error has gone away. However, I'm still unable to step into Java code. While flow debugging, the JavaCompute node has the little green "step into source" icon above it, but when I click on "step into source" it doesn't actually step into the Java code. Have you seen this before?
cheers
Tony |
|
| Back to top |
|
|
| international |
| Posted: Tue Jun 20, 2006 3:14 am Post subject: |
|
|
Apprentice
Joined: 19 Jun 2006
Posts: 37
|
Oops, my fault. I created a new EG but forgot to establish a JVM debug port. I can now debug flows fine
cheers
Tony |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
