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] [Closed] (POOL-182) Issues with org.apache.commons.pool2.performance. PerformanceTest
Date Wed, 31 Dec 2014 16:50:14 GMT

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

Phil Steitz closed POOL-182.
----------------------------

> Issues with org.apache.commons.pool2.performance. PerformanceTest
> -----------------------------------------------------------------
>
>                 Key: POOL-182
>                 URL: https://issues.apache.org/jira/browse/POOL-182
>             Project: Commons Pool
>          Issue Type: Bug
>    Affects Versions: 2.0
>            Reporter: Zoltan Farkas
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: PerformanceTest.patch
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
>  the use volatiles : waiting,complete,totalBorrowTime, totalReturnTime, nrSamples
>  is not correct.
>  for ex the following totalBorrowTime += borrowTime is not atomic resulting in a
>  race condition.
>  one way to fix this is using the java.util.concurent Atomic variants or even
>  better,
>  make these variables members of MyThread and aggregate them at the end of the
>  test,
>  this way there will be no need to use Atomic and thus increasing efficiency, and
>  accuracy of the test of the test.
>  also:
>  private boolean start;
>  needs to be volatile, due to visibility issue.
>  (when updating start other threads might not pick up the value)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message