How to enable these two features? I didn't see any specification for this
part.
When I do prototype on one machine with two instances, I just to use the
default configuration, and the timer service can migrate from the failure
node to the other automatically.
BRs
//Jason
--------------------------------------------------
From: "Marina Vatkina" <Marina.Vatkina_at_Sun.COM>
Sent: Saturday, February 21, 2009 9:10 AM
To: <users_at_glassfish.dev.java.net>
Subject: Re: EJB timer service can not automatically migration
> Jason,
>
> Did you enable timer migration? If yes, you might also need to enable
> delegated transaction recovery in order to automatically migrate timers.
>
> thanks,
> -marina
>
> shockwave_115_at_hotmail.com wrote:
>> Hi
>>
>> When I look into the source code, I found the timer migration is invoked
>> by
>> AdminEventMulticaster.multicastEvent(AdminEvent event), so does it means
>> the
>> node failure event is monitored by DAS instead of other instance? If so
>> how
>> can I achieve the HA if DAS crashed?
>>
>> And the automatically migration problem is still there, I don't know how
>> to
>> do further investigation, I stop one instance on node one, I can see
>> nothing
>> showed in the logs of instance two on the node two.
>>
>> For my understanding, at least instance two should have the heartbeat
>> with
>> instance one, so when instance one crashed, instance two can know it. If
>> so,
>> why use multicast?
>>
>> BRs
>> Jason
>>
>> ---------------------------------------------------------------------
>> 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
>
>