users@glassfish.java.net

Re: glassfish memory leak? ConcurrentLinkedQueue

From: <glassfish_at_javadesktop.org>
Date: Tue, 30 Mar 2010 00:59:37 PDT

Thanks for your help.

We've just updated the server and the problem seems to stay.

After 40 minutes uptime, there are already 60 MB LinkedBlockingQueue$Node. The stacktrace is the following

SelectorThread-80
  at sun.nio.ch.EPollArrayWrapper.epollWait(JIJI)I (Native Method)
  at sun.nio.ch.EPollArrayWrapper.poll(J)I (EPollArrayWrapper.java:215)
  at sun.nio.ch.EPollSelectorImpl.doSelect(J)I (EPollSelectorImpl.java:65)
  at sun.nio.ch.SelectorImpl.lockAndDoSelect(J)I (SelectorImpl.java:69)
  at sun.nio.ch.SelectorImpl.select(J)I (SelectorImpl.java:80)
  at com.sun.enterprise.web.connector.grizzly.SelectorThread.doSelect()V (SelectorThread.java:1410)
  at com.sun.enterprise.web.connector.grizzly.SelectorThread.startListener()V (SelectorThread.java:1325)
  at com.sun.enterprise.web.connector.grizzly.SelectorThread.startEndpoint()V (SelectorThread.java:1288)
  at com.sun.enterprise.web.connector.grizzly.SelectorThread.run()V (SelectorThread.java:1264)

btw, we have cometSupport enabled on this SelectorThread, but the error appears on the admin-listener, too.
[Message sent by forum member 'kimschneider']

http://forums.java.net/jive/thread.jspa?messageID=394407