I'm not sure how it is deployed if you set @...Binding.
But you should see in the jmx-console JNDI-View how the bean is bind to the global context and adjust it
thank you for your answer.
I know what is the bind name of my ejb
+- SearchServiceBean (class: org.jnp.interfaces.NamingContext) | +- local (proxy: $Proxy374 implements interface com.neptuny.cpit.dh.core.SearchServiceLocalInterface,interface org.jboss.ejb3.JBossProxy) | +- remote (proxy: $Proxy373 implements interface com.neptuny.cpit.dh.core.SearchServiceRemoteInterface,interface org.jboss.ejb3.JBossProxy)
The problem seems to be in the HAJNDI.
In fact let's suppose that the node nvm1 is down and nvm2 is up and run:
- If I lookup the object with PROVIDER_URL = jnp://nvm1:1299 , I get the same exception above
- If I lookup the object with PROVIDER_URL = jnp://nvm2:1299, everything works fine.