[jboss-jira] [JBoss JIRA] Closed: (JBCOMMON-53) ConnectionPool really slow when releasing closed connections (ConnectionError)

[Adrian Brock (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCOMMON-53?page=all ]

Adrian Brock closed JBCOMMON-53.
--------------------------------

    Resolution: Rejected
      Assignee:     (was: Dimitris Andreadis)

You can't find:
* The forums to ask the question
* The faq for this "answered many times" question
* Even the correct JIRA project to post the question under.

Read this - which was linked in BIG CAPITAL LETTERS before you posted this "bug report" - sigh! ;-(
http://wiki.jboss.org/wiki/JBossHelp

If/when you find the correct forum it will have a topic at the top that links 
to the docs/FAQ where the question is answered.

Sorry, I'm not going to encourage you to raise spurious bug reports by providing links
to FAQs here.

> ConnectionPool really slow when releasing closed connections (ConnectionError)
> ------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-53
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-53
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: common-core
>         Environment: Windows XP and Linux; JBoss 4.0.0 or JBoss 4.2.2 with Oracle 10g
>            Reporter: Stephane Poulin
>
> When databases are restarted after a shut down or a crash, JBoss connection pool's takes about 10 minutes to release all closed connections and get fresh ones.
> Even after the db restard I get:
> java.sql.SQLException: Closed Connection
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
> at oracle.jdbc.driver.PhysicalConnection.setAutoCommit(PhysicalConnection.java:1038)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkTransaction(BaseWrapperManagedConnection.java:399)
> at org.jboss.resource.adapter.jdbc.WrappedConnection.checkTransaction(WrappedConnection.java:722)
> at org.jboss.resource.adapter.jdbc.WrappedConnection.prepareStatement(WrappedConnection.java:202)
> or 
> java.sql.SQLException: Closed Connection
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
> at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:1142)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcRollback(BaseWrapperManagedConnection.java:515)
> at org.jboss.resource.adapter.jdbc.WrappedConnection.rollback(WrappedConnection.java:460)
> Apparently the pool purges itself but takes 10 minutes to do so.
> There must be a way to get connections as soon as the db server is back.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira