[jira] Resolved: (DIRMINA-331) StatCollector is not thread safe and some stats are being mixed up

["Trustin Lee (JIRA)" <ji...@apache.org>]

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

Trustin Lee resolved DIRMINA-331.
---------------------------------

    Resolution: Fixed
      Assignee: Trustin Lee

Done.  Please close this issue if my fix based on your patch works, Gaston.  Some issues will be addressed in 2.0: DIRMINA-317

> StatCollector is not thread safe and some stats are being mixed up
> ------------------------------------------------------------------
>
>                 Key: DIRMINA-331
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-331
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.1
>            Reporter: Gaston Dombiak
>         Assigned To: Trustin Lee
>             Fix For: 1.0.2
>
>
> The instance variable polledSessions is not thread-safe (i.e. uses ArrayList) and its access is not always protected (e.g. StatCollector$Worker#run()). Under  heavy load this is producing an error in the Worker.
> The bytesReadThroughput statistic is incorrectly being set. It is adding up the throughput of written messages.
> Instance variables: msgWrittenThroughput, msgReadThroughput, bytesWrittenThroughputand bytesReadThroughput could be corrupted and return an unexpected value since they are not thread safe and 2 different threads may be changing them.

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