| Author |
Message
|
| TBS |
 Posted: Tue Dec 04, 2007 4:53 am Post subject: MQSICHANGETRACE do not stop trace |
 |
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
The trace is not stopping when is isue a MQSICHANGE
I try :
mqsichangetrace <brokername> -t -b -l none
mqsichangetrace <brokername> -t -e <egroup> -l none
mqsichangetrace <brokername> -u -e <egroup> -l none
No one is stopping the I/O
File name
BKMQSINT03.f09cf6bc-0a01-0000-0080-f7219c01a8af.userTrace.bin.2
Any help ? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Dec 04, 2007 4:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What version of broker? What platform?
Have you satisfied yourself that the trace is coming from the broker/execution group that you think it is, not from a different group that happens to have the same or similar flow running in it? Or that you don't have a trace node actually in the flow?
At first glance the commands look right, or at least close.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Dec 04, 2007 5:05 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
WMB V 6.0.0.5
And there is only one exec group --> default |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 04, 2007 5:10 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
On what platform?
| TBS wrote: |
| And there is only one exec group --> default |
And the flow in question has no trace nodes in it, the output is a broker trace not user defined output to standard output, perfectly standard and stopping / starting the broker does not affect it?
Is it user trace or system trace?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Dec 04, 2007 7:22 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
It's on a windows platform ..
My problem is that I do not now what trace that is running. A nother erson have startet it and is not working here any more 
You wrote -> "And the flow in question has no trace nodes in it,"
Is the trace node logging in "BKMQSINT03.f09cf6bc-0a01-0000-0080-f7219c01a8af.userTrace.bin.2" ?
stopping / starting the broker does not affect it any thing ...
There is no trace/traceSize from the MQSISERVICE command
Is theere a place where I can see witch traces that are on ? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Dec 04, 2007 7:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| TBS wrote: |
You wrote -> "And the flow in question has no trace nodes in it,"
Is the trace node logging in "BKMQSINT03.f09cf6bc-0a01-0000-0080-f7219c01a8af.userTrace.bin.2" ?
|
A trace node will log to whatever location it's set to. Yours sounds like a default file location.
It's also immune to the change trace command and will continue to log even if broker trace is switched off because it's not part of the trace mechanism.
Have you checked that the flow does not have such a node? Is the trace a complete description of the flow's actions or only part (like a single node)? This would be another clue.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 04, 2007 7:34 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is there a flow that has user trace turned on?
Edit: Also, what is *in* that trace file?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Dec 04, 2007 10:24 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
There is 200 flows in the default execgroup
The files is locat in :
C:\Documents and Settings\All Users\Application Data\IBM\MQSI\common\log
There is 4 files that wraps arround
BKMQSINT03.f09cf6bc-0a01-0000-0080-f7219c01a8af.userTrace.bin.0 and 1 and 2 and 3
I'l try to stop every one ....
Is there a place where I can see witch traces that are on ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 04, 2007 11:06 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Toolkit should show you this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Dec 04, 2007 11:41 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
I have now read the trace and found out that a flow i looping but it do not react on stop trace from from tool kit.
Is this the FLOW ?
This is an information message produced by WBIMB statistics.
2007-12-04 19:58:19.506145 10168 UserTrace BIP2380I: WBIMB message flow statistics.
ProcessID='9200',
Key='69813',
Type=''Archive'',
Reason=''Redeploy'',
BrokerLabel=''BKMQSINT03'',
BrokerUUID=''ef9cf6bc-0a01-0000-0080-f7219c01a8af'',
ExecutionGroupName=''default'',
ExecutionGroupUUID=''f09cf6bc-0a01-0000-0080-f7219c01a8af'',
MessageFlowName=''DOKFS5060'',
StartDate='DATE '2007-12-04'',
StartTime='TIME '19:58:10.029'',
EndDate='DATE '2007-12-04'',
EndTime='TIME '19:58:15.039'',
TotalElapsedTime='0',
MaximumElapsedTime='0',
MinimumElapsedTime='0',
TotalCPUTime='0',
MaximumCPUTime='0',
MinimumCPUTime='0',
CPUTimeWaitingForInputMessage='0',
ElapsedTimeWaitingForInputMessage='5006000',
TotalInputMessages='0',
TotalSizeOfInputMessages='0',
MaximumSizeOfInputMessages='0',
MinimumSizeOfInputMessages='0',
NumberOfThreadsInPool='1',
TimesMaximumNumberOfThreadsReached='0',
TotalNumberOfMQErrors='0',
TotalNumberOfMessagesWithErrors='0',
TotalNumberOfErrorsProcessingMessages='0',
TotalNumberOfTimeOuts='0',
TotalNumberOfCommits='0',
TotalNumberOfBackouts='0'.
AccountingOrigin=''Anonymous''.
Statistical information for message flow ''DOKFS5060'' in broker ''BKMQSINT03''. |
|
| Back to top |
|
|
| TBS |
| Posted: Tue Dec 04, 2007 11:59 am Post subject: |
|
|
Centurion
Joined: 29 Jan 2007
Posts: 143
Location: Hillerød / Denmark
|
I have now stoped the two flow and the trace i stoped.. 
Thank's for your help .. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 04, 2007 12:18 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yeah, so if a flow is stuck in a loop on an input message, it may not respond to control commands such as "stop trace"...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mqceries |
| Posted: Thu May 10, 2012 7:50 am Post subject: |
|
|
Acolyte
Joined: 02 Dec 2011
Posts: 70
|
Apologize for bumping the old thread, but wanted to share my solution. I also had a similar problem yesterday that we are not able to stop the trace because of the looping. The flow was not stopping by any means so as the trace. We tried to kill the process id for the EG (same as mqsireload) and then tried to stop the trace and was successfull. After the killing the PID , EG started with another PID and we are able to stop the trace with out stopping the flow.
Broker : 6.1 fixpack 9
OS : Windows 2003 Server.
Trace : User trace.
Hope it will be helpful. |
|
| Back to top |
|
|
|
|
