Salut,
glassfish_at_javadesktop.org wrote:
> D--n, I think I love you, h1d3m3. Thanks for the tip!!
I was about to reply the following. Can you do
% prstat -Lp <java PID>
% pstack PID/LWPID
Then match the result:
f8800278 ???????? (c497fcb8, c497fe80, a, ec2ff250, f880d120, c497fdb0)
The last line ??????? contains the thread ID: c497fcb8.
Then kill -3 PID and match the thread id. We will know which thread is
eating the memory.
Note that all Pipeline Threads are expected. This is the thread pool and
its associated WorkerThread which are waiting for works.
A+
-- Jeanfrancois
> [Message sent by forum member 'russpet' (russpet)]
>
> http://forums.java.net/jive/thread.jspa?messageID=317726
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>