| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| problem during MB Toolkit debugging |
« View previous topic :: View next topic » |
| Author |
Message
|
| hemendra123 |
 Posted: Thu Jan 05, 2006 9:53 pm Post subject: problem during MB Toolkit debugging |
 |
|
Novice
Joined: 30 May 2005
Posts: 20
|
Hello, I am trying the debug broker message flow. debug Control enters into the main input node, then to compute node and lastly to output node. when the control gets into compute node, I was able to see the execution by setting the break points. However after it executes the Return Statement, the control gets lost and a exception pops up to contact that Visual Flowdebugger not able to execute. If I run normally it runs fine, till the end. I was wondering if you ever encountered such a problem and likely fixes to it. btw, I am using MB Toolkit 5.0.4 and 5.0.2 Agent Controller
Appreciate your help
Thanks
S Hemendr
_________________
Hemendr |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Thu Jan 05, 2006 10:04 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi hemendra123,
| Quote: |
| If I run normally it runs fine, till the end |
You mean in the debug mode without the breakpoints ? or when u simply run the flow... ?
What does the Windows event log say ?
Do u get the message back in the input queue ?
Regards. |
|
| Back to top |
|
|
| premkumar |
| Posted: Thu Jan 05, 2006 10:24 pm Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
Hi hemendra123,
Have ur input node catch terminal is connected. if not then connect input nodes catch terminal to MQoutput node.
This will let u know that any exception occured in ur compute node or not...
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
|
| hemendra123 |
| Posted: Thu Jan 05, 2006 10:49 pm Post subject: |
|
|
Novice
Joined: 30 May 2005
Posts: 20
|
Hi, Thanks for the prompt replies. I did set the break points in the ESQL and I was able to track the flow until returning the flow from ESQL. The execution control breaks when it executes the last statement of the function ' RETURN TRUE'. If I do the normal execution messages are 'put' into the output queue. and even when debugging, once it breaks, internally it process and put the message into the output queue. it may sound weird but unfortunately that's what happens for me...if you can think of any alternatives, I will try out.. thanks
_________________
Hemendr |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Thu Jan 05, 2006 11:01 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi hemendra123,
| Quote: |
| and even when debugging, once it breaks, internally it process and put the message into the output queue |
MB is not God to know which the ouput queue of every flow is and put it there 
It is not internally processing, u have linked the failure or catch to the output or maybe even set the backout queue as the Output queue.
I am now sure that in both cases ur message is failing, ur message is wrong and hence when it is supposed to go to ouptut, it is failing, that is at the RETURN TRUE statement.
Check your ESQL, or post it here with the imput message.
Regards. |
|
| Back to top |
|
|
| hemendra123 |
| Posted: Sat Jan 07, 2006 8:46 pm Post subject: |
|
|
Novice
Joined: 30 May 2005
Posts: 20
|
Thanks elvis. If you don't understand/experienced the issue, it is unlikely that you may provide me appropriate solution. 
On further analysis, we have seen that if break points are removed from ESQL but placed after the compute node break point , it does go through till the end of executiona and completes the flow. i.e., inpt node -> compute node ( removed break points) -> insert break point ->output node. anyways Also, this issue is independant of messages. Thanks for you suggestion and trying to help me.
Hemendr
_________________
Hemendr |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Sun Jan 08, 2006 5:03 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi hemendra123,
If you would understand your own problem and put it in better words, we would also understand it better...After all even we are not Gods to know what ur actual problem is when u explain it to be something else
And if u still think that the breakpoints in the code where the issue, either ur installation is corrupted or u require the CSD.
Its of no use in questioning my understanding, if inserting and removing breakpoints in ur ESQL is producing different results, u still have a problem.
It is a fact that we do see a breakpoint on a connection even when we have removed it sometimes, if u do a remove and add again, it gets fixed.
But, you should have explained it better, i feel. Anyway don't take it to heart, we are here to help with something we can't see or check 
Regards. |
|
| Back to top |
|
|
| JT |
| Posted: Sun Jan 08, 2006 4:43 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
What version & fixpack do you have installed for the toolkit and the message broker ?
What level is the Agent Controller ?
I have seen this behaviour in the past, and I seem to remember that it was related to the software levels being out-of-sync, but don't hold me to it (my memory is not what it use to be). |
|
| 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
|
|
|
|
