You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Jonathan Valliere (JIRA)" <ji...@apache.org> on 2018/03/05 16:57:00 UTC

[jira] [Commented] (DIRMINA-1068) Mina 2.0.7 cpu load 100% on windows server 64

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

Jonathan Valliere commented on DIRMINA-1068:
--------------------------------------------

Please pull MINA from GIT and compile the 2.0 branch.  The large number of "Thread-X" threads is odd, not sure what in MINA creates threads that way.  The Acceptor spin is caused by an error in the {{accept()}} function creating spin.  Newer versions of MINA have checks for this.

> Mina 2.0.7 cpu load 100% on windows server 64
> ---------------------------------------------
>
>                 Key: DIRMINA-1068
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1068
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.7
>         Environment: windows server 64
> JDK 1.8.0_121 
>            Reporter: gunker
>            Priority: Major
>         Attachments: $V350`0YL5A@`FQ)5GFJ97S.jpg, )XDXFZF(26)(25UK0OVL)WW.jpg, ABN)]7BCUMHZLESQVUO%4@P.jpg, F5}3O~0_4K1KH(XJDXG`_RR.jpg, O`AUL[7]JG5QVKFY4K~`[$M.jpg, _HB%JVLZW`NW]~JW4L0766J.png
>
>
> in my case:
> I deploy this service on windows server(64).
> At beginning, all is normal. But after servrial days (not a fixed time) the cpu load 100%, I dump the theads info, it shows has a lot of "Thread-" threads, and the mina NioSocketAcceptor thread load 100%.     



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)