commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DBCP-270) Dead lock using the evictor
Date Fri, 27 Jun 2008 02:52:45 GMT

     [ https://issues.apache.org/jira/browse/DBCP-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz resolved DBCP-270.
------------------------------

    Resolution: Fixed

Pactch applied.  Thanks!

This patch also resolves the last deadlock reported in DBCP-44.  

> Dead lock using the evictor
> ---------------------------
>
>                 Key: DBCP-270
>                 URL: https://issues.apache.org/jira/browse/DBCP-270
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.2.2
>            Reporter: Filip Hanik
>            Priority: Critical
>         Attachments: deadlock-abandoned-trace.patch
>
>
> Patch attached, dead lock reported. the abandonedtrace does synchronized(this) when it
really only needs to do synchronized(this.trace)
> Dead lock reported when using the evictor
> =============================
> "Timer-3":
>   waiting to lock monitor 0x0000000053b40548 (object 0x00002aaabf3210f0, a
> org.apache.tomcat.dbcp.dbcp.PoolableConnection),
>   which is held by "TP-Processor27"
> "TP-Processor27":
>   waiting to lock monitor 0x0000000053b404d0 (object 0x00002aaab9fa8b08, a
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool),
>   which is held by "Timer-3"
> Java stack information for the threads listed above:
> ===================================================
> "Timer-3":
>         at
> org.apache.tomcat.dbcp.dbcp.AbandonedTrace.addTrace(AbandonedTrace.java:175)
>         - waiting to lock <0x00002aaabf3210f0> (a
> org.apache.tomcat.dbcp.dbcp.PoolableConnection)
>         at
> org.apache.tomcat.dbcp.dbcp.AbandonedTrace.init(AbandonedTrace.java:92)
>         at
> org.apache.tomcat.dbcp.dbcp.AbandonedTrace.<init>(AbandonedTrace.java:82)
>         at
> org.apache.tomcat.dbcp.dbcp.DelegatingStatement.<init>(DelegatingStatement.java:61)
>         at
> org.apache.tomcat.dbcp.dbcp.DelegatingConnection.createStatement(DelegatingConnection.java:224)
>         at
> org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.validateConnection(PoolableConnectionFactory.java:331)
>         at
> org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.validateObject(PoolableConnectionFactory.java:312)
>         at
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.evict(GenericObjectPool.java:1217)
>         - locked <0x00002aaab9fa8b08> (a
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool)
>         at
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool$Evictor.run(GenericObjectPool.java:1341)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> "TP-Processor27":
>         at
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.addObjectToPool(GenericObjectPool.java:1136)
>         - waiting to lock <0x00002aaab9fa8b08> (a
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool)
>         at
> org.apache.tomcat.dbcp.pool.impl.GenericObjectPool.returnObject(GenericObjectPool.java:1076)
>         at
> org.apache.tomcat.dbcp.dbcp.PoolableConnection.close(PoolableConnection.java:87)
>         - locked <0x00002aaabf3210f0> (a
> org.apache.tomcat.dbcp.dbcp.PoolableConnection)
>         ....

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message