users@glassfish.java.net

Re: glassfish memory leak? ConcurrentLinkedQueue

From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Mon, 29 Mar 2010 18:07:32 +0200

Please try to patch GF with the latest Grizzly 1.0.33 binaries [1]

WBR,
Alexey.

[1] http://blogs.sun.com/oleksiys/entry/patching_glassfish_2_1_x

On Mar 29, 2010, at 18:04 , glassfish_at_javadesktop.org wrote:

> We seem to have the same issue with our Glassfish.
>
> Our server runs out of memory twice a week (on average). We tracked
> this down to an increasing number of ConcurrentLinkedQueue node in
> the selector threads. (see image selectorthread.png)
>
> Everything seems to be working fine in our webapplication until the
> memory is full.
>
> Here some more background:
> Sun GlassFish Enterprise Server v2.1.1 ((v2.1 Patch06)(9.1_02
> Patch12)) (build b31g-fcs)
> Ubuntu 8.10
> Sun Java 1.6.0_16-b01
>
> I hope somebody has an idea what is going on here.
>
> Kim
> [Message sent by forum member 'kimschneider']
>
> http://forums.java.net/jive/thread.jspa?messageID=394320
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>