I do have fine logging enabled. It seems that the timeout is not getting
called - on restart after a missed persistent timeout the container always
detects this and wil run the job immediately.
I would post all the relevant logs but it's very hard to display/attach them
in a sensible manner using this forum so I have tried to condense the
pertinent entries:
[#|2012-01-01T02:10:00.900+0000| 'BEING_DELIVERED' for timeout at Sun Jan 15
02:10:00 GMT 2012|#] [#|2012-01-03T05:56:42.104+0000| 'CREATED' for timeout
at Sun Jan 08 02:10:00 GMT 2012|#] [#|2012-01-04T06:05:07.334+0000| 'CREATED'
for timeout at Sun Jan 08 02:10:00 GMT 2012|#]
[#|2012-01-08T02:10:00.611+0000| 'BEING_DELIVERED' for timeout at Sun Jan 22
02:10:00 GMT 2012|#] [#|2012-01-11T05:21:26.866+0000| 'CREATED' for timeout
at Sun Jan 15 02:10:00 GMT 2012|#] [#|2012-01-13T05:38:13.968+0000| 'CREATED'
for timeout at Sun Jan 15 02:10:00 GMT 2012|#]
[#|2012-01-15T02:10:03.518+0000| 'BEING_DELIVERED' for timeout at Sun Jan 29
02:10:00 GMT 2012|#] [#|2012-01-25T04:28:52.044+0000| 'CREATED' for timeout
at Sun Jan 29 02:10:00 GMT 2012|#] [#|2012-01-29T02:10:02.388+0000|
'BEING_DELIVERED' for timeout at Sun Feb 12 02:10:00 GMT 2012|#]
[#|2012-02-08T04:21:41.509+0000| 'CREATED' for timeout at Wed Feb 08 04:21:42
GMT 2012|#] [#|2012-02-08T04:21:45.291+0000| 'BEING_DELIVERED' for timeout at
Sun Feb 19 02:10:00 GMT 2012|#] [#|2012-02-08T04:45:55.730+0000| 'CREATED'
for timeout at Sun Feb 12 02:10:00 GMT 2012|#]
[#|2012-02-12T02:10:01.324+0000| 'BEING_DELIVERED' for timeout at Sun Feb 26
02:10:00 GMT 2012|#] [#|2012-02-22T04:40:11.995+0000| 'CREATED' for timeout
at Wed Feb 22 04:40:12 GMT 2012|#] [#|2012-02-22T04:40:15.428+0000|
'BEING_DELIVERED' for timeout at Sun Mar 04 02:10:00 GMT 2012|#]
Am I right in saying the 'BEING_DELIVERED' entries are when the timeout is
scheduled and the 'CREATED' entries are when the timeout actually occurs?
For the most recent missed timeout on the 19th Feb you can see the timeout
was scheduled on 2012-02-08 but did not actually run on the 19th. It did run
however at 2012-02-22T04:40 when I restarted Glassfish.
[quote=mvatkina]You have the FINE logging enabled, don't you? Is it that the
next calculated date is wrong or the timeout is not called? It's really
strange that your test machine works correctly (and we had never seen any
problems on our tests).... forums_at_java.net wrote: > I updated the JDK and the
job ran on 2012-02-12 but didn't run on the > 19th > so it doesn't look like
a JDK version issue. > > > -- > > [Message sent by forum member 'buddypine']
> > View Post: http://forums.java.net/node/866262 > >[/quote]
--
[Message sent by forum member 'buddypine']
View Post: http://forums.java.net/node/866262