Remote clients unable to find jndi name.

[norm32]

I've written a JMS client that works fine when I run it from the local machine. When I try to run it from a remote machine, I am unable to get a ConnectionFactory. Here is the code snippet that is failing:

topicConnectionFactory=(TopicConnectionFactory)jndiContext.lookup("java:/XAConnectionFactory");

the NamingException.getMessage() produces - "jnp"
real descriptive :).

I also tried:

topicConnectionFactory=(TopicConnectionFactory)jndiContext.lookup("TopicConnectionFactory");

the NamingException.getMessage() produces - "null"

I'm thinking that I must have something missing in my jboss.jcml

Any help would be greatly appreciated.
Norm

[yzhang_jboss]

What version of JBoss are you using? Try using "ConnectionFactory" as the JNDI look up string and see if it solves your problem. eg:
// Get the connection factory
TopicConnectionFactory topicFactory =
(TopicConnectionFactory)context.lookup("ConnectionFactory");


Cathy

[norm32]

Upon further invetigation, I see that I am getting a CommunicationException.

javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused: connect]

For some reason its trying to go to the localhost. I'm sure the context properties are correct.

prop.put(Context.INITIAL_CONTEXT_FACTORY,"org.jnp.interfaces.NamingContextFactory");
prop.put(Context.URL_PKG_PREFIXES,"org.jboss.naming:org.jnp.interfaces");
prop.put(Context.PROVIDER_URL, "jnp://10.0.0.107:1099/");


jndiContext=new InitialContext(prop);

Norm

[yzhang_jboss]

Do you have to use "jnp://" setting? Can you just use
prop.put(Context.PROVIDER_URL, "10.0.0.107:1099");
I assume that you are writing a plain JMS client, not a bean that sends out messages through your local container to a topic running on a remote machine.

[ecomba]

I have this problem too. I don´t think the solution is putting the ip address of the machine you want to access, as we face the same problem using the ip or the resolved name.... :(

[hchirino]

You can bypass JNDI if you need to:

Properties props = new Properties();
props.setProperty(OILServerILFactory.SERVER_IL_FACTORY_KEY, OILServerILFactory.SERVER_IL_FACTORY);
props.setProperty(OILServerILFactory.CLIENT_IL_SERVICE_KEY, OILServerILFactory.CLIENT_IL_SERVICE);
props.setProperty(OILServerILFactory.PING_PERIOD_KEY, "1000");
props.setProperty(OILServerILFactory.OIL_ADDRESS_KEY, "localhost");
props.setProperty(OILServerILFactory.OIL_PORT_KEY, "8090");

QueueConnectionFactory cf = new SpyConnectionFactory(props);
QueueConnection c = cf.createQueueConnection();

---- OR -----

Properties props = new Properties();
props.setProperty(UILServerILFactory.SERVER_IL_FACTORY_KEY, UILServerILFactory.SERVER_IL_FACTORY);
props.setProperty(UILServerILFactory.CLIENT_IL_SERVICE_KEY, UILServerILFactory.CLIENT_IL_SERVICE);
props.setProperty(UILServerILFactory.PING_PERIOD_KEY, "1000");
props.setProperty(UILServerILFactory.UIL_ADDRESS_KEY, "localhost");
props.setProperty(UILServerILFactory.UIL_PORT_KEY, "8091");

QueueConnectionFactory cf = new SpyConnectionFactory(props);