RMI/JNDI problem w/tomcat 3.3

[Mike Comb]

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:   
For additional commands: 
Troubles with the list: 

RE: RMI/JNDI problem w/tomcat 3.3

[Larry Isaacs]

I assume you noticed in the documentation that Tomcat 3.3
startup scripts ignore your CLASSPATH.  Did you modify
the tomcat.bat/tomcat.sh file to include the jndi.properties
file?  If so, what is the error you are seeing?

Cheers,
Larry

> -Original Message-
> From: Mike Comb [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 06, 2001 10:37 PM
> To: [EMAIL PROTECTED]
> Subject: 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.Registry
> ContextFactory
> 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:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>
> 

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

RE: RMI/JNDI problem w/tomcat 3.3

[Mike Comb]

Yes, I know it ignores the CLASSPATH.  I tried puting jndi.properties in my 
webapps classes directory as well as modifying tomcat.sh so it uses the 
system CLASSPATH.  Neither had any effect.  I am not getting any error, RMI 
just never starts up.  Has anybody gotten this to work with tc3.3?  Can 
someone try?  I want to know if this is a TC bug or just a configuration 
error with my setup.

Thanks,
-Mike

--On Friday, December 7, 2001 8:04 AM -0500 Larry Isaacs 
<[EMAIL PROTECTED]> wrote:

> I assume you noticed in the documentation that Tomcat 3.3
> startup scripts ignore your CLASSPATH.  Did you modify
> the tomcat.bat/tomcat.sh file to include the jndi.properties
> file?  If so, what is the error you are seeing?
>
> Cheers,
> Larry
>
>> -Original Message-
>> From: Mike Comb [mailto:[EMAIL PROTECTED]]
>> Sent: Thursday, December 06, 2001 10:37 PM
>> To: [EMAIL PROTECTED]
>> Subject: 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.Registry
>> ContextFactory
>> 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:   <mailto:[EMAIL PROTECTED]>
>> For additional commands: <mailto:[EMAIL PROTECTED]>
>> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Tomcat/Poolman/JNDI (was RMI/JNDI problem w/tomcat 3.3)

[Mike Comb]

OK, let me make this simpler since I have only received one response.  Has 
anybody gotten poolman 2.04 to work with tomcat 3.3 using JNDI?  How?

Thanks,
-Mike

--On Friday, December 7, 2001 10:08 AM -0800 Mike Comb <[EMAIL PROTECTED]> 
wrote:

> Yes, I know it ignores the CLASSPATH.  I tried puting jndi.properties in
> my webapps classes directory as well as modifying tomcat.sh so it uses
> the system CLASSPATH.  Neither had any effect.  I am not getting any
> error, RMI just never starts up.  Has anybody gotten this to work with
> tc3.3?  Can someone try?  I want to know if this is a TC bug or just a
> configuration error with my setup.
>
> Thanks,
> -Mike
>
> --On Friday, December 7, 2001 8:04 AM -0500 Larry Isaacs
> <[EMAIL PROTECTED]> wrote:
>
>> I assume you noticed in the documentation that Tomcat 3.3
>> startup scripts ignore your CLASSPATH.  Did you modify
>> the tomcat.bat/tomcat.sh file to include the jndi.properties
>> file?  If so, what is the error you are seeing?
>>
>> Cheers,
>> Larry
>>
>>> -Original Message-
>>> From: Mike Comb [mailto:[EMAIL PROTECTED]]
>>> Sent: Thursday, December 06, 2001 10:37 PM
>>> To: [EMAIL PROTECTED]
>>> Subject: 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.Registry
>>> ContextFactory
>>> 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:   <mailto:[EMAIL PROTECTED]>
>>> For additional commands: <mailto:[EMAIL PROTECTED]>
>>> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>>>
>>
>> --
>> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
>> For additional commands: <mailto:[EMAIL PROTECTED]>
>> Troubles with the list: <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Re: Tomcat/Poolman/JNDI (was RMI/JNDI problem w/tomcat 3.3)

[Mike Comb]

Sorry to keep replying to myself, but I have confirmed that this problem 
happens with tomcat 3.3 and the latest 3.3.1 development build.  Both 3.2.3 
and 3.2.4 work as expected.

I am getting rather frustrated here, I have the semi-common problem where 
tomcat 3.2.3's CPU load jumps to nearly 100% for no obvious reason, but I 
can't upgrade.  3.3 had this problem and 4.0.1 does not support 
loadbalancing which we have to have.

Help?
-Mike

--On Friday, December 7, 2001 11:48 AM -0800 Mike Comb <[EMAIL PROTECTED]> 
wrote:

> OK, let me make this simpler since I have only received one response.
> Has anybody gotten poolman 2.04 to work with tomcat 3.3 using JNDI?  How?
>
> Thanks,
> -Mike
>
> --On Friday, December 7, 2001 10:08 AM -0800 Mike Comb
> <[EMAIL PROTECTED]> wrote:
>
>> Yes, I know it ignores the CLASSPATH.  I tried puting jndi.properties in
>> my webapps classes directory as well as modifying tomcat.sh so it uses
>> the system CLASSPATH.  Neither had any effect.  I am not getting any
>> error, RMI just never starts up.  Has anybody gotten this to work with
>> tc3.3?  Can someone try?  I want to know if this is a TC bug or just a
>> configuration error with my setup.
>>
>> Thanks,
>> -Mike
>>
>> --On Friday, December 7, 2001 8:04 AM -0500 Larry Isaacs
>> <[EMAIL PROTECTED]> wrote:
>>
>>> I assume you noticed in the documentation that Tomcat 3.3
>>> startup scripts ignore your CLASSPATH.  Did you modify
>>> the tomcat.bat/tomcat.sh file to include the jndi.properties
>>> file?  If so, what is the error you are seeing?
>>>
>>> Cheers,
>>> Larry
>>>
>>>> -Original Message-
>>>> From: Mike Comb [mailto:[EMAIL PROTECTED]]
>>>> Sent: Thursday, December 06, 2001 10:37 PM
>>>> To: [EMAIL PROTECTED]
>>>> Subject: 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.Registry
>>>> ContextFactory
>>>> 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:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Re: Tomcat/Poolman/JNDI (was RMI/JNDI problem w/tomcat 3.3)

[Mike Comb]

OK, last time responding to myself.  I finally found the problem with TC3.3 
and it really was a CLASSPATH issue.  My database drivers where not in my 
CLASSPATH which apparently was keeping poolman from starting up which was 
in turn keeping RMI from starting.  Unfortunately nothing threw an 
exception or logged any errors until I tried to access the DB (at which 
point it threw an exception trying to connect to the RMI server).  I don't 
understand why nothing threw an exception while starting poolman or 
creating the pool, but I have learned to be very careful with paths with 
the new classpath layout under tc3.3.

Thanks,
-Mike


--On Friday, December 7, 2001 12:59 PM -0800 Mike Comb <[EMAIL PROTECTED]> 
wrote:

> Sorry to keep replying to myself, but I have confirmed that this problem
> happens with tomcat 3.3 and the latest 3.3.1 development build.  Both
> 3.2.3 and 3.2.4 work as expected.
>
> I am getting rather frustrated here, I have the semi-common problem where
> tomcat 3.2.3's CPU load jumps to nearly 100% for no obvious reason, but I
> can't upgrade.  3.3 had this problem and 4.0.1 does not support
> loadbalancing which we have to have.
>
> Help?
> -Mike
>
> --On Friday, December 7, 2001 11:48 AM -0800 Mike Comb
> <[EMAIL PROTECTED]> wrote:
>
>> OK, let me make this simpler since I have only received one response.
>> Has anybody gotten poolman 2.04 to work with tomcat 3.3 using JNDI?  How?
>>
>> Thanks,
>> -Mike
>>
>> --On Friday, December 7, 2001 10:08 AM -0800 Mike Comb
>> <[EMAIL PROTECTED]> wrote:
>>
>>> Yes, I know it ignores the CLASSPATH.  I tried puting jndi.properties in
>>> my webapps classes directory as well as modifying tomcat.sh so it uses
>>> the system CLASSPATH.  Neither had any effect.  I am not getting any
>>> error, RMI just never starts up.  Has anybody gotten this to work with
>>> tc3.3?  Can someone try?  I want to know if this is a TC bug or just a
>>> configuration error with my setup.
>>>
>>> Thanks,
>>> -Mike
>>>
>>> --On Friday, December 7, 2001 8:04 AM -0500 Larry Isaacs
>>> <[EMAIL PROTECTED]> wrote:
>>>
>>>> I assume you noticed in the documentation that Tomcat 3.3
>>>> startup scripts ignore your CLASSPATH.  Did you modify
>>>> the tomcat.bat/tomcat.sh file to include the jndi.properties
>>>> file?  If so, what is the error you are seeing?
>>>>
>>>> Cheers,
>>>> Larry
>>>>
>>>>> -Original Message-
>>>>> From: Mike Comb [mailto:[EMAIL PROTECTED]]
>>>>> Sent: Thursday, December 06, 2001 10:37 PM
>>>>> To: [EMAIL PROTECTED]
>>>>> Subject: 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.Registry
>>>>> ContextFactory
>>>>> 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:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>