Also keep in mind, additional configuration parameters are required when
a cluster spans sub-nets or the internet. This configuration enables
virtual multicast wherever ip multicast is not possible.
Mohamed
Rogerio Maretti wrote:
> Hi,
>
> I think I have a network problem here, some packets sent to other machines didn't reach. I'm almost sure that the leader problem I had was because of this. I'm trying to solve the communication problem. After it I'm going to test the application again in different machines, If the problem persists I'll send you the logs.
>
> Thanks,
> Rogério Maretti
>
> ----- Original Message -----
> From: "Rogerio Maretti" <rogerio.maretti_at_eversystems.com.br>
> To: users_at_shoal.dev.java.net
> Sent: Quinta-feira, 10 de Abril de 2008 14h21min21s (GMT-0300) Auto-Detected
> Subject: leader problem
>
>
> Hi Shreedhar,
>
> I'm using shoal in the project I've been working at, related to fault tolerance. I'll have only CORE members (n), but only the leader will have the power to do things such as connecting to other systems, etc. When I test the application running many instances (members) in the same machine, the application works well, but when I test each instance running in different machines at the same network, the application doesn't work well, sometimes it elects more than one leader, which couldn't happen in my application logic. Do you have any idea of what is happening?
>
> I didn't change the configuration of ServiceProviderConfigurationKeys, I pass null.
> GMSFactory.startGMSModule(instanceName, "TEST_GROUP", GroupManagementService.MemberType.CORE, null);
>
> Thanks,
> Rogério Maretti
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_shoal.dev.java.net
> For additional commands, e-mail: users-help_at_shoal.dev.java.net
>
>