| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Execution group timestamp becomes garbled |
« View previous topic :: View next topic » |
| Author |
Message
|
| gisly |
 Posted: Tue Aug 25, 2015 7:44 am Post subject: Execution group timestamp becomes garbled |
 |
|
Apprentice
Joined: 10 May 2012
Posts: 29
|
Hi!
I've got a strange thing on my local Windows WMB v 7.
When started, all execution groups on all broker instances write the following into their console.logs:
16870-05-25 11:57:27.498 Execution group started. UUID is: 'groupUid'. Broker is: BrokerName
Listening for transport dt_socket at address: 2233
invalid epocht: dec=470211123447 ; hex=6d7ac458f7
max valid epocht: dec=32535244799 ; hex=793406fff
In the system event viewer, I see the following:
| Code: |
Message broker internal error: diagnostic information ''ImbTimeStamp::fromString() reported 'Invalid timestamp string' with values... '-1' ''S22007'' ''16870-05-25 11:57:27.498''''.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: ''ImbTimeStamp::fromString() reported 'Invalid timestamp string' with values... '-1' ''S22007'' ''16870-05-25 11:57:27.498''''.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
|
As a result, the broker instance stops and cannot be contacted.
There are no errors in the broker's log.
Broker restart, and the whole system reboot did not help.
Actually, I deleted the damaged instance and created a new one with the same name which works without any problem.
However, I am really curious about the reasons of this wild behaviour. Where did they take this date?
I've checked the date in WMB's java, and it's OK. |
|
| Back to top |
|
 |
| gisly |
| Posted: Tue Aug 25, 2015 11:43 pm Post subject: |
|
|
Apprentice
Joined: 10 May 2012
Posts: 29
|
I managed to solve it:
the wrong date was in the file:
C:\ProgramData\IBM\MQSI\components\(broker name)\repository\brokeraaeg.dat
(DateLastUpdated="16870-05-25")
I changed the date to the right one, and the broker started without any problem.
I still don't understand why the file had got damaged because I definitely had not changed it by hand. |
|
| 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
|
|
|
|
