Hi
On Feb 25, 2009, at 12:08 AM, glassfish_at_javadesktop.org wrote:
> Hi,
> I've been following this discussion because I have the exact same
> problem. A brutal restart of one cluster node causes the ejb-timers
> to get stucked on that node. In my case failover does work if I only
> kill the java processes on one node.
> The result of the mcastsniffer is a success (9 rows of log output),
> test-mcastsniffer:
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
> [java] Here's some multicast data
> [java]
>
> Does this mean that Multicast is enabled and that the automatic
> failover of timers should work? No other configurations to be made?
Yes . in a cluster setup no other extra config needed for automatic
timer migration
thanks
-vivek
> My setup is four vmware linux machines, 2 DAS + 2 Payloads, running
> SGCS 1.5 (build b60g-fcs). The next step for us will be to create
> some code ourselves, but it would be nice to have the correct setup
> - if possible.
>
> Best regards
>
> Fredrik Olsson
> [Message sent by forum member 'frolsson' (frolsson)]
>
> http://forums.java.net/jive/thread.jspa?messageID=333698
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>