[
https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12828045#action_12828045
]
Jean-Jacques Parent commented on GERONIMO-4906:
-----------------------------------------------
I am using c3p0 in production since december 2009.
Still have some 'connection closed' but those are captured by c3p0 and removed
from the pool.
So Still have the problem but under control. Our Web application does not crash
anymore.
It seems that only one connection from the pool was corrupted but this one was
always given to the application...
Still investigating the origin of the problem. We will try a new version of the
jdbc driver (11g).
Anyway you can close this issue unless you have more ideas.
Thanks for the c3p0 suggestion, it saved the situation
> DB connection problem
> ---------------------
>
> Key: GERONIMO-4906
> URL: https://issues.apache.org/jira/browse/GERONIMO-4906
> 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 10.2.0.1
> 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.
