commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Helge Dannenberg (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (POOL-192) GenericKeyedObjectPool: clear() clears the keyed pool but does not decrease the item counter
Date Wed, 21 Dec 2011 05:15:31 GMT

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

Helge Dannenberg commented on POOL-192:
---------------------------------------

Vielen Dank für Ihre E-Mail. Ich bin voraussichtlich am 09.01.2012 wieder im Hause. In dringenden
Fällen wenden Sie sich bitte an Dieter Frank (+49 69 696 8113) oder Christian Peter (+49
69 696 72449) Mit freundlichen Grüßen, Helge Dannenberg ----- I'm out of office until 09th
of January 2012. In urgent cases please contact Mr Dieter Frank (+49 69 696 8113) or Mr Christian
Peter (+49 69 696 72449) Best regards, Helge Dannenberg

                
> GenericKeyedObjectPool: clear() clears the keyed pool but does not decrease the item
counter
> --------------------------------------------------------------------------------------------
>
>                 Key: POOL-192
>                 URL: https://issues.apache.org/jira/browse/POOL-192
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.5.6
>            Reporter: Helge Dannenberg
>             Fix For: 1.5.7
>
>
> If function 'clear(Object key)' in GenericKeyedObjectPool is called onto a keyed pool,
the ObjectQueue (= the keyed pool) is removed from the pool list. 
> Its items are deleteded in the function 'destroy()' afterwards. But as the ObjectQueue
is already removed, the itemcounter _totalInternalProcessing is 
> never decreased.
> As a result of this bug the pool exhausts even if the pool is empty.
> The solution is to decrease the counter _totalInternalProcessing in 'destroy()' also
if ObjectQueue in null.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message