Yes, that appears to be my issue. Thank you very much for the input. By the way, I just queried the bug database, and see that there are a number of similar reports out there. They all seem to reference your suggestion of using a <Context> element though, and since we didn't have an explicit <Context> element at first, I'm going to look further into whether this is truly a bug, or just my misunderstanding of the relationships. And I'll pay more attention to the bug database next time I run across an issue like this.
Thanks again. Jay -----Original Message----- From: Philipp Taprogge [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 11:36 AM To: Tomcat Users List Subject: Re: JDBC/DBCP problems Hi! Burgess, Jay S wrote: > Thanks for the feedback. Maybe my problem does have something to do > with context visibility, but since I'm defining the resource within > SERVER.XML's <GlobalNamingResources>, I was under the impression that > these resources were available to all contexts. I had a similar problem. It seems, that if you auto-deploy a context by dropping a .war into tomcat's webapps, this context does not see the JNDI-Resources defined in the GlobalNamingResources section of the server.xml. I had to specify them explicitly in it's own <Context> section for my webapp. This problem seems to be limited to tomcat 4.x, since it vanished after I upgraded to tomcat5. HTH Phil -- And on the seventh day, He exited from append mode. (Book of create(2), line 255) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
