You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Glenn Nielsen <gl...@voyager.apg.more.net> on 2002/06/21 19:19:02 UTC
Tomcat 4.1 HEAD DefaultContext JNDI bug
I just built Tomcat 4.1 HEAD from CVS and get the following for JNDI
named resource defined in the server.xml <DefaultContext> for a Host.
2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
ct: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
ct: javax.naming.NameNotFoundException: Name mail is not bound in this Context
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat 4.1 HEAD DefaultContext JNDI bug
Posted by Glenn Nielsen <gl...@voyager.apg.more.net>.
Ok, thanks.
Remy Maucherat wrote:
>
> Glenn Nielsen wrote:
> > I just built Tomcat 4.1 HEAD from CVS and get the following for JNDI
> > named resource defined in the server.xml <DefaultContext> for a Host.
> >
> > 2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
> > ct: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
> > 2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
> > ct: javax.naming.NameNotFoundException: Name mail is not bound in this Context
>
> I noticed (yesterday) I had introduced bugs during my last cleanup (much
> needed, there were two notification schemes being used, etc). I'm
> working on it :)
>
> Remy
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Tomcat 4.1 HEAD DefaultContext JNDI bug
Posted by Remy Maucherat <re...@apache.org>.
Glenn Nielsen wrote:
> I just built Tomcat 4.1 HEAD from CVS and get the following for JNDI
> named resource defined in the server.xml <DefaultContext> for a Host.
>
> 2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
> ct: javax.naming.NameNotFoundException: Name jdbc is not bound in this Context
> 2002-06-21 12:07:46 NamingContextListener[/Tomcat-Apache/www.dev.kinetic.more.net/dbtags-examples]: Failed to bind obje
> ct: javax.naming.NameNotFoundException: Name mail is not bound in this Context
I noticed (yesterday) I had introduced bugs during my last cleanup (much
needed, there were two notification schemes being used, etc). I'm
working on it :)
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>