-
1. Re: JNDI provider and backup servers
gaohoward Mar 23, 2012 3:01 AM (in response to ejb3workshop)Re: Is it possible to configure the servers to only accept JNDI requests once they out of stand-by mode ?
If a backup server becomes live, it should be able to get connected via JNDI. In other words a backup won't register its resources with JNDI unless it becomes live server.
If you use a 'HA' connection factory you should get load balancing capability.
Howard
-
2. Re: JNDI provider and backup servers
ejb3workshop Mar 23, 2012 4:46 AM (in response to gaohoward)My problem is that I am able to connect to the backup before it becomes alive while it is still in stand-by. In this state none of the connection factories and destinations have been deployed, and hence cannot be found. So when connected to a backup-node in stand-by state I am getting NameNotFoundExceptions.
-
3. Re: JNDI provider and backup servers
john.dorien Apr 11, 2013 12:42 PM (in response to ejb3workshop)Same situation here. Need to provide JNDI names of multiple HornetQ servers (live/backup setup). But backup server accepts JNDI connections and fails to lookup resources with NameNotFoundException (because it is backup and resources are not in JDNI yet).
Why does backup server even accepts JNDI connections where it is not fully started? And once it does why not to publish queues/connection factories for clients? Client can get connection factory from backup server and factory should lookup active HornerQ server (transparently to the client).
@Alex: did you ever find solution to this issue?