You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jean-Jacques Parent (JIRA)" <ji...@apache.org> on 2009/10/14 15:02:31 UTC
[jira] Created: (GERONIMO-4906) DB connection problem
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: 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770416#action_12770416 ]
Jean-Jacques Parent commented on GERONIMO-4906:
-----------------------------------------------
I am still investigating the origin of my problem, may be some additional informations:
I used a special oracle driver with trace functionalities. It was not possible to set a high level of logs because of bad performances but we have the same information: connection interrupted (stopped).
I succeeded to reproduce the problem in my development environment by unplugging the network cable of my server. Indeed, the following actions in the application after re-plugging the cable are giving: connection interrupted.
Some questions according to this kind of situation:
1 is this means that after a problem, maybe a network one, all the connection pool managed by Geronimo falls into an invalidate state and this pool will always give a connection even if this one is broken. (Unless this connection is removed by the idle timeout or by restarting the server)
2 Why the Geronimo pool does not killed those corrupted connexions?
3 is it a good idea to set the connection idle timeout to 0, in order to force the pool to kill the maximum of connections especially when those become unsafe?
We are still investigating the reasons why the connection pool become unsafe, but I don't understand why broken connections are still available in the pool...
> 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765975#action_12765975 ]
Quintin Beukes commented on GERONIMO-4906:
------------------------------------------
I remember now that I was using c3p0 with Hibernate. These were the options I was referring to:
http://www.mchange.com/projects/c3p0/index.html#configuring_connection_testing
> 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Quintin Beukes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765973#action_12765973 ]
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: 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765942#action_12765942 ]
Jean-Jacques Parent commented on GERONIMO-4906:
-----------------------------------------------
Is there a way to get trace from the jdbc ?
Is it possible to "manage" the connections from the pool, to see if one is in a wrong state and eventually to kill it?
See some similar post on http://www.nabble.com/Bad-JDBC-Connection-with-Oracle-td18079875s134.html
> 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.
[jira] Commented: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12766432#action_12766432 ]
Jean-Jacques Parent commented on GERONIMO-4906:
-----------------------------------------------
Ok, I will try to implement c3p0
I will give you a feed back as soon as possible.
> 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.
[jira] Updated: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Jacques Parent updated GERONIMO-4906:
------------------------------------------
Attachment: Errors_samples.txt
Different kind of errors
> 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: 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.
[jira] Updated: (GERONIMO-4906) DB connection problem
Posted by "Jean-Jacques Parent (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Jacques Parent updated GERONIMO-4906:
------------------------------------------
Attachment: config.xml
Connection pool configuration
> 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.