Re: connection pooling with servlets

I've fixed the problem.  Looked like there was a conflict between the
MyApp.war/META-INF/context.xml and the
Tomcat/Catalina/localhost/MyApp/context.xml

Thanks for the reply.

> -----Original Message-----
> From: pgsql-jdbc-owner@postgresql.org [mailto:pgsql-jdbc-
> owner@postgresql.org] On Behalf Of Guy Rouillier
> Sent: Friday, April 28, 2006 13:33
> To: pgsql-jdbc@postgresql.org
> Subject: Re: [JDBC] connection pooling with servlets
>
> J. wrote:
> > I am a novice, but thought it would make more sense to post this
> > here.  I'm trying to write a basic webstore app for a school project
> > and I'm having trouble getting more than one servlet to access the
> > database connection.  I tried the method described on the PostgreSQL
> > site - as I understood it.  That entailed opening a connection in
one
> > servlet and then having code like this in other servlets that need
> > connections:
>
> Don't attempt to put your datasource in the session.  Use a database
> pool instead, and then just do a JNDI lookup to obtain a connection
> wherever you need it.  If you are using Tomcat as your servlet
> container, it has built-in support for datasources.  Post back if you
> need help in configuring that.
>
> --
> Guy Rouillier
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match