users@glassfish.java.net

Re: Persistent timers problem

From: <forums_at_java.net>
Date: Wed, 5 Oct 2011 12:03:19 -0500 (CDT)

Sahoo, do you by any chance undeploy with keepstate=true? If not, may be
there are other timers involved, or the undeploy didn't really happen, so the
timers were not removed, but the new load is done via deploy, and a new app
id is being created - you can check for the appid in the timer table vs. the
value stored in the domain.xml under the corresponding <application> entry
(let me know if it is not stored there - that would explain why the timers
are left behind).

 

-marina


--
[Message sent by forum member 'mvatkina']
View Post: http://forums.java.net/node/847384