[
https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851566#comment-16851566
]
Hrushikesh Agrawal commented on DIRMINA-1114:
---------------------------------------------
Hi [~johnnyv],
Thanks for looking into this.
I have executed below commands and its confirmed that, machine is NOT* Virtual
machine, and its physical machine.
group03@group03:~/Downloads/LDAP-663$ imvirt
Physical
group03@group03:~/Downloads/LDAP-663$ dmesg | grep -i "Hypervisor detected"
group03@group03:~/Downloads/LDAP-663$
group03@group03:~/Downloads/LDAP-663$ hostnamectl status
Static hostname: group03
Icon name: computer-desktop
Chassis: desktop
Machine ID: 9982cd822cde4d3bb226805f177c5c5a
Boot ID: fb57668868fb4ea1a80b9352ff13bba6
Operating System: Ubuntu 18.04.1 LTS
Kernel: Linux 4.15.0-50-generic
Architecture: x86-64
group03@group03:~/Downloads/LDAP-663$ systemd-detect-virt
none
Yes, every time you could see the 100% CPU usage, attaching the htop.png which
shows the 100% CPU usage.
Thanks,
Hrushi
> 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
> Assignee: Jonathan Valliere
> Priority: Major
> Attachments: 29thMay.zip, CPUAnalysys.zip, flamerelated.zip,
> graph1_color.svg, htop.png, htop.png, step1_flamegraph.txt,
> 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)
