Greetings,
as some of you know there have been previous discussions on the list
about the responsibility for validation of discarded Connection instances
in the object pools in OJB's default ConnectionManagerPooledImpl and
ConnectionManagerDBCPImpl.
A user-submitted patch applied to OJB's pooling
Is it possible to disable connection pooling in ojb ?
I'm using only one jdbc connection at the same time and do not want
to bother with the validationQuery that is database specific.
Regards,
Guillaume
-
To unsubscribe, e
Thanks, Armin
Guillaume
-Message d'origine-
De : Armin Waibel [mailto:[EMAIL PROTECTED]
Envoye : vendredi 13 fevrier 2004 10:12
A : OJB Users List
Objet : Re: Connection pooling
Hi,
Guillaume Nodet wrote:
Is it possible to disable connection pooling in ojb
was Connection is closed 13-Feb-2004
12:07:40 INFO [ CPS-Promotion]
slayer.ConnectionFactoryPooledImpl
-
-Original Message-
From: Kollivakkam R. Raghavan [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 12, 2004 4:53 PM
To: 'OJB Users List'
Subject: Connection pooling and HSQL
I am using OJB with HSQL and the following connection descriptor in a
Struts based web application. I very frequently see a message saying
that the connection was closed and destroy object was called. It
appears as if the connection pooling is not working as it should. Am I
missing a setting
Hi,
I am using version 0.9.8 and have set up JNDI and connection pooling in
my repository.xml file. The problem is that it seems the connection
pooling is not working. Each time it gets a new connection. It works
fine when I don't use JNDI. I was wondering if anyone has had any issues
What kind if environment are you in right now? I mean, what is the
behind the scenes system handling connections, pooling, and JNDI?
For example I primarily use OJB in servlet/J2EE engines, so all of that
stuff is handled by the container. I've had some connection pooling
problems with Orion
