[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854186#comment-16854186 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi [~johnnyv], No I am not removing anything. Please find below sh file that I have executed. Same details have been attached with last post. root@group03:~/Downloads/LDAP-663# cat build-flamegraph #!/bin/bash sudo perf record -F 1000 -p 10653 -g -- sleep 30; sudo ./FlameGraph-master/jmaps sudo perf script | ./FlameGraph-master/stackcollapse-perf.pl | ./FlameGraph-master/flamegraph.pl --color=java --hash > flamegraph.svg sudo rm perf.data root@group03:~/Downloads/LDAP-663# 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: 0531.zip, 29thMay.zip, CPUAnalysys.zip, > flamerelated.zip, graph1_color.svg, htop.png, htop.png, > nio-metal-example.svg, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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) - To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org For additional commands, e-mail: dev-h...@mina.apache.org
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16852757#comment-16852757 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi [~johnnyv], Thanks for looking into this. I have uploaded the latest "0531.zip" file with latest capture. Please note, If I used the below command then I would get the below error- sudo perf record -F 1000 -a -g -- sleep 30; sudo ./FlameGraph-master/jmaps errors:- Failed to open /tmp/perf-15873.map, continuing without symbols Failed to open /tmp/perf-9469.map, continuing without symbols Failed to open /tmp/perf-10155.map, continuing without symbols Please see attached file. then I have used the command with process id, like below, and it ran successfully. sudo perf record -F 1000 -p 10653 -g -- sleep 30; sudo ./FlameGraph-master/jmaps 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: 0531.zip, 29thMay.zip, CPUAnalysys.zip, > flamerelated.zip, graph1_color.svg, htop.png, htop.png, > nio-metal-example.svg, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: 0531.zip > 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: 0531.zip, 29thMay.zip, CPUAnalysys.zip, > flamerelated.zip, graph1_color.svg, htop.png, htop.png, > nio-metal-example.svg, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: htop.png > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850892#comment-16850892 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi [~johnnyv], I am not sure about "java" and "[unknown]", I have followed the mentioned steps. Please help me on this if we need that class name for these. Still I have capture one more graph and attaching here "graph1_color.svg". If I opened the graph in internet explorer and do the mouse over on any java stack then its gives package name and class name, method name. 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, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: graph1_color.svg > 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, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: 29thMay.zip > 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, > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850541#comment-16850541 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi [~johnnyv], Thanks for help. As suggested, I have executed the flame graph steps mentioned in given link. I am attaching "29thMay.zip" which has below stuff - - generated svg file - generated svg color file - steps that I have executed at my end. - Java project execution command Please let me know if you need anything more. 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, > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Comment Edited] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849643#comment-16849643 ] Hrushikesh Agrawal edited comment on DIRMINA-1114 at 5/28/19 12:02 PM: --- Hi [~johnnyv], I have executed the flame graph steps mentioned in this portal "http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html#Java"; from section 8 JAVA. I am attaching "flamerelated.zip" which has below stuff - - generated svg file - htop screenshot that shows java process (pid- 16280) is 100% CPU utilization. - steps that I have executed at my end. I have executed simple standalone java class through jar and take above results. If needed, I can share the sample java project. Please let me know if you need anything more. Thanks, Hrushi was (Author: hagrawal): Hi, I have executed the flame graph steps mentioned in this portal "http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html#Java"; from section 8 JAVA. I am attaching "flamerelated.zip" which has below stuff - - generated svg file - htop screenshot that shows java process (pid- 16280) is 100% CPU utilization. - steps that I have executed at my end. I have executed simple standalone java class through jar and take above results. If needed, I can share the sample java project. Please let me know if you need anything more. 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: CPUAnalysys.zip, flamerelated.zip, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849643#comment-16849643 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi, I have executed the flame graph steps mentioned in this portal "http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html#Java"; from section 8 JAVA. I am attaching "flamerelated.zip" which has below stuff - - generated svg file - htop screenshot that shows java process (pid- 16280) is 100% CPU utilization. - steps that I have executed at my end. I have executed simple standalone java class through jar and take above results. If needed, I can share the sample java project. Please let me know if you need anything more. 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: CPUAnalysys.zip, flamerelated.zip, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: flamerelated.zip > 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: CPUAnalysys.zip, flamerelated.zip, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: step1_flamegraph.txt > 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: CPUAnalysys.zip, 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848916#comment-16848916 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi, I am trying for flamegraph. In first step - Linux Perf_events, faced some issue and have sorted out. But now facing issue below error, do you have idea on this. group03@group03:~/Downloads/LDAP-663$ sudo perf script > out.perf Failed to open /tmp/perf-12427.map, continuing without symbols Attaching the log file for task that we did till now. 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: CPUAnalysys.zip, htop.png, > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Commented] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847609#comment-16847609 ] Hrushikesh Agrawal commented on DIRMINA-1114: - Hi Jonathan, Thanks for looking into this, PFA htop.png, that shows you that if execute the program and monitor the top or htop, there is process that consumes the 100% cpu. will work on flamegragh and update you further meanwhile if you have any question please let me know. 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: CPUAnalysys.zip, htop.png, > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: htop.png > 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: CPUAnalysys.zip, htop.png, > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Updated] (DIRMINA-1114) High CPU utilization because of Mina-core jar
[ https://issues.apache.org/jira/browse/DIRMINA-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hrushikesh Agrawal updated DIRMINA-1114: Attachment: threaddump_06_05_20191557137173951.log threaddump_06_05_20191557137156089.log > 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=0x7f95940d4000 > nid=0x77fb runnable [0x7f956f1fe000] > 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 <0xebdf89e8> (a sun.nio.ch.Util$3) > - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) > - locked <0xebdf88c0> (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)
[jira] [Created] (DIRMINA-1114) High CPU utilization because of Mina-core jar
Hrushikesh Agrawal created DIRMINA-1114: --- Summary: 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 Attachments: CPUAnalysys.zip 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=0x7f95940d4000 nid=0x77fb runnable [0x7f956f1fe000] 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 <0xebdf89e8> (a sun.nio.ch.Util$3) - locked <0xebdf89d8> (a java.util.Collections$UnmodifiableSet) - locked <0xebdf88c0> (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)
