I don't know anything about the release schedule. You could, however, compile the project from source.
I've don't that, and made the artifacts available here: https://discourse.igniterealtime.org/t/openfire-4-3-2-cpu-goes-at-100-after-a-few-hours-on-linux/85119/27 On Fri, 24 May 2019 at 15:58, Hrushikesh Agrawal <hagra...@tibco.com.invalid> wrote: > Thank Guus. Do you know the expected date the 2.1.3 would be available? I > wanted to try with this jar as well. > > Regards, > Hrushi > > On Fri, May 24, 2019 at 6:28 PM Guus der Kinderen < > guus.der.kinde...@gmail.com> wrote: > > > This sounds like https://issues.apache.org/jira/browse/DIRMINA-1111 but > I > > think the MINA devs told me that this was limited to the 2.1.X branch. If > > that's true, then I cannot explain why you found the issue in 2.0.18 and > > 2.0.21. > > > > On Fri, 24 May 2019 at 14:36, Hrushikesh Agrawal > > <hagra...@tibco.com.invalid> > > wrote: > > > > > 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 > > > > > >
