http://jira.jboss.com/jira/browse/JBAS-5009
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108190#4108190
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108190
___
jboss-user
Seems the HttpNamingContextFactory doesn't have to logic built into it to parse
multiple URLs.
Also, I've been looking at this code and the naming proxy you'll get won't have
automatic loadbalancing, failure detection and failover in it.
Probably the way to go is to use a loadbalancer. If you d
In this case I see:
javax.naming.NamingException: Failed to retrieve Naming interface [Root
exception is java.io.FileNotFoundException:
http://10.0.0.17:8080/invoker/HAJNDIFactory,http://10.0.0.100:8080/invoker/HAJNDIFactory]
at
org.jboss.naming.HttpNamingContextFactory.getInitialConte
I have host1 and host2.
java.naming.provider.url = http://host1:8080/invoker/HAJNDIFactory
I start client application, it connects to server and works. Then I stop host1,
and client application can't lookup new beans.
I look at NamingContext in the debug mode and see that it have
HttpInvokerPr
Try:
java.naming.provider.url=http://host1:8080/invoker/HAJNDIFactory,http://host2:8080/invoker/HAJNDIFactory
What allows HA-JNDI to find host2 is you don't list it like that is the
multicast autodiscovery feature. But if you use that, you'll get an RMI-based
proxy. So you'd need to list all
Try this. In your jndi.properties, use
| java.naming.factory.initial = org.jboss.naming.HttpNamingContextFactory
| java.naming.provider.url = http://yourhost:8080/invoker/HAJNDIFactory
I must confess I've never used that, but it follows the same pattern as HTTP
tunneling to the regular JND
Of course, I can use loadbalancer (Apache HTTP Server). But I want to use
HAJNDI based on client-side interceptor, without loadbalancer. It is possible?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009228#4009228
Reply to the post :
http://www.jboss.com/in
