Hi all. After a recent upgrade from a 3.0 version to recent
SVN, it looks like all scheduled jobs are running an hour after the start time
defined in the job_sandbox entry. The webtools screen shows the start time an hour after the
scheduled run time. Any idea as to what could be causing it? Is there perhaps
a timezone setting I’m missing somewhere? Thank you! sterling _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
After digging around I noticed that the
system clock was correct but the hardware clock was an hour behind. I set
hwclock to system clock, but still having problem with jobs running an hour
after scheduled run time even after restarting OFBiz. Anyone have any other ideas? Please? From: Hi all. After a recent upgrade from a 3.0 version to
recent SVN, it looks like all scheduled jobs are running an hour after the
start time defined in the job_sandbox entry. The webtools screen shows the start time an hour after the
scheduled run time. Any idea as to what could be causing it? Is
there perhaps a timezone setting I’m missing somewhere? Thank you! sterling _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
In reply to this post by Sterling Okura
I couldn’t figure out why this was
happening with the new code, so I did a diff of JobManager and tried putting
back some old code. It worked. The JobManager showed the following delegator
finds with the old one commented:
jobEnt = delegator.findByAnd("JobSandbox", updateFields, order);
//jobEnt = delegator.findByCondition("JobSandbox", mainCondition,
null, order); I switched around the comments to comment
out the new one an reactive the old one, and now it goes on time. Not sure if this is just something screwy
with my system, but I thought I’d share in case anyone else has similar problems. Thanks! sterling From: After digging around I noticed that the
system clock was correct but the hardware clock was an hour behind. I set
hwclock to system clock, but still having problem with jobs running an hour
after scheduled run time even after restarting OFBiz. Anyone have any other ideas? Please? From: Hi all. After a recent upgrade from a 3.0 version to
recent SVN, it looks like all scheduled jobs are running an hour after the
start time defined in the job_sandbox entry. The webtools screen shows the start time an hour after the
scheduled run time. Any idea as to what could be causing it? Is
there perhaps a timezone setting I’m missing somewhere? Thank you! sterling _______________________________________________ Users mailing list [hidden email] http://lists.ofbiz.org/mailman/listinfo/users |
Hi,
On one of the servers I have similiar problem. Preface: Hardware and system clocks are synced and shows correct time. trunk is r952341 Case 1 (ofbiz session time zone 1 hour less from actual) : When I login into webtools and schedule job it is showing Pending status even RunTime has already passed. An interesting thing is that when I cancel Pending job it shows cancel date an hour less. Example, runtime date was 13:10 and I cancelled it in 5 minutes and Cancel date was 12:15 Case 2 (ofbiz session time zone in sync with actual): I noticed that for some reason session time zone was one hour off , I changed time zone for session to be EDT ( same as server time now). But when I went into schedule job again and put in time 13:20 in date pickup popup, it was displayed as 14:20 in job listing RunTime column??? Cancel time is correct now though. But the job is not triggered even when I try to cheat it and put one time less from actual time. Where to look? Server is Fedora 11. I would appreciate any ideas. Thank you. P.S. Ofbiz log entries shows one hour less from system time. Where it gets that time? |
Ok, I have solved it.
Time difference ofbiz vs system was caused by the fact that JVM uses own time zone settings regardless of what server has. It was solved by passing time zone param to jvm in startofbiz.sh script. |
Did you try setting the ofbiz.timeZone.default property in start.properties?
-Adrian On 7/21/2010 8:04 AM, masionas wrote: > > Ok, I have solved it. > Time difference ofbiz vs system was caused by the fact that JVM uses own > time zone settings regardless of what server has. It was solved by passing > time zone param to jvm in startofbiz.sh script. |
Hi Adrian,
Yes, I have tried that, but it did not help. Stopped ofbiz, changed property, then started again, but it still used GMT -5:00 zone Here is what I have put in start.prtoperties but it did not helped # -- The default time zone for this OFBiz instance. ofbiz.timeZone.default=America/New_York And here is what really helped (startofbiz.sh): # added timzeone var TIMEZONE="-Duser.timezone=America/New_York" #and add it to args string VMARGS="$MEMIF $MISC $DEBUG $RMIIF $ADMIN $TIMEZONE" |
I spent some time trying to recreate the problem you describe, but I can't duplicate the problem - everything works the way it should.
It might help if you could give me step-by-step instructions on how to recreate the problem - starting with a fresh checkout. -Adrian --- On Wed, 7/21/10, masionas <[hidden email]> wrote: > From: masionas <[hidden email]> > Subject: Re: Users - scheduled jobs delayed by an hour > To: [hidden email] > Date: Wednesday, July 21, 2010, 8:28 AM > > Hi Adrian, > > Yes, I have tried that, but it did not help. Stopped ofbiz, > changed > property, then started again, but it still used GMT -5:00 > zone > Here is what I have put in start.prtoperties but it did not > helped > > # -- The default time zone for this OFBiz instance. > ofbiz.timeZone.default=America/New_York > > And here is what really helped (startofbiz.sh): > > # added timzeone var > TIMEZONE="-Duser.timezone=America/New_York" > > #and add it to args string > VMARGS="$MEMIF $MISC $DEBUG $RMIIF $ADMIN $TIMEZONE" > -- > View this message in context: http://ofbiz.135035.n4.nabble.com/Users-scheduled-jobs-delayed-by-an-hour-tp139235p2297283.html > Sent from the OFBiz - User mailing list archive at > Nabble.com. > |
Hi Adrian,
I think it is coupled somehow to specific server setup, OS version or even architecture. Because as I mentioned above on the other server Fedora Core 5 JVM picked up correct time zone and I never had this kind of problem there. But on the Fedora Core 11 server( hardware is also different from the first one) it did not make it. So on one of the servers I also can;t recreate the problem because it works there as expected, in other words time zone of JVM matches to time zone of the server. |
Free forum by Nabble | Edit this page |