-
1. Re: Is this expected clustering behaviour and if so, why??
Sacha Labourey Dec 3, 2002 10:26 AM (in response to Chuck Moore)more or less yes. When the client cannot reach a JNDI server, it will try to discover a HA-JNDI service. Which is why you see this behaviour.
Cheers,
sacha -
2. Re: Is this expected clustering behaviour and if so, why??
Chuck Moore Dec 3, 2002 5:28 PM (in response to Chuck Moore)Thanks for that. My collegue say "bugger". However, here's another question. If we have 2 clusters, one with the 4 nodes identified in the original question and another with 4 different nodes, how can we stop the second cluster's nodes from responding to a request destined for nodes in cluster 1. Our setup has all nodes in all clusters listening on port 1100 but different ip addresses.
Note: in this scenario, all nodes in cluster 1 are down.
Cheers -
3. Re: Is this expected clustering behaviour and if so, why??
Sacha Labourey Dec 5, 2002 12:45 PM (in response to Chuck Moore)Take a recent CVS snapshot: you will then be able to define the "jnp.partitionName" system property and set the appropriate partition name. Client side Automatic Discovery will then restrict its discovery to this partition only.
To entirely disable the AD feature, set the jnp.disableDiscovery setting.
Cheers,
sacha