SwiftMQ internal clock differs from system's clock by 1 hour

classic Classic list List threaded Threaded
3 messages Options
CL
Reply | Threaded
Open this post in threaded view
|

SwiftMQ internal clock differs from system's clock by 1 hour

CL
I was debugging a very wierd problem when I chance upon this:

-rw-rw-r--  1 mtouche mtouche 1050239 Sep 20 17:50 warning.log-20060920185033.old
-rw-rw-r--  1 mtouche mtouche 1052256 Sep 21 08:30 warning.log-20060921093035.old
-rw-rw-r--  1 mtouche mtouche 1052210 Sep 21 08:52 warning.log-20060921095236.old

You can see that the time at the end of the filename is 1 hour later then the official system time. As such, all scheduled message got deleted immediately and not processed because all the messages are 1 hour late!

Anyone knows how to fix the clock?
CL
Reply | Threaded
Open this post in threaded view
|

Re: SwiftMQ internal clock differs from system's clock by 1 hour

CL
Found out that this is a Java TimeZone problem. I solved it with :

java -Duser.timezone=Asia/Bangkok

There is probably a problem for the jvm to read the /etc/localtime Timezone file properly.

I wonder if there is an easier method.

:(
Reply | Threaded
Open this post in threaded view
|

Re: SwiftMQ internal clock differs from system's clock by 1 hour

IIT Software
Administrator
SwiftMQ uses the default time zone, e.g. with Calendar.getInstance(). Actually that should work...