Greetings all. We are running 4.0.1sp1 on two clustered servers (win 2k). Server1 starts and has HA-JNDI and JMS running. Our application logs login attemtps via an MDB. When the user logs in on Server1 everything works fine. When they try to login on Server2 we get javax.naming.NameNotFoundException: ConnectionFactory not bound. I read the following in the HowToConfigureMDBsToSubscribeToATopic wiki
This procedure can not be used as-is with JBossAS 4.0.2. Because of a bug in HA-JNDI auto-discovery, the client is not able to look up the topic. Until this issue is fixed, you should use the following JNDI properties java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory #java.naming.provider.url=192.168.4.150:1100 <--- comment out this line and update it accordingly java.naming.factory.url.pkgs=org.jboss.naming Is this a problem in 4.0.1sp1 as well? Should the comment read uncomment rather than comment since the line is already commented out? Thanks! Earnie! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926534#3926534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926534 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
