You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Phil Steitz (JIRA)" <ji...@apache.org> on 2008/05/31 22:25:45 UTC

[jira] Reopened: (POOL-29) [pool]NumActive goes to negative when the pool can't create more objects

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

Phil Steitz reopened POOL-29:
-----------------------------


Comments in the duplicate, POOL-129, indicate that this may not have been resolved in 1.3, and / or reintroduced in 1.4.  

> [pool]NumActive goes to negative when the pool can't create more objects
> ------------------------------------------------------------------------
>
>                 Key: POOL-29
>                 URL: https://issues.apache.org/jira/browse/POOL-29
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 1.2
>         Environment: Operating System: All
> Platform: All
>            Reporter: Daniel C. Amadei
>             Fix For: 1.5
>
>
> Under heavy usage on multithreaded environment, the pool start to show 
> NumActive property as negative value.
> We've implemented a pool of sockets and if there is a problem creating new 
> sockets after some time of successful operation, the pool starts trying to 
> create new sockets but while trying to create them, it goes removing invalid 
> instances from the pool and after the evictor runs, it starts to invalidate the 
> objects, making the numActive property stay negative.
> I changed the class GenericObjectPoolImpl to check if _numActive property is 
> bigger than Zero, before decrementing it and I'd like to know if this is ok so 
> I can submit a patch. From my tests, it's working fine after checking if 
> numActive is > than zero before executing numActive--.
> Daniel

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