You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2015/04/21 12:19:28 UTC

[Bug 57839] New: Commons DBCP Closed Connection error

https://bz.apache.org/bugzilla/show_bug.cgi?id=57839

            Bug ID: 57839
           Summary: Commons DBCP Closed Connection error
           Product: Tomcat 6
           Version: 6.0.5
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
          Assignee: dev@tomcat.apache.org
          Reporter: rohini.tn@in.ibm.com

The Oracle DB has 37k packages in our customer env. The issue is seen after
running the below query from the program or when using
DatabaseMetadata.getProcedureColumns()  in a program . We are seeing these
errors  "Exhausted Resultset (SQL Code =99999 and vendor code=17,011) " or
"Closed Connection :next (SQL code=08003 , Vendor code=17,008)".

Something happening to connection or resultset getting closed after running the
query/getProcedureColumns call. We have investigated further and see this issue
of Exhausted Resultset/Connection getting closed only when we use the
datasource connection pool logic in our product.

When we run a standalone java program with the query/getProcedureColumns  call
, it took 10mins for the customer to get the output and there were no issues.We
want the same behavior with datasource connection pool logic .


We are using Tomcat sevrer and org.apache.commons.pool.impl.GenericObjectPool
connection pool.We have these connection pool settings done. 

connectionPool.setMaxActive(25);
connectionPool.setMaxIdle(1);
connectionPool.setMinEvictableIdleTimeMillis(120000);
connectionPool.setTimeBetweenEvictionRunsMillis(1000);
connectionPool.setTestOnReturn(false);
connectionPool.setTestOnBorrow(true);
connectionPool.setTestWhileIdle(false); 

Hence please let us know if there is any fine tuning to be done to make query
or DatabaseMetadata.getProcedureColumns() to work when we use datasource
connection pool logic.Please suggest us any other timeout or if there is
anything else which can help us in this scenario.Thanks


SQL QUERY :
SELECT * FROM SYS.ALL_ARGUMENTS WHERE PACKAGE_NAME = 'PKG_TEST' AND OBJECT_NAME
= 'PRC_INSERT' AND OWNER = 'APPS' ORDER BY SEQUENCE

ERROR:
java.sql.SQLRecoverableException: Closed Connection: next
at oracle.jdbc.driver.OracleResultSetImpl.next(OracleResultSetImpl.java:233)

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 57839] Commons DBCP Closed Connection error

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=57839

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
This is phrased very much like a support question and Bugzilla is not the best
place for that sort of discussion.

You need to take your question to either the Tomcat users list or the Commons
user list since DBCP is produced by the Apache Commons project. I'd recommend
the Commons user list. If the discussion there concludes there is a bug at the
root of this rather than that a configuration change is required, they will
point you to the right place to raise that bug (Commons DBCP in the ASF Jira
instance) and Tomcat will pick up the fix once it is made.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org