[jboss-user] [Clustering/JBoss] - Re: HA-JNDI and JNDI for cluster access

"[EMAIL PROTECTED]" wrote : To continue your use case beyond what you wrote to include actual use of the context: | | Object foo = context.lookup("Foo"); | | then server context has connected to fails or is shut down | | Object bar = context.lookup("Bar"); | | 1) With case

[jboss-user] [Clustering/JBoss] - HA-JNDI and JNDI for cluster access

Hi, can anybody tell me what is difference between case1(1099) and case2(1100)? it seem both notation work for cluster-access by client. thanks in advance case1: Properties props = new Properties(); ... props.put("java.naming.provider.url", "server1:1099,server2:1099,server3:1099"); context = new

[jboss-user] [Beginners Corner] - java.naming.provider.url by HA-JNDI cluster client with 110

Hi, can anybody tell me what is difference between case1(1099) and case2(1100)? both notation mean the same? thanks in advance case1: Properties props = new Properties(); ... props.put("java.naming.provider.url", "server1:1099,server2:1099,server3:1099"); context = new InitialConte

[jboss-user] [Messaging, JMS & JBossMQ] - DLQHandler javax.naming.NameNotFoundException: XAConnectionF

Good Morning, can anybody help me? At the moment i have this Exception in my server.log 2007-06-20 08:57:20,792 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Initialization failed DLQHandler javax.naming.NameNotFoundException: XAConnectionFactory at org.jboss.ha.jndi.TreeHead.lookup(Tree