Joined: 15 May 2001 Posts: 540 Location: New Zealand
I would be inclined to run the service trace rather than user trace and hope that you can trap an example of the occurence. You would need to specify a big trace size (-c 20000 for example) and hope that you can then stop the trace, if a message gets stuck, before it wraps around.
Unfortunately we did not luck out. We had turned on a simple trace and when the messages started to pile up in the queue, there was nothing written in the log file. It only wrote to the log file once the flow was restarted and the messages started to process. The log file has no valuable information.
This is a QA environment and I'm reluctant to turn on the debug trace since it will slow it down. Even then, I'm not sure it will catch anything in the trace when it fails to process the messages.
Do you guys think it will write to the Event log if I do the suggested option mentioned above even though it did not write anything in the trace file? I am running out of options now.
Joined: 15 May 2001 Posts: 540 Location: New Zealand
Have you not seen this problem in any of your other broker runtime environments?
The user trace will only have trace entries if the message is read. However the service trace may show the flow polling the queue, or not! If you raise a PMR and describe the symptoms the change team should tell you what tracing to activate
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