Glassfish TimerService - Expunging timer after failed deliveries
On my glassfish installation I am running different TimerServices. In one I saw the problem that the TimerService stopped unexpected after running more than 20 hours.
In this situations a exeption is logged by the server like this one:
[#|2009-07-09T03:10:56.375+0200|INFO|sun-appserver2.1|javax.enterprise.system.container.ejb|_ThreadID=15;_ThreadName=p: thread-pool-1; w: 4;'1@@1247059844937@@server@@domain1' 'TimedObject = ScheduledWorkflowServiceImplementation' 'Application = myapp.ear-1.3.4' 'BEING_DELIVERED' 'PERIODIC' 'Container ID = 81721584505847814' 'Wed Jul 08 15:30:44 CEST 2009' '600000' ;2;|EJB5119:Expunging timer ['1@@1247059844937@@server@@domain1' 'TimedObject = ScheduledWorkflowServiceImplementation' 'Application = myapp.ear-1.3.4' 'BEING_DELIVERED' 'PERIODIC' 'Container ID = 81721584505847814' 'Wed Jul 08 15:30:44 CEST 2009' '600000' ] after [2] failed deliveries|#]
There is a Bugreport concerning this issue:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=4634
and also this discussion thread:
http://forums.java.net/jive/thread.jspa?messageID=219367
arround this toppic.
Now I will test if changing the TimerService settings in the EJB Containterconfiguration will solve the problem.
First I will change the following Params
- "Maximum Redeliveries" from "1" -> "16"
- "Redelivery Interval" from 5000 -> 30000
not sure if this will help....
Posted at 06:24AM Jul 09, 2009
Posted by: Ralph
Category: General