Thanks Nikola, That was the issue. For the rest of my query, go to the beginning of this thread, but here is the synopsis:
- If you do not put in a validation query when creating a data source under the Tomcat 4.1.12 manager/admin web app, you will have an empty value for the validationQuery parameter and your attempted accessing of a connection will go to Never-Never Land (an apparent infinite loop). I consider this a bug, primarily because Tomcat itself generated the XML, but also because the code should handle intelligently the absence of a value for a named parameter. At the very least, an exception should be thrown! If the consensus is that this is a bug to be reported, how do I go about doing that? Thanks, Steve ----- Original Message ----- From: "Nikola Milutinovic" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, October 10, 2002 1:33 AM Subject: Re: PostgreSQL JNDI resource under Tomcat 4.1.12 problem > > Server.xml: This portion exists under the GlobalNamingResources element > > under Server; the only pieces changed are the username and password.-) > > > > <Resource name="jdbc/election" scope="Shareable" > > type="javax.sql.DataSource"/> > > <ResourceParams name="jdbc/election"> > > <parameter> > > <name>validationQuery</name> > > <value></value> > > </parameter> > > Should this be empty? If you do not have a connection validation query, then remove this or put something quick and small. I'm not saying that is the problem, but most of my expirience (and others, too) can be described as getting "null" object from JNDI, not hanging. > > Nix. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
