Hi Shreedhar
Thanks for your quick response.
Maybe I have made a mistake, it may caused by our legacy code, but after
fix this problem we still met the timer service failed to auto-migrate
problem, I will try to reproduce it and send out the steps.
BRs
//Jason
--------------------------------------------------
From: "Shreedhar Ganapathy" <Shreedhar.Ganapathy_at_Sun.COM>
Sent: Monday, February 02, 2009 1:13 PM
To: <users_at_glassfish.dev.java.net>
Subject: Re: EJB timer service can not automatically migration
> Hi Jason
> Wrote a separate note to you on the shoal user mailing list. In addition
> to that could you share exact steps to reproduce this problem?
>
> Thanks
> Shreedhar
>
> shockwave_115_at_hotmail.com wrote:
>> Hi
>> I continue to investigate this problem by turn on the log of "Group
>> Management Service", I found some error logs on "FailureNotification", I
>> don't know if it is the root cause the timer automatic migration failure.
>>
>> [#|2009-02-02T10:27:06.122+0800|INFO|sun-appserver9.1|ShoalLogger|_ThreadID=21;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>> Thread;instance2;|Sending FailureSuspectedSignals to registered Actions.
>> Member:instance2...|#]
>>
>> [#|2009-02-02T10:27:06.174+0800|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=21;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>> Thread;_RequestID=26e5a26b-7b1c-4eb9-be38-1be1c42a1ae7;|Exception in
>> thread "com.sun.enterprise.ee.cms.impl.common.Router Thread" |#]
>>
>> [#|2009-02-02T10:27:06.176+0800|WARNING|sun-appserver9.1|javax.enterprise.system.stream.err|_ThreadID=21;_ThreadName=com.sun.enterprise.ee.cms.impl.common.Router
>> Thread;_RequestID=26e5a26b-7b1c-4eb9-be38-1be1c42a1ae7;|java.lang.ClassCastException:
>> timer.TimerFailureNotificationAction cannot be cast to
>> com.sun.enterprise.ee.cms.core.FailureSuspectedAction
>> at
>> com.sun.enterprise.ee.cms.impl.common.Router.notifyFailureSuspectedAction(Router.java:299)
>> at
>> com.sun.enterprise.ee.cms.impl.common.SignalHandler.analyzeSignal(SignalHandler.java:120)
>> at
>> com.sun.enterprise.ee.cms.impl.common.SignalHandler.handleSignals(SignalHandler.java:103)
>> at
>> com.sun.enterprise.ee.cms.impl.common.SignalHandler.run(SignalHandler.java:85)
>> at java.lang.Thread.run(Thread.java:619)
>> |#]
>>
>> Does it mean the callback failed to perform the timer migration when it
>> got the SuspectedFailureNotification?
>>
>> BRs
>> Jason
>>
>> --------------------------------------------------
>> From: <glassfish_at_javadesktop.org>
>> Sent: Sunday, January 18, 2009 1:39 PM
>> To: <users_at_glassfish.dev.java.net>
>> Subject: Re: EJB timer service can not automatically migration
>>
>>> I think this is a very good question. I do not know where the automatic
>>> failover is done.
>>> Is that done by the DAS server???
>>> If the DAS server is down where is then the failover performed? We must
>>> be sure not to have a single point of failure in our system. If the DAS
>>> is single point of failure then the EJB timer is not feasable.
>>>
>>> I had a look at Quartz that can be performed from a Servlet.
>>> Is there somebody who has experience with Quartz vs EJB Timer on
>>> GlassFishV2?
>>> Where can I find more information about automatic failover of the EJB
>>> Timer in GlassFish?
>>>
>>> Thanks
>>> Jelte
>>> p.s. I cannot use GlassFishV3 since it is still prelude.
>>> [Message sent by forum member 'jeltejansons' (jeltejansons)]
>>>
>>> http://forums.java.net/jive/thread.jspa?messageID=326679
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>