[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 08:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 Category: JBossCX Group: v2.4 (stable) Status: Closed Resolution: Fixed Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: David Jencks (d_jencks) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- Comment By: David Jencks (d_jencks) Date: 2003-02-16 20:15 Message: Logged In: YES user_id=60525 I'm going to close this because in in jb3/4 you can now set an sql statement to be attempted before a connection is handed out. The better solution is still to write a db specific wrapper that determines if any particular exception means the connection should not be reused. -- Comment By: David Jencks (d_jencks) Date: 2002-02-05 18:27 Message: Logged In: YES user_id=60525 I believe that the jdbc specs don't really discuss what to do with dead connections, however the jca specs do. Please try using the jca xa wrapper to see if that works properly. Note that this is pretty much untested code, since I don't have a XADataSource implementation to play with. (For various reasons, the XADataSourceImpl wrapper doesn't work very well pretending to be an XADatasource in the jca framework) -- Comment By: Bani Greyling (banigreyling) Date: 2001-11-28 08:46 Message: Logged In: YES user_id=302589 I investigated this further. As it turned out I was not using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl but com.jnetdirect.jsql.JSQLXADataSource as my DataSourceClass. When using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl any dead connection would be removed from the pool after participating in a (failed) transaction, so at least I would not end up with a bunch of dead connections. Maybe this is not a bug but rather an enhancement request;) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 02:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 Category: JBossCX Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: David Jencks (d_jencks) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- Comment By: David Jencks (d_jencks) Date: 2002-02-05 12:27 Message: Logged In: YES user_id=60525 I believe that the jdbc specs don't really discuss what to do with dead connections, however the jca specs do. Please try using the jca xa wrapper to see if that works properly. Note that this is pretty much untested code, since I don't have a XADataSource implementation to play with. (For various reasons, the XADataSourceImpl wrapper doesn't work very well pretending to be an XADatasource in the jca framework) -- Comment By: Bani Greyling (banigreyling) Date: 2001-11-28 02:46 Message: Logged In: YES user_id=302589 I investigated this further. As it turned out I was not using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl but com.jnetdirect.jsql.JSQLXADataSource as my DataSourceClass. When using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl any dead connection would be removed from the pool after participating in a (failed) transaction, so at least I would not end up with a bunch of dead connections. Maybe this is not a bug but rather an enhancement request;) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 00:30 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: David Jencks (d_jencks) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- Comment By: David Jencks (d_jencks) Date: 2002-02-05 10:27 Message: Logged In: YES user_id=60525 I believe that the jdbc specs don't really discuss what to do with dead connections, however the jca specs do. Please try using the jca xa wrapper to see if that works properly. Note that this is pretty much untested code, since I don't have a XADataSource implementation to play with. (For various reasons, the XADataSourceImpl wrapper doesn't work very well pretending to be an XADatasource in the jca framework) -- Comment By: Bani Greyling (banigreyling) Date: 2001-11-28 00:46 Message: Logged In: YES user_id=302589 I investigated this further. As it turned out I was not using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl but com.jnetdirect.jsql.JSQLXADataSource as my DataSourceClass. When using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl any dead connection would be removed from the pool after participating in a (failed) transaction, so at least I would not end up with a bunch of dead connections. Maybe this is not a bug but rather an enhancement request;) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 00:30 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: Nobody/Anonymous (nobody) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- Comment By: Bani Greyling (banigreyling) Date: 2001-11-28 00:46 Message: Logged In: YES user_id=302589 I investigated this further. As it turned out I was not using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl but com.jnetdirect.jsql.JSQLXADataSource as my DataSourceClass. When using org.jboss.pool.jdbc.xa.wrapper.XADataSourceImpl any dead connection would be removed from the pool after participating in a (failed) transaction, so at least I would not end up with a bunch of dead connections. Maybe this is not a bug but rather an enhancement request;) -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [ jboss-Bugs-484776 ] Dead connection in Pool
Bugs item #484776, was opened at 2001-11-23 00:30 You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 Category: JBossCMP Group: v2.4 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bani Greyling (banigreyling) Assigned to: Nobody/Anonymous (nobody) Summary: Dead connection in Pool Initial Comment: Windows NT4 SP5 JDK 1.3 JBoss2.4.1a-Tomcat3.2.3 If a connection die in the pool and is later given out to participate in a transaction, it (obviously) give an exception. I think this is incorrect behaviour for the pool to assume the connection to be still valid after the transaction the connection was used in did not succeed. I configured my datasource with InvalidateOnError=true, but it does not seem to work. The dead connection stay in the pool. If my connections tend to die over time, I will end up with a pool of dead connections with no automated way of getting rid of them. IdleTimeout will not work, because the connection will not be idle as it is given out all the time (and cause exceptions). -- You can respond by visiting: http://sourceforge.net/tracker/?func=detailatid=376685aid=484776group_id=22866 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
