tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chonsiu208" <chonsiu...@hotmail.com>
Subject Re: Connection Pooling with different databases problems
Date Thu, 03 May 2001 15:18:39 GMT
thanks  a lot Kium !! I will try it !!

chonsiu  : )
----- Original Message -----
From: Winfried Klum <klum@bison-soft.de>
To: <tomcat-user@jakarta.apache.org>
Sent: Thursday, May 03, 2001 6:06 PM
Subject: Re: Connection Pooling with different databases problems


> First try to upgrade to poolman2.0 and use the Datasource Access method.
> I have tested only the 2.0 release.
> Here's how to get a connection,
> code (sample from original doc) looks like this:
>
> // Get a Connection
> DataSource ds = PoolMan.findDataSource("JNDINameOfMyPool");
> Connection con = null;
> con = ds.getConnection();
> // ... etc. ...
>
> This works for me.
>
> There's actually no JNDI involved I think, the codesnippet is misleading
> here.
> Getting the database Driver with class.forName, I have encountered some
> access problems when using multiple web-apps in the servlet container
> (also with web-apps hwo aren't using poolman at all).
>
> Best regards,
>  Winfried
>
> >
> > hi kium,
> >
> > I am using poolman1.4.1 to serve more than one database(to run with
> > different servlets) with traditional JDBC methods.................does
it
> > mean I can solve those "general error", "access violation(0xc0000005)"
> > problem by using JNDI for Driver-Access  ?
> >
> > ----- Original Message -----
> > From: Winfried Klum <klum@bison-soft.de>
> > To: <tomcat-user@jakarta.apache.org>
> > Sent: Thursday, May 03, 2001 2:26 PM
> > Subject: Re: Connection Pooling with different databases problems
>

Mime
View raw message