https://issues.apache.org/bugzilla/show_bug.cgi?id=57460

            Bug ID: 57460
           Summary: [DB2]Connection broken after few hours but not removed
                    from the pool?
           Product: Tomcat Modules
           Version: unspecified
          Hardware: Other
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: jdbc-pool
          Assignee: dev@tomcat.apache.org
          Reporter: loic.rod...@gmail.com

Hi,

We encountered an error using tomcat.jdbc in acceptance.
This pool is used by default on TomEE 1.6.0.2. Some application using DB2 had
the issue after a night or at least some hours of inactivity.
Some broken connections seems to be in pool.
Changing the pool implementation to Common JDBC fix the problem.

I am not sure it is very interesting to solve issue on DB2 but maybe...

TomEE 1.6.0.2 use Tomcat 7.0.53
The driver used is DataDirect 5.1.3
Here is the pool configuration is:

JdbcDriver com.merant.datadirect.jdbc.db2.DB2Driver
        JdbcUrl
jdbc:datadirect:db2://ooooo:uuu;locationName=xxxx;packageCollection=JDBCV5R0
        UserName XXXXXX
        Password XXXXXX
        JtaManaged true
        InitialSize 3
        MaxActive 20
        MinIdle 3
        MaxIdle 10
        TestOnBorrow true
        testOnReturn true
        testWhileIdle true
        numTestsPerEvictionRun 1
        PoolPreparedStatements true
        MaxOpenPreparedStatements 128
        ValidationQuery select current date from sysibm.sysdummy1
        timeBetweenEvictionRunsMillis 100000

The stack trace is:

Caused by: java.sql.SQLException: [DataDirect][DB2 JDBC Driver]Object has been
closed.
    at com.ddtek.jdbc.db2base.ddcf.b(Unknown Source)
    at com.ddtek.jdbc.db2base.ddcf.a(Unknown Source)
    at com.ddtek.jdbc.db2base.ddce.b(Unknown Source)
    at com.ddtek.jdbc.db2base.ddce.a(Unknown Source)
    at com.ddtek.jdbc.db2base.BaseConnection.rollback(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at
org.apache.tomcat.jdbc.pool.ProxyConnection.invoke(ProxyConnection.java:126)
    at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)
    at
org.apache.tomcat.jdbc.pool.interceptor.AbstractCreateStatementInterceptor.invoke(AbstractCreateStatementInterceptor.java:71)
    at
org.apache.tomcat.jdbc.pool.interceptor.StatementCache.invoke(StatementCache.java:180)
    at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)
    at org.apache.tomcat.jdbc.pool.TrapException.invoke(TrapException.java:41)
    at
org.apache.tomcat.jdbc.pool.JdbcInterceptor.invoke(JdbcInterceptor.java:109)
    at
org.apache.tomcat.jdbc.pool.DisposableConnectionFacade.invoke(DisposableConnectionFacade.java:80)
    at com.sun.proxy.$Proxy71.rollback(Unknown Source)
    at
org.apache.openejb.resource.jdbc.managed.local.LocalXAResource.rollback(LocalXAResource.java:158)
    ... 36 more

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

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

Reply via email to