|
From: Leif M. <le...@ta...> - 2008-06-04 16:53:06
|
Thorsten, This is not a problem which I have heard of in the past. A few questions. 1) Are you passing any time related parameters to the JVM when it is launched? 2) What is the specific JVM version you are running? Is it the same on both machines? Depending on your wrapper configuration, you may not be running the JVM you are expecting when running as a service. I suggest setting the following property to see the resolved location of the java exe: wrapper.java.command.loglevel=INFO You can also see the Java version in the log file if you set wrapper.debug=true 3) Do you get the same behavior when running from a console as you do when running as a service? Cheers, Leif Thorsten Lampe wrote: > Sorry for replying to my own post. Just noticed that the 2 hours time shift does exactly match the difference between my local time (GMT+1, Berlin) in daylight savings time versus GMT without daylight savings time. So it seems as if my java app might be running in "plain" GMT. I only wonder why, when the wrapper starting it runs in "GMT+1+daylight savings"... > > > ----- Ursprüngliche Mail ---- > Von: Thorsten Lampe <kar...@ya...> > An: wra...@li... > Gesendet: Montag, den 2. Juni 2008, 22:22:59 Uhr > Betreff: [Wrapper-user] Wrapper starts java app with wrong time (time shift of exactly 2 hours) > > I've got some very strange behavior here. Running on a Windows 2003 Server, the service wrapper starts my java app using a domain user account. The extremely strange thing is that I'm absolutely positive that the wrapper is running at the correct system time while my java app's time is 2 hours behind that!!! > I can see this in the log files since every line logged by my app itself contains a time of, say 5:46.16 PM when the exact same line of output will appear in the wrapper's log as logged at time 7:46.16 PM, the correct system time as currently defined. > > Does anyone have a clue what might be the reason for this? I'm absolutely clueless (and kind of speechless, too... :-) > > BTW, the same app works fine when installed on another - Windows XP - machine so I guess that it must somehow be some kind of configuration problem on my server, but I can't really figure out which... > > > Thanks for any ideas! > > > Thorsten > |