Also, the thread dump shows many such idle threads in RUNNABLE state (more than 500). Isn't that an issue?
Regards, Dhiraj On Tue, Jun 24, 2014 at 2:33 PM, dhiraj prajapati <[email protected]> wrote: > Hi, > But the application is using a lot of native memory and it ends up using a > lot of swap space after which I am forced to restart the application. > > Regards, > Dhiraj > > > On Tue, Jun 24, 2014 at 1:20 PM, Jan Bartel <[email protected]> wrote: > >> Dhiraj, >> >> That thread dump just shows an idle thread. In past versions of jetty, >> there were issues with jdk epoll bugs, but they manifested themselves >> as cpu spin. So if you're not seeing undue cpu activity then this is >> not a problem. >> >> Jan >> >> On 23 June 2014 14:57, dhiraj prajapati <[email protected]> wrote: >> > I am using Jetty 9.1.2 in my application. The application uses huge >> native >> > memory space. In the thread dump, I see a lot of instances like: >> > >> > "qtp2042324703-524-selector-ServerConnectorManager@5c95306c/7" prio=10 >> > tid=0x00007f4c1985a000 nid=0xb7bb runnable [0x00007f4c0ef6e000] >> > 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:79) >> > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) >> > - locked <0x00000000bff941a8> (a sun.nio.ch.Util$2) >> > - locked <0x00000000bff94198> (a >> > java.util.Collections$UnmodifiableSet) >> > - locked <0x00000000bff941b8> (a sun.nio.ch.EPollSelectorImpl) >> > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) >> > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:102) >> > at >> > >> org.eclipse.jetty.io.SelectorManager$ManagedSelector.select(SelectorManager.java:531) >> > at >> > >> org.eclipse.jetty.io.SelectorManager$ManagedSelector.run(SelectorManager.java:484) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607) >> > at >> > >> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536) >> > at java.lang.Thread.run(Thread.java:744) >> > >> > I need some help to sort this out. Is this a known bug which is fixed >> in a >> > later release? >> > >> > Regards, >> > >> > Dhiraj >> > >> > >> > _______________________________________________ >> > jetty-users mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >> >> >> >> -- >> Jan Bartel <[email protected]> >> www.webtide.com >> 'Expert Jetty/CometD developer,production,operations advice' >> _______________________________________________ >> jetty-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
