[
https://issues.apache.org/jira/browse/POOL-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871118#action_12871118
]
[email protected] commented on POOL-168:
---------------------------------------
<quote author='JIRA [email protected]'>
[
https://issues.apache.org/jira/browse/POOL-168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz closed POOL-168.
----------------------------
Fix Version/s: 1.5.5
Resolution: Duplicate
This duplicates POOL-162, which has been fixed in the source repository.
The fix for this bug will be included in pool 1.5.5.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
</quote>
Quoted from:
http://apache-commons.680414.n4.nabble.com/jira-Created-POOL-168-Thread-Interrupt-during-borrowObject-may-lock-pool-tp2067214p2068518.html
hi,
I have the same problem and I can't find neither the snapshot nor POOL-168 in
http://svn.apache.org/viewvc/commons/proper/pool/trunk/?view=log
Can you tell me when the release of 1.5.5 will be.
regards
Daniel
<pre>
Full thread dump Java HotSpot(TM) 64-Bit Server VM (11.2-b01 mixed mode):
"ajp-28009-40" daemon prio=10 tid=0x0000000003104800 nid=0x4950 in
Object.wait() [0x0000000046fa9000..0x0000000046faab20
]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x00007fd959609c20> (a
org.apache.commons.pool.impl.GenericObjectPool)
at java.lang.Object.wait(Object.java:485)
at
org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:793)
- locked <0x00007fd959609c20> (a
org.apache.commons.pool.impl.GenericObjectPool)
at org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:171)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:207)
at rsw.db.Database.getConnection(Database.java:63)
......
</pre>
> Thread Interrupt during borrowObject may lock pool
> --------------------------------------------------
>
> Key: POOL-168
> URL: https://issues.apache.org/jira/browse/POOL-168
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 1.5.4
> Environment: The pool is being used for a connection pool of SSH
> connections on slax.
> Reporter: YL
> Fix For: 1.5.5
>
>
> We're using the pool quite intensively, with many borrow and return calls.
> The pool is set to WHEN_EXHAUSTED_BLOCK with a positive wait value (a few
> seconds). Sometimes, the thread that is waiting on the "latch.wait(waitTime)"
> call (Line 1112 in GenericObjectPool of version 1.5.4) may be interrupted.
> When that happens, the InterruptedException will be caught and rethrown
> correctly. However, after this happens, the pool becomes useless and no
> borrowObject calls succeed.
> By looking at the code, it appears that some cleanup that is done in normal
> operation (right before the NoSuchElementException timeout exception is
> thrown) is not done in the case detailed above. It is possible that the
> cleanup should be done in the case of interruption as well, to ensure the
> pool continues to operate correctly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
