You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Mike Comb <mc...@softcoin.com> on 2001/12/07 04:37:22 UTC

RMI/JNDI problem w/tomcat 3.3

Hi, I am trying to upgrade from tomcat 3.2.3 to 3.3 and I am having a 
problem.  Under 3.2.3 I was able to get tomcat to act as a JNDI server by 
adding a jndi.properties file to my classpath with the following contents...

------------
java.naming.factory.initial=com.sun.jndi.rmi.registry.RegistryContextFactory
java.naming.provider.url=rmi://localhost:1099
------------

an RMI server was automatically started on port 1099 as part of the tomcat 
process.  With TC 3.3 this no longer works.  I found a couple of old emails 
mentioning that tc3.3 may not be able to open that file, but no real 
details.  Can someone please tell me what is going on and if there is any 
work around?

Thanks,
-Mike


--
To unsubscribe:   <ma...@jakarta.apache.org>
For additional commands: <ma...@jakarta.apache.org>
Troubles with the list: <ma...@jakarta.apache.org>