Hi all,
I know that this is a old very known problem but from all the topics I saw its saying should be not present(fixed) in glassfish 3.1.2.2 build5!
I re-produce the problem over a 5 times in my test/dev enviroment...
What happens is that glassfish tryies to stop-interrupt a idle thread which is all ok..but it dose this in a starvesion lock flowting the log file with this output and eating up maximum(100%) of the machine cpu...
[#|2012-11-13T20:23:52.137+0100|WARNING|glassfish3.1.2|com.sun.grizzly.config.Gr
izzlyServiceListener|_ThreadID=25;_ThreadName=Thread-2;|GRIZZLY0023: Interruptin
g idle Thread: admin-thread-pool-4848(5).|#]
[#|2012-11-13T20:23:53.138+0100|WARNING|glassfish3.1.2|com.sun.grizzly.config.Gr
izzlyServiceListener|_ThreadID=25;_ThreadName=Thread-2;|GRIZZLY0023: Interruptin
g idle Thread: admin-thread-pool-4848(4).|#]
Any idea somebody?!
Like I said before I reproduce the problem 5-6 times from a fresh instaled version with no app deployed
Tnx
B