geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Quintin Beukes (JIRA)" <>
Subject [jira] Commented: (GERONIMO-4906) DB connection problem
Date Thu, 15 Oct 2009 08:34:31 GMT


Quintin Beukes commented on GERONIMO-4906:

I remember dealing with a similar problem once. I've been trying to think which pool manager
this was, but am unable.

Though I do remember how it was solved. It was an an option (possible 2 separate once - not
sure) which routinely tested the actual connection, and if closed would remove it from the
pool. Also, before the connection is given to a requesting client it would also be tested
to ensure it's active, if not it would be removed and another connection tried - until one
could be found. If none could be found an exception is raised.

Maybe such an option is available? And if not, I definitely recommend it be added.

If this isn't available yet, the code that requests the connection could perhaps (even temporarily)
wrap the request in a method which has the above behavior (testing the connection and requesting
a new one if the test fails). The pool should automatically remove it when an exception is
raised, so I don't think this wrapper needs to worry about that.

> DB connection problem
> ---------------------
>                 Key: GERONIMO-4906
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: databases
>    Affects Versions: 2.0.1
>         Environment: Geronimo running on Windows server 2003 (Virtual Machine)
> Oracle 10g
> Driver jdbc
> Spring-Version: 2.0.2
> Hibernate-Version: 3.2.0.cr4
>            Reporter: Jean-Jacques Parent
>         Attachments: config.xml, Errors_samples.txt
> Your expertise on my problem will be helpful.
> Once a week, I get a DB connectivity problem with my application.
> No new DB transaction can be open. After a few minutes, the situation can come back as
normal, if not the Geronimo server has to be restarted.
> I ask our technicians about connectivity and performance, but they found nothing wrong.
> I give you the stack trace in attachment with the different kind of error message.
> You will see that it looks like a network problem, but maybe this could also be due to
a jdbc, timeout...? 
> My pool configuration is as follow
> Pool Min Size:25	 
> 	The minimum number of connections in the pool. The default is 0.
> Pool Max Size:140	 
> 	The maximum number of connections in the pool. The default is 10.
> Blocking Timeout: 5000	 (in milliseconds)
> 	The length of time a caller will wait for a connection. The default is 5000.
> Idle Timeout: 5	 (in minutes)
> 	How long a connection can be idle before being closed. The default is 15.
> Any help will be appreciate.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message