|
From: Marco L. <m.l...@we...> - 2005-04-13 13:36:48
|
Hello to everyone,
we have finally made to build and run the 0.7.7-dev version of openjms.
We can make some clients connect to the server through http-tunneling.
In our configuration we would like to have the local jms-clients connect
to the bus through rmi and only remote clients connect through rmi but
we're not able to make rmi connections.
The clients crash when looking up through embedded jndi the Initial
context on default localhost (or local ip):1099 complaining with the
following error message:
Failed to create initial JNDI context:
javax.naming.ServiceUnavailableException [Root exception is
java.lang.NullPointerException]
If I make the lookup through the Http connector then everything works
during the look up but when the local client tries to connect to the
looked up Destination it crashes with the following exception:
javax.jms.JMSException
at
org.exolab.jms.client.net.JMSExceptionAdapter.adapt(JMSExceptionAdapter.java:79)
at
org.exolab.jms.server.net.RemoteServerConnection__Proxy.getConnectionId(RemoteServerConnection__Proxy.java:68)
at
org.exolab.jms.client.net.JmsConnectionStubImpl.getConnectionId(JmsConnectionStubImpl.java:126)
at
org.exolab.jms.client.JmsConnection.<init>(JmsConnection.java:176)
at
org.exolab.jms.client.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:284)
at
org.exolab.jms.client.JmsConnectionFactory.createConnection(JmsConnectionFactory.java:266)
at DurableSubscriber.main(DurableSubscriber.java:128)
JMS exception: javax.jms.JMSException
Are we missing something with the RMI configuration? Is it possible to
make Http, tcp and RMI coexist at this stage of development?
Thanx in advance,
M.
ps. I attach our openjms.xml file for further documentation.
|