| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| different results when running user trace on exec grp |
« View previous topic :: View next topic » |
| Author |
Message
|
| kwelch |
 Posted: Thu Jun 06, 2002 7:15 am Post subject: different results when running user trace on exec grp |
 |
|
Master
Joined: 16 May 2001
Posts: 255
|
We are running WMQI 2.1 and twice now I have experienced the situation where my message flow runs without errors when I run it normally but when I put the user trace debug on the execution group to try and figure out why a particular field is not being built as expected I get run time errors on my message flow. It is almost as if the user trace debug imposes strictor rules than running my flow normally. Has anyone else experienced this? Are there any known problems or fixes for this?
Thanks for any input or help.
Karen |
|
| Back to top |
|
 |
| Segs |
| Posted: Thu Jun 06, 2002 7:52 am Post subject: |
|
|
Voyager
Joined: 04 Oct 2001
Posts: 78
Location: Zurich Financial Services
|
Karen
Sorry for building any hopes that this is an answer, but I have been unable to run a trace under 2.1 CSD2. Have you installed the control centre only or are you running from a machine with the config mgr and control centre have been installed?
I think there are more problems with the standalone install similar to those when logoinfo files weren't being copied. |
|
| Back to top |
|
|
| kwelch |
| Posted: Thu Jun 06, 2002 8:04 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 255
|
Hi Segs,
I have the control center only installed on my pc and the trace runs ok, but what concerns me is every time I run the trace, I get these run time errors that should be uncovered under normal circumstances. Here I am thinking my messageflow is working pretty good and it's not. Apparently it just skips right over the offensive code and moves on and writes out a nice XML file. Only when the user trace is on do I get these errors. The errors are easy enough to fix but should be found under normal run of the messageflow. What if I didn't have this other problem and never turned on the trace? These errors have nothing to do with the original problem I was tracing!!!
Karen |
|
| Back to top |
|
|
| Miriam Kaestner |
| Posted: Wed Jun 19, 2002 11:51 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2001
Posts: 103
Location: IBM IT Education Services, Germany
|
The reason for this behaviour could be the parsing-on-demand which WMQI does since 2.1.
With user trace, trace node and debugger the broker is forced to parse where it would not do so without debugging. So run-time parsing errors can occur for invalid messages that might not be detected without debugging. |
|
| 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
|
|
|
|
