[jira] [Commented] (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13096686#comment-13096686 ] Radim Kolar commented on GERONIMO-4222: --- This ticket should be closed as fixed. I havent seen this error too. It works as expected now. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: PGtrial.patch, before and after wasce restart.txt, > connector.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927974#action_12927974 ] David Frahm commented on GERONIMO-4222: --- FYI -- Since my original post opening this issue we have upgraded to WASCE 2.1.1.3, and also RHEL 5.3. Its been many months, and we have not seen the specific error I described even once. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758103#action_12758103 ] Jack Cai commented on GERONIMO-4222: Thanks Forrest for trying out the patch! Guess the problem is because you still have some tranql-connector-1.4.jar in your repo which get loaded by the server (each vendor RAR contains a copy of this jar). Once we replace all the 1.4 jars with the updated jars, the problem shall go away. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757938#action_12757938 ] Forrest Xia commented on GERONIMO-4222: --- Results of some tries: 1. Derby ones work 2. PostgreSQL local one works 3. MySQl local one works However, there are some strange classloader problem when I am trying application-wide datasource. If the classloader behavior keeps as default(parent first), then PostgreSQL and MySQL local datasource cannot be created, and throw an exception as below: org/tranql/connector/jdbc/AbstractLocalDataSourceMCF.(Ljavax/sql/ConnectionPoolDataSource;Z)V java.lang.NoSuchMethodError: org/tranql/connector/jdbc/AbstractLocalDataSourceMCF.(Ljavax/sql/ConnectionPoolDataSource;Z)V at org.tranql.connector.postgresql.PGSimpleLocalMCF.(PGSimpleLocalMCF.java:34) So I add to the deployment plan and then they work fine! > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757852#action_12757852 ] David Jencks commented on GERONIMO-4222: Jack, I was working on the sqlstate exception sorter and just implemented ConnectionPoolDataSource wrapping before I saw your work. I'll compare our approaches and look at the vendor wrappers tomorrow. Radim, I haven't looked into this in a long time, but I think that the standard behavior for uncommitted work when putting a connection back in the pool is to commit it. However, the problem we are dealing with here is that on a connection error, after removing the connection from the pool so it won't be used ever again, we are not trying to rollback work on it before destroying it. If we could tell if the connection was actually still usable, we wouldn't close it at all if the rollback could succeed... so two things to do are to improve our decision of when to close the connection (using a ConnectionPoolDataSource, and a better ExceptionSorter) and trying to rollback before destroy just in case we were wrong about needing to destroy the connection. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757662#action_12757662 ] Radim Kolar commented on GERONIMO-4222: --- Before returning connection from client back to pool connection manager is expected to do rollback() on it, isn't it? Best method would be if rollback fails, drop connection. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, PGtrial.patch, > stacktrace.txt, tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756858#action_12756858 ] David Jencks commented on GERONIMO-4222: Absolutely the best solution for this kind of problem is to wrap a PooledDatasource rather than a driver. I couldn't find any when I started on tranql :-) You should be able to make an AbstractPooledDatasourceMCF similar to the AbstractXADatasourceMCF but using locat tx. I don't think that only rejecting a few known exceptions is necessarily a good idea. For the generic ra I implemented a new exception sorter that allows exceptions with SQLCode from a list. However I suspect the list of non-fatal SQLCOdes could be a lot more comprehensive. Can anyone find the list in the ansi or x/open specs? > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, PGtrial.patch, > stacktrace.txt, tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756410#action_12756410 ] Forrest Xia commented on GERONIMO-4222: --- I verified that the modified "tranql-connector-postgresql-common-1.1.jar" works for tranql's postgresql local adapter. Once db error is fixed, the geronimo server can rebuild connection to the postgresql database. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, PGtrial.patch, > stacktrace.txt, tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755804#action_12755804 ] David Jencks commented on GERONIMO-4222: Could you show the code you are using? I'm not entirely sure I think that a property file is easier to update than java code. You still have to repack everything and make sure you have it the right place and the right copy it seems to me that rebuilding the project might be easier and it is certainly much more friendly to tracking what code you are using. So, without more discussion I'd be much more in favor of not having a configurable exception sorter but just getting it right for postgres. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt, > tranql-connector-postgresql-common-1.1.jar > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754499#action_12754499 ] Radim Kolar commented on GERONIMO-4222: --- Can you get this bug fixed? Its major reliability problem. Tomcat is using Jakarta commons DBCP and do not suffers from this problem. Is there way to use DBCP in Geronimo? > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740370#action_12740370 ] Forrest Xia commented on GERONIMO-4222: --- More findings about db connection regeneration problem. 1. the general tranql adapter has the problem(except that the db vendor is DB2) 2. tranql-connector-mysql-local has the problem So I suspect if all of vendor local adapter has the problem. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733655#action_12733655 ] Forrest Xia commented on GERONIMO-4222: --- Does some testing on this issue. Conclude that: 1. tranql-connector-postgresql-xa adapter has no such problem. 2. tranql-connector-postgresql-local does have such problem Besides the exception described by Radim Kolar, additional exceptions are: Caused by: java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:103) at java.net.SocketOutputStream.write(SocketOutputStream.java:147) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:76) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:134) at org.postgresql.core.PGStream.flush(PGStream.java:508) at org.postgresql.core.v3.QueryExecutorImpl.sendSync(QueryExecutorImpl.java:676) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:191) ... 62 more Seems for local transaction db pool of Postgresql, the bad connection won't be threw out, for following db request, the server still return the bad connection to application. But for XA transaction db pool of Postgresql, no such problem. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662373#action_12662373 ] Radim Kolar commented on GERONIMO-4222: --- I did testing on PostgreSQL 8.2 and WAS CE 2.1.1.1. After PGSQL is restarted db pool is unusable, there is no hang, but Geronimo never recovers from that error. Trace dumps are like this. javax.servlet.ServletException: org.postgresql.util.PSQLException: An I/O error occured while sending to the backend. org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:852) org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:781) org.apache.jsp.index_jsp._jspService(index_jsp.java:535) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:369) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:342) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:267) javax.servlet.http.HttpServlet.service(HttpServlet.java:806) same application running in tomcat 5.5.25 container fails only once after pgsql is restarted, following requests are fine. Probably tomcat db pool can detect failed connections to database and close them instead of recycling them to application. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662119#action_12662119 ] David Frahm commented on GERONIMO-4222: --- FWIW, upgrading WASCE seems to have resolved the connection issues we were having. We installed a new physical server, keeping RHEL 5.2 but using WASCE 2.1.0.1 this time. Its been running for weeks without a single connection issue. As commented above, previous server would have hung connections 2 or more times per week. Thanks everyone! > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: Wish List > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626943#action_12626943 ] Radim Kolar commented on GERONIMO-4222: --- This issue is still not fixed. I can reproduce it easily just by restarting database (tested it on app using postgresql, but it will most likely do same on mysql like in old G version). I tested it with Geronimo-2.1.1 After db is restarted, all connections still fails, but i must correct my previous comment: G-2.1.1 doesnt hangs. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Fix For: 2.0.3, 2.1 > > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12626405#action_12626405 ] Kevan Miller commented on GERONIMO-4222: Hi David, The testing I performed was totally manual. However, we did add additional test cases as the Connector problems were being identified, diagnosed and fixed. Have you had a chance to test your scenario using Geronimo 2.1.2? Was waiting to hear back, before closing this Jira out. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624413#action_12624413 ] David Frahm commented on GERONIMO-4222: --- Thank you for the test results. Is that test, or some other test, now added to an automated build test suite or part of regression testing in some way? > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623244#action_12623244 ] Kevan Miller commented on GERONIMO-4222: I tried to recreate this using the Roller plugin and MySQL (on 2.1.2). I drove DB connection errors by stopping/restarting the MySQL server. The Connection Pool seemed to be working properly. Driving an idle timeout was a little tricky because of DB activity that Roller initiates. However, that too seemed to be working properly. As Donald mentions, I believe this is probably a bug in geronimo-connector -- which has been fixed. If you could test your environments with this code, it would be greatly appreciated. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621858#action_12621858 ] Thad West commented on GERONIMO-4222: - The Derby test case outlined by David would sufficiently recreate the problem I have encountered! > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621840#action_12621840 ] David Frahm commented on GERONIMO-4222: --- I will see about trying a newer WASCE. Might not happen very soon though. I was trying to think about how to create a test case for this that doesn't involve our production as/400. With other people having this issue, maybe we could use a different database. Certainly MySQL would be better, but what about something like Derby for a unit test? That could be embedded and therefore run with every build. Maybe the test could: 1. initialize Derby, create the database, a table, some data 2. use the connection pool to access the data 3. take down Derby (even delete the database?) 4. repeat step 1 5. test the connection pool I'm not sure what would be best, trying to debug the production issues or trying to create a repo test case. I guess I'll keep thinking on both and see which one yields some results. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621804#action_12621804 ] Donald Woods commented on GERONIMO-4222: Is there anyway you can try recreating this on WASCE 2.0.0.2/2.1.0.0 or Geronimo 2.1.2? The WASCE 2.0.0.2 release includes additional txmanager manager changes that are in Geronimo 2.0.3-SNAPSHOT and Geronimo 2.1.x releases and should generate different results. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: before and after wasce restart.txt, stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621592#action_12621592 ] David Frahm commented on GERONIMO-4222: --- I've never seen that error, sorry. I'm not where I can get at the logs right now, but I do have some old notes regarding this error we would get until we restarted the server: WARN [GeronimoConnectionEventListener] connectionErrorOccurred called with null > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621561#action_12621561 ] Kevan Miller commented on GERONIMO-4222: Trying to get some time to investigate this. Maybe tonight? Do you see anything suspicious in your logs? Maybe something like: "Error occurred during execution of ExpirationMonitor TimerTask" > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621218#action_12621218 ] Radim Kolar commented on GERONIMO-4222: --- We have some problems, it can be reproduces very easily for example by restarting database server and i agree with poster that Websphere 6 doesnt have this problem. Tomcat5.5 have same problem. Its serious problem and needs to be fixed. Also G hangs if connection pool is full of invalid connections until they idle timeouts. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > Attachments: stacktrace.txt > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618401#action_12618401 ] Thad West commented on GERONIMO-4222: - We are running Geronimo 2.0.2 connecting to MySQL v5 The default for MySQL is to close a connection after 8 hours of inactivity (overnight for us). Here are the details: http://dev.mysql.com/doc/refman/5.0/en/gone-away.html For testing purposes, you could change the time limit by setting the wait_timeout variable when you start mysql. http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html So...MySQL invalidates the connection, but Geronimo keeps it in the pool. As soon as you get one of these connections and try to use it, kablammo! > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
