Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Timer always expires

 
Himai Minh
Ranch Hand
Posts: 1361
7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I am using a deployment descriptor, ejb-jar.xml to configure a timer using Ivan's example.
I tried this :



Info: Portable JNDI names for EJB Scheduled1StatelessSessionBean : [java:global/TimerExample1/Scheduled1StatelessSessionBean!com.ivan.scbcd6.Scheduled1StatelessSessionBean, java:global/TimerExample1/Scheduled1StatelessSessionBean]
Info: Schedule: 16/20 # * # * # * # * # * # * # null # 1427471400000 # 1427471460000 # true # scheduledMethod2 # 0 already expired
Info: TimerExample1 was successfully deployed in 374 milliseconds.


For the <start> and <end> elements, I put a future time. But I don't know why it always says "Schedule : .... already expired".
 
Himai Minh
Ranch Hand
Posts: 1361
7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Regarding to the previous post, at the time of the writing, it was March 27th at 15:45pm.

I got the "schedule already expired" issue. Maybe, Glassfish has a system clock that has already passed this 15:50 pm.

I set the start/end time to a more future time, such as this :


The schedule already expired message is not there anymore. The timer has not expired at this time yet.

I think the clock in the Glassfish is not set probably. The clock in Glassfish is ahead of my system clock in my computer, as I guess.

Any idea how to set the clock in Glassfish, so that it is consistent with the current time?
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic