Re: Problems with 0.7.7.-dev RMI connector...
Marco Lettere <[email protected]>
| Newsgroups | gmane.comp.java.openjms.user |
|---|---|
| Message-ID | <[email protected]> |
Thank you very much Tim. We'll check it out asap. M. Tim Anderson wrote: >I've just checked in a fix for this. It should propagate through >to the public CVS in a few hours. > >When you run cvs update, you should pick up version 1.3 of: > modules/net/src/main/java/org/exolab/jms/net/connector/Request.java > >-Tim > > > >>-----Original Message----- >>From: openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >>[mailto:openjms-user-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf >>Of Marco Lettere >>Sent: Wednesday, 13 April 2005 11:30 PM >>To: [email protected] >>Subject: [openjms-user] Problems with 0.7.7.-dev RMI connector... >> >> >>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(JMSExcepti >>onAdapter.java:79) >> at >>org.exolab.jms.server.net.RemoteServerConnection__Proxy.getCon >>nectionId(RemoteServerConnection__Proxy.java:68) >> at >>org.exolab.jms.client.net.JmsConnectionStubImpl.getConnectionI >>d(JmsConnectionStubImpl.java:126) >> at >>org.exolab.jms.client.JmsConnection.<init>(JmsConnection.java:176) >> at >>org.exolab.jms.client.JmsConnectionFactory.createConnection(Jm >> >> >sConnectionFactory.java:284) > > >> at >>org.exolab.jms.client.JmsConnectionFactory.createConnection(Jm >> >> >sConnectionFactory.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. >> >> >> > > > >------------------------------------------------------- >SF email is sponsored by - The IT Product Guide >Read honest & candid reviews on hundreds of IT Products from real users. >Discover which products truly live up to the hype. Start reading now. >http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >_______________________________________________ >openjms-user mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/openjms-user > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click