| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Issues with trace node. |
« View previous topic :: View next topic » |
| Author |
Message
|
| VishnuPrasadS |
 Posted: Fri Feb 22, 2013 7:30 am Post subject: Issues with trace node. |
 |
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Hello All,
--- Issues with trace node.
--- Need help to find root cause.
--- I use WebSphere Message Brokers Version: 6.1.0.11 and WebSphere MQ Version: 7.0.1.6
--- I created message flow with trace at input and output as shown in figure. Names : Trace_IN , Trace_OUT_A , Trace_OUT_B, Trace_OUT_C
https://docs.google.com/file/d/0B4qbySw4DAiQSEdiaUZRQkFpbFE/edit?usp=sharing
--- More than 55 input messages that were suppossed to passed to Trace_OUT_A have not been logged. These 55 messages were logged in Trace_IN.
--- Logic of flow is : If message flows through upper branch it will reach only one of the trace nodes at output. In case of exception in upper branch, messages will pass through lower branch and finally reach both trace nodes at output, namely : Trace_OUT_A, (Trace_OUT_B or Trace_OUT_C) .
--- Only two messages were logged in Trace_OUT_A. These two messages were not logged in Trace_IN.
--- I redeployed the bar file and the logging in trace files happens as expected.
--- Please suggest what can cause this unusual behaviour. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Feb 22, 2013 8:38 am Post subject: Re: Issues with trace node. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| VishnuPrasadS wrote: |
| Please suggest what can cause this unusual behaviour. |
What does the user trace say is happening?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| VishnuPrasadS |
| Posted: Sun Feb 24, 2013 1:38 am Post subject: Re: Issues with trace node. |
|
|
Apprentice
Joined: 22 Feb 2013
Posts: 28
Location: Pune, India
|
Today I donot have user log or service log.
This flow was running on multiple instances.
Is it possible that due to multiple thread accessing same file, caused file dead lock and this lock was released when i redeployed the bar file, with no code or configuration change. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Feb 24, 2013 6:37 am Post subject: Re: Issues with trace node. |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| VishnuPrasadS wrote: |
| Is it possible that due to multiple thread accessing same file, caused file dead lock and this lock was released when i redeployed the bar file, with no code or configuration change. |
No. Even if you're outputting trace to a file (which is not ideal & implies you're using it as a poor man's audit) then WMB should manage. At worst you should get one file and another instance abending because it couldn't write to the locked file.
You need to take a trace to see what's happening.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Feb 25, 2013 5:38 am Post subject: Re: Issues with trace node. |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| Vitor wrote: |
| VishnuPrasadS wrote: |
| Is it possible that due to multiple thread accessing same file, caused file dead lock and this lock was released when i redeployed the bar file, with no code or configuration change. |
No. Even if you're outputting trace to a file (which is not ideal & implies you're using it as a poor man's audit) then WMB should manage. At worst you should get one file and another instance abending because it couldn't write to the locked file.
You need to take a trace to see what's happening. |
Trace files are opened by WMB with shared access. They are not opened for exclusive access. Your guess that the problem was caused by a Trace file locking condition is incorrect.
Troubleshoot and fix the real problem Don't guess.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Tue Feb 26, 2013 9:18 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
Can we get bit more details on how many of messages when through Trace_IN, A, B/C?
Also worst case, since the failure terminal of the input node is not connected, what happens if there is a fault in the catch side of the flow? Is MQ used in this if yes does it have a backout queue. if yes can you check whether the messages are present there.
Always safe to connect your failure terminal to ensure any unhandled exception is handled 
_________________
A Colorblind man may appear disadvantaged but he always sees more than just colors... |
|
| 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
|
|
|
|
