You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by bhaskar <bh...@yahoo-inc.com> on 2006/09/08 07:17:34 UTC

JNDI context in ServletContextListener

Hi,
I am using tomcat 5.0.18. Our application is doing the JNDI lookup in the
listener. During tomcat startup when i try to get the db connection, i get
following error:
Name OracleDev not bound to this context
 
This is not consistent but it happens quite often.
 
In the tomcat-user list, i found the discussion on the similar
issue(http://marc.theaimsgroup.com/?l=tomcat-user
<http://marc.theaimsgroup.com/?l=tomcat-user&m=104438035321814&w=2>
&m=104438035321814&w=2) but i didnt' find any resolution on this. 
 
Can some one please tell me on whether doing the JNDI lookup in the Listener
is the right recommendation ?
 
Thanks in Advance,
Bhaskar

Re: JNDI context in ServletContextListener

Posted by Mark Thomas <ma...@apache.org>.
bhaskar wrote:
===========================
> 
> Does it mean that it will solve my problem if I move from Tomcat 5.0.x to
> Tomcat 5.5 ?

Probably.

It it is a bug there is a much greater chance of it getting fixed in
5.5.x than 5.0.x.

Mark

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: JNDI context in ServletContextListener

Posted by bhaskar <bh...@yahoo-inc.com>.
Hi,
Below bug is similar to the issue which I am facing:
http://issues.apache.org/bugzilla/show_bug.cgi?id=30079
 
bug says:
============================
DefaultContext JNDI behavior was a bit shaky with a few Tomcat releases, so
it 
could be your issue is valid.  However:
- DefaultContext is gone altogether in Tomcat 5.5, replaced with a different

mechanism,
- JNDI resources work fine for both normal Contexts and via 
GlobalNamingResources/ResourceLink: either one of those is a better approach

and more encouraged than using DefaultContext,
- Several Tomcat versions on the 5.0.x branch have been released since, so
if 
you really must keep using DefaultContext you could try these later versions
============================

Does it mean that it will solve my problem if I move from Tomcat 5.0.x to
Tomcat 5.5 ?

Please clarify

Thanks 
Bhaskar


> -----Original Message-----
> From: bhaskar [mailto:bhaskar@yahoo-inc.com] 
> Sent: Friday, September 08, 2006 10:48 AM
> To: users@tomcat.apache.org
> Subject: JNDI context in ServletContextListener
> 
> Hi,
> I am using tomcat 5.0.18. Our application is doing the JNDI 
> lookup in the listener. During tomcat startup when i try to 
> get the db connection, i get following error:
> Name OracleDev not bound to this context
>  
> This is not consistent but it happens quite often.
>  
> In the tomcat-user list, i found the discussion on the 
> similar issue(http://marc.theaimsgroup.com/?l=tomcat-user
> <http://marc.theaimsgroup.com/?l=tomcat-user&m=104438035321814&w=2>
> &m=104438035321814&w=2) but i didnt' find any resolution on this. 
>  
> Can some one please tell me on whether doing the JNDI lookup 
> in the Listener is the right recommendation ?
>  
> Thanks in Advance,
> Bhaskar
> 


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org