This content has been marked as final.
Show 4 replies
-
1. Re: How to Determine (HA-) Jndi port at runtime?
kiran222 Dec 15, 2004 4:46 PM (in response to ckmod)
The HA-JNDI-Port is always the 1100 (unless configured otherwise). Right? -
2. Re: How to Determine (HA-) Jndi port at runtime?
ckmod Dec 21, 2004 3:33 AM (in response to ckmod)We have configured different ports since we are running multiple jboss instances on one piece of hardware. Therefore the port is not always 1100.
-
3. Re: How to Determine (HA-) Jndi port at runtime?
jaco.joubert Feb 4, 2005 2:44 AM (in response to ckmod)Suppose you have figured it out by now, but you could always query the 'Port' attribute of the 'jboss:service=HAJNDI' MBean through the local MBeanServer.
-
4. Re: How to Determine (HA-) Jndi port at runtime?
paxtor Feb 4, 2005 8:12 AM (in response to ckmod)I think it's always neccesary to know where the HAJNDI ports and nodes are. You can configure clients to connect with a list of HAJNDI services. If one fails, the client try to continue with the next.
i.e.java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=localhost:1100,localhost:1200
For your code, access to the cluster is now transparent.
If you are going to change the cluster, just you'll need to change the
configuration of the client