| Author |
Message
|
| mm7106 |
 Posted: Fri Aug 19, 2011 4:21 pm Post subject: Debugging FTE Nodes in Toolkit 7.0.0.1 |
 |
|
Newbie
Joined: 19 Aug 2011
Posts: 3
|
A message flow with an FTE input node does not seem to stop or
recognize breakpoints in Debug Mode. When the Debugger is Terminated, the message flow resumes processing. Debug Mode works with any other message flow with MQ Input, File Input, SAP Input, etc but it does not work with FTE Input. Broker and Toolkit version: 7.0.0.1, FTE version 7.0.3, MQ version 7.0.1.3. Is it possible to debug FTE Input nodes? Are there configurations that need to be set? Also please refer us to documentation on the Info Center if any. There are no exceptions since the message flow is not invoked at all. |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Aug 22, 2011 4:33 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mm7106 |
| Posted: Mon Aug 22, 2011 9:33 am Post subject: |
|
|
Newbie
Joined: 19 Aug 2011
Posts: 3
|
| Immediately after the FTE Input Node on the Out terminal and immediately after a Trace Node which connects from the FTE Input node. If your suggesting that there should be breakpoints on the other FTE Input node terminals, the file is processed in non-Debug mode successfully. There are no errors on the Failure or Catch terminals. The message flow is not invoked at any break point. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 22, 2011 9:52 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 22, 2011 9:59 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| I always place a trace node after all terminals. You'd be surprised what you see. |
OK, I'll bite - what do you see in a Trace node related to the debugger? 
And what would the OP see that he's not seeing in the Trace node he already claims to have in place?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Aug 22, 2011 10:17 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
| I always place a trace node after all terminals. You'd be surprised what you see. |
So all your flows run like a dog with three broker, sorry broken legs then?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 22, 2011 11:40 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| smdavies99 wrote: |
| lancelotlinc wrote: |
| I always place a trace node after all terminals. You'd be surprised what you see. |
So all your flows run like a dog with three broker, sorry broken legs then? |
hahahahaah
In my banking industry flows, as if for a major bank or a major credit card network, I tend to be more conservative on trace nodes. In my insurance industry flows, I let my hair down a bit since latency is not the prime consideration. Trace nodes disabled in production add three percent latency. Not a bad tradeoff. So my internal broker latency goes from 80 milliseconds to 81 milliseconds. 1 millisecond delay for the convenience of trace nodes is a good tradeoff IMHO.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 22, 2011 11:46 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| lancelotlinc wrote: |
| I always place a trace node after all terminals. You'd be surprised what you see. |
OK, I'll bite - what do you see in a Trace node related to the debugger? And what would the OP see that he's not seeing in the Trace node he already claims to have in place? |
For example, I now put (thanks mgk) a Trace node on the SOAPRequest -> Fault terminal. Some (all) SOAP faults do not get processed by the typical error processing upstream.
I rely less on interactive debugging and more on Trace nodes now that I am in the insurance industry again. In banking industry, you have to use the debugger more since you cannot be so liberal with Trace node sprinkles.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 22, 2011 11:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| I rely less on interactive debugging and more on Trace nodes now that I am in the insurance industry again. In banking industry, you have to use the debugger more since you cannot be so liberal with Trace node sprinkles. |
That's nice for you. This relates to the OP's question about breakpoints how? On the off chance the OP works in banking?
Don't answer the question you wish has been asked. And don't project your Nirvana-like site onto the wider world - there are enough insurance sites who frown on Trace nodes.
Which is a shame, since Trace nodes and user trace are the more useful diagnostic tool.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Aug 22, 2011 11:54 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| This relates to the OP's question about breakpoints how? |
It provides alternative tool choices to the OP since he or she is having difficulty with the interactive debugger.
It's Monday Vitor. Cheer up friend. Only 4 more days till the weekend.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Aug 22, 2011 12:00 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| Vitor wrote: |
| This relates to the OP's question about breakpoints how? |
It provides alternative tool choices to the OP since he or she is having difficulty with the interactive debugger. |
And is no use if he's stuck with the debugger (for instance can't run mqsichangetrace)
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mm7106 |
| Posted: Mon Aug 22, 2011 4:37 pm Post subject: |
|
|
Newbie
Joined: 19 Aug 2011
Posts: 3
|
| Alright girls, lets calm down. Lancelotlinc was just trying to help. And he has a point because it worked. I placed Trace nodes on the Catch and Failure Terminals and when the broker agent was invoked, the FTE Input node woke up. It stopped on the Out Terminal which was already connected with a breakpoint prior to this post. I guess it needed the other 2 legs. I did get a "Timeout occurred while waiting for packet 812" a few times when I tried to terminate the debugger. Anyone knows what that means? Entire error: The debugger failed with the following exception: org.eclipse.jdi.TimeoutException: Timeout occurred while waiting for packet 812. occurred disconnecting from VM. |
|
| Back to top |
|
|
|
|
