Author |
Message
|
satya2481 |
Posted: Thu Dec 23, 2010 7:15 pm Post subject: Timestamp logging issue with UserTrace |
|
|
Disciple
Joined: 26 Apr 2007 Posts: 170 Location: Bengaluru
|
Hi All,
I am using WMB V6.1 Toolkit and RunTime environment...
I need to analyze one of the existing flow performace, in this regards i am using User trace to check which node consuming more time to process the message.
I am following below steps to get the Trace for the message flow...
Quote: |
mqsichangetrace BRKV6 -u -e default -l normal
mqsireporttrace BRKV6 -u -e default
mqsichangetrace BRKV6 -u -e default -r |
Send a test message to the flow
Quote: |
mqsireadlog BRKV6 -u -e default -o C:/Trace.xml
mqsiformatlog -i C:/Trace.xml -o C:/Trace.txt |
When I see the Trace.txt file logging is happening, however the date in the log file is Future date !!! apart from this no difference is shown in the timing... from start till end the timestamp is same...
Anyone know how to resolve this issue.. or how to find out location of the issue....
Regards
Satya |
|
Back to top |
|
 |
nukalas2010 |
Posted: Thu Dec 23, 2010 9:44 pm Post subject: |
|
|
 Master
Joined: 04 Oct 2010 Posts: 220 Location: Somewhere in the World....
|
|
Back to top |
|
 |
smdavies99 |
Posted: Thu Dec 23, 2010 11:17 pm Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
This is how I do it.
To enable trace
Code: |
mqsichangetrace <BKR> -e <EG> -l debug -r [optional -c nnnnn]
|
Send message to flow
Get the log
Code: |
mqsichangetrace <BKR> -e <EG> -l none
mqsireadlog <BKR> -e <EG> -o <EG>.xml
mqsiformatlog -i <EG>.xml -o <EG>.log
|
Obvuously you substitute your values for <BKR> & <EG>
However, you may well be going about the whole thing wrongly.
Remember that a usertrace will slow the whole flow down.
A more realistic way of finding the culprit node(s) is to use the FLOWSTATS feature of broker. You can get the node level performance over a period of time from a running system.
Take a look at the IS02 Support Pack
http://www-01.ibm.com/support/docview.wss?uid=swg24012457
This may well give you what you want pretty well OOTB. _________________ 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 |
|
 |
satya2481 |
Posted: Sun Dec 26, 2010 7:34 pm Post subject: |
|
|
Disciple
Joined: 26 Apr 2007 Posts: 170 Location: Bengaluru
|
Thank you for your replies...
Well, I have used the same commands and tested same flow in another system and the results are good... no issues with the timestamp etc...
Quote: |
May I know yr flow??? |
The flow is using MQ Nodes, Database nodes, filter nodes, compute nodes. There are multiple subflows.
I would like to know how to find out whats the issue with timestamp getting logged with same value in another system...
Regards
Satya |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Dec 27, 2010 2:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Define "future date"
How far off from "correct" time?
What is the system clock configured to? What timezone? |
|
Back to top |
|
 |
satya2481 |
Posted: Tue Dec 28, 2010 11:27 pm Post subject: |
|
|
Disciple
Joined: 26 Apr 2007 Posts: 170 Location: Bengaluru
|
TimeZone - GMT + 05:30
System Clock configured correctly
Wrong time is around 4 days ahead...
Not sure where to check...
Regards
Satya |
|
Back to top |
|
 |
|