| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Timestamp variations seen in Broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| kash3338 |
 Posted: Thu Jun 25, 2015 12:58 am Post subject: Timestamp variations seen in Broker |
 |
|
Shaman
Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India
|
Hi,
We have an issue where we are seeing differences in the Time stamps shown in the deployment logs of Broker. The Timestamp shown in the log is 11 Hours ahead of the Current Timestamp. We have now traced this difference only in the Deployment time seen through Broker toolkit.
But the flows deployed in the Broker updates few Database tables with CURRENT_TIMESTAMP and those times are seen correct. There are no issues in that. When the below mqsi command was run to see the Broker time set, this is what we see,
| Code: |
mbuser@jfststcmtapp006:/home/mbuser $ mqsiservice -t
BIPmsgs en_US
Console CCSID=819, ICU CCSID=819
Default codepage=ISO-8859-1, in ascii=ISO-8859-1
JAVA console codepage name=ISO-8859-1
ICU Version: 4.8.1.1
ICU TZ Data Version: 2013i
Current Local time: 2015-06-25 13:29:01.026369
Current UTC time: 2015-06-25 18:59:01.026427
Env TZ: IST+5:30
ICU TimeZone ID: IST
ICU Non-DST Name: GMT-05:30
ICU DST Name: GMT-05:30
Standard offset from GMT: -330
Supports DST? false
Day Names: Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday,
Month Names: January, February, March, April, May, June, July, August, September, October, November, December,
First day of week: 1
Days in first week of year: 1
AM: AM PM: PM
BIP8071I: Successful command completion.
|
The problem summary is as below,
1. Broker shows a different time (11 Hours ahead) in the deployment properties view from Toolkit. Why is this behavior and how to correct it.
2. The Timestamp inserted in the DB tables from the flows deployed in the Broker is correct
3. The above code snippet shows the result of mqsi command run to get the Broker set time. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jun 25, 2015 4:17 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
This could be due to ambiguous Time Zone names.
If you go with the 3 character time zone make sure there does not exist another time zone with the same 3 char name and a different offset...
It may be better not to use a timezone name with 3 chars but to use the std GMT offset...
Have fun 
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
