[jira] [Comment Edited] (DIRMINA-1114) High CPU utilization because of Mina-core jar

["Jonathan Valliere (JIRA)" <ji...@apache.org>]

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

Jonathan Valliere edited comment on DIRMINA-1114 at 5/24/19 12:46 PM:
----------------------------------------------------------------------

Please build a [flamegraph|https://github.com/brendangregg/FlameGraph] and post that up here.  Set the sample interval to very low and let it run for 10 minutes.


was (Author: johnnyv):
Please build a [flamegraph|https://github.com/brendangregg/FlameGraph] and post that up here.

> High CPU utilization because of Mina-core jar
> ---------------------------------------------
>
>                 Key: DIRMINA-1114
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1114
>             Project: MINA
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2
>            Reporter: Hrushikesh Agrawal
>            Priority: Major
>         Attachments: CPUAnalysys.zip, threaddump_06_05_20191557137156089.log, threaddump_06_05_20191557137173951.log
>
>
> Hi,
> We are have our own product  through which we are trying to communicate with LDAP server by using the mina-core-2.1.2.jar and api-all-1.0.3.jar jars. When we have invalid connection parameter, and tried to get the connection, CPU core utilization is 100%.
> Then we have seen in JVisualVM and in Jprofiler that "org.apache.mina.transport.socket.nio.NioSocketConnector" is in CPU more time.
> We can see below in thread dump-
> "NioSocketConnector-3" #152 prio=5 os_prio=0 tid=0x00007f95940d4000 nid=0x77fb runnable [0x00007f956f1fe000]
>    java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
> at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:93)
> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
> - locked <0x00000000ebdf89e8> (a sun.nio.ch.Util$3)
> - locked <0x00000000ebdf89d8> (a java.util.Collections$UnmodifiableSet)
> - locked <0x00000000ebdf88c0> (a sun.nio.ch.EPollSelectorImpl)
> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
> at org.apache.mina.transport.socket.nio.NioSocketConnector.select(NioSocketConnector.java:292)
> at org.apache.mina.core.polling.AbstractPollingIoConnector$Connector.run(AbstractPollingIoConnector.java:433)
> at org.apache.mina.util.NamePreservingRunnable.run(NamePreservingRunnable.java:64)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> We can see same issue with standalone java class and try to get the ldap connection. Attaching couple of snapshot to understand the issue. 
> Please note this happens in Ubuntu and Centos. Also found same issue with 2.0.21, 2.0.18 mina core jar.
> Can someone please help me on this.
>  
> Thanks,
> Hrushi
>  
>  
>  



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