| Author |
Message
|
| torryramesh |
 Posted: Wed Apr 27, 2005 12:20 pm Post subject: Mistmatch in the timestamp of Broker's Trace output and MQM |
 |
|
Novice
Joined: 06 Aug 2004
Posts: 15
|
Environment:
AIX V 5, WMQI 2.1 with CSD 6, MQ V 5.3
Issue brief: Mistmatch in the timestamp of Broker's Trace output and MQMD PutTime.
Issue Description: We have built a message tracking tool to monitor flow of interface messages in production. When the message reaches the hub,
we store the MQMD put time in the DB to later display in the UI for the message. Also, trace is enabled for all the execution groups (this will be retained for some time...). The trace file has a time one hour behind what the puttime represents.
Eg.
MQMD PUT TIME to HUB -> 15:56:04
Broker Trace - Message Arrival time -> 16:56:04
(All times are represented in GMT.)
Can anyone suggest why this might happen ? Do we have to set any parameter in MQ or in the Broker so that these two give the same picture ? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Apr 27, 2005 12:47 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
So, your Broker is acting as a hub.
That means that messages coming from other computers are passing through the Broker.
And you're surprised that the clock on the other computers is different than the one on the broker?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| torryramesh |
| Posted: Thu Apr 28, 2005 12:19 pm Post subject: Mismatch in Timstamp. |
|
|
Novice
Joined: 06 Aug 2004
Posts: 15
|
I believe the MQ Queue Manager at the source will convert its local time into GMT which is then filled in MQMD PutTime.
Based on this assumption, why should the Broker trace indicate a different timestamp |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 28, 2005 12:56 pm Post subject: Re: Mismatch in Timstamp. |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| torryramesh wrote: |
I believe the MQ Queue Manager at the source will convert its local time into GMT which is then filled in MQMD PutTime.
Based on this assumption, why should the Broker trace indicate a different timestamp |
Because the clock on machine A is different than machine B.
So when the time on machine A gets converted to GMT, it is still wrong.
And so when it moves over to machine B, it's still a different time than the GMT time on machine B.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 28, 2005 8:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Or just assume computer B has set its Time Zone to CET
Now for whatever reason B has forgotten to define a summer time period.
Voila B is now sending messages (if it's clock is set to display the correct local time) that are no longer keeping GMT time but GMT + 1.
So when B sends a message at 17:00 GMT (19:00) local (Summer time in CET = GMT +2) it's GMT time gets set to 18:00. (And you get 1 hour synchronization problem right there)
Just because a computer displays the right time does not mean that it's time zone settings are right. !! This will skew the way GMT/UTC is calculated from local time...
 |
|
| Back to top |
|
|
| torryramesh |
| Posted: Fri Apr 29, 2005 11:29 am Post subject: |
|
|
Novice
Joined: 06 Aug 2004
Posts: 15
|
One more fact that I would like to add to my initial question:
We have a cluster set up in the production environment. We have API Exits(Put) configured for all applications connecting to hub.
So, when the Source Application connects to QMgr A which is in Eastern Time and puts a message to a clustered queue, the exits caputre the PUTTIME - SOURCE. This can be different from Broker's timestamp and we know it.
But, when the message is actually put in the physical queue in the hub, another put time is generated. Lets call this PUTTIME-HUB. My question on the Mismatch of timestamp is between this PUTTIME-HUB and the WMQI Broker Trace timestamp and nothing to do with PUTTIME-SOURCE.
Sorry for misleading the group. Would appreciate if you could share some more on what you think. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Apr 29, 2005 7:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well that would all depend on what is happening between the 2 registrations:
A) uncorrectly defined TimeZones
B) Communications problems ?? Remember MQ is Asynchronous !!
C) Work build up. It may take time to get to the message in the queue.
Etc ....
Enjoy  |
|
| Back to top |
|
|
|
|
