[ 
https://issues.apache.org/jira/browse/POOL-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12765145#action_12765145
 ] 

Hassan Sajjad commented on POOL-151:
------------------------------------

Generic Object Pool/Eviction params
{noformat}
    <property name="maxActive" value="100" /> 
    <property name="maxIdle" value="100" />   
    <property name="exhaustedAction" value="2" /> <!-- GROW -->
    <property name="timeBetweenEvictionRunsMillis" value="10000" /> <!-- 10 sec 
for testing / reproducing the issue -->
    <property name="minEvictableIdleTimeMillis" value="10000" />
    <property name="numTestsPerEvictionRun" value="-1" /> 
{noformat}

> Eviction thread is able to remove (destroy) in-flight (borrowed) objects
> ------------------------------------------------------------------------
>
>                 Key: POOL-151
>                 URL: https://issues.apache.org/jira/browse/POOL-151
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: Hassan Sajjad
>            Priority: Blocker
>
> Under high concurrent use, the eviction thread can temper with an in-use 
> object from the pool, potentially causing catastrophic results, as illustrate 
> in the below log from our use. Note the object - in our case JMSSession is 
> closed in-flight (after message send but before commit), causing the commit 
> to fail with {{javax.jms.IllegalStateException: MQJMS1024: session closed}} 
> error.
> {noformat}
> 2009-10-12 15:08:40,254 DEBUG [asyncDelivery59] Borrowed session 
> com.ibm.mq.jms.mqqueuesess...@40bc88 for jms connector 
> 2009-10-12 15:08:40,341 DEBUG [Timer-0] Physically closing 
> com.ibm.mq.jms.mqqueuesess...@40bc88 for connector 
> 2009-10-12 15:08:40,669 DEBUG [asyncDelivery59] Returning session 
> com.ibm.mq.jms.mqqueuesess...@40bc88 for jms conn
> ector
> 2009-10-12 15:08:40,433 ERROR [asyncDelivery59] Exception caught while 
> committing transaction [com.ibm.mq.jms.mqqueuesess...@40bc88]
> {noformat}

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

Reply via email to