rmi RemoteException from Tomcat to JBossMQ

[ehansen]

Hello, I am trying to connect to a JBossMQ (JBoss 3.2.1) from within Tomcat 4.1.x or 5.0.x. The following code WORKS great from within Tomcat 4.0.6 but fails in the later versions of Tomcat...

Properties properties = new Properties();
properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
properties.put(Context.PROVIDER_URL, jnp://localhost:1099");
properties.put(Context.URL_PKG_PREFIXES, org.jboss.naming:org.jnp.interfaces");
properties.put(Context.SECURITY_PRINCIPAL, "jmsuser");
properties.put(Context.SECURITY_CREDENTIALS, "jmsuserpassword");
jmsContext = new InitialContext(properties);

Object connFactory = jmsContext.lookup("ConnectionFactory");
//... make jms queue and topic connection


the exception thrown (at jmsContext.lookup...) is:
RemoteException occurred in server thread
javax.naming.CommunicationException [Root exception is java.rmi.ServerException: RemoteException
occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.net.MalformedURLException: no protocol: Files/Crystal]

The "Files/Crystal" part of the error is a bit odd... it is part of the path to both the Tomcat installation and the JBoss installation (c:\Program Files\Crystal Stuff\...)

Any clues or leads is GREATLY appreciated!!
Thanks
Eric-

p.s. If there is another way to get the JMS connection from within Tomcat, an example would be great. If investigated the <resource-env-ref> route in the web.xml and server.xml but have not found any info on how to do that with JBossMQ.

[adrian.brock]

http://jboss.org/wiki/Wiki.jsp?page=JBossInstallation

Point 3
Unzip the sources into a directory that does not contain spaces anywhere in the path. (Meaning do not put it in C:\Program Files\bla)

We gave up trying to workaround Sun's jvm problems with windows paths a while ago.

[ehansen]

Thanks for the reply....
It is interesting that it works with Tomcat 4.0.6. Any idea why? Is there any workaround you can think of? We are pretty committed to the current deployment (there would be major ripple effects of changing it).

Thanks
Eric-

[adrian.brock]

And it was Adrian "Demi god" Brock that added that comment. :-)

You probably saw examples from the client configuration.

[ehansen]

It really works in Tomcat 4.0.6. I've been using it in production for a while now.

I've copied the same set of JBoss client jars that I'm using in 4.0.6 (common/lib folder) into the newer Tomcat's common/lib folders and it's no good.

Eric-

[ehansen]

Is there a way to access the Topic and Queue connections using Tomcat's internal jndi?? (I've seen references to <resource-env-ref> entries in the web.xml file to do such things) Or would it experience the same 'path' problem?

Thanks,
Eric-