CPU consuming thread, help to analyze
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
CPU consuming thread, help to analyze
by Harri Jaakkola
::
Rate this Message:
Hi,
Bear with me, I am not very familiar in Sailfin/Glassfish code, but I hope you are the ones to help... I have been running a small 2 instance SGCS cluster with very basic SIP and HTTP towards simple test servlets for some hours, and after shutting down the client, I can still after several idle hours see ONE of the instances consuming CPU. I did some analysis and think this may be the consuming thread: "Thread-15" prio=10 tid=0x00002aab7a7d0000 nid=0x448b runnable [0x0000000041a08000] java.lang.Thread.State: RUNNABLE at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:215) at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65) at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69) - locked <0x00002aaab75fb3b8> (a sun.nio.ch.Util$1) - locked <0x00002aaab75fb3d0> (a java.util.Collections$UnmodifiableSet) - locked <0x00002aaab75f3b68> (a sun.nio.ch.EPollSelectorImpl) at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) at com.sun.grizzly.TCPSelectorHandler.select(TCPSelectorHandler.java:469) at com.sun.grizzly.Controller.doSelect(Controller.java:369) at com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:82) at com.sun.grizzly.Controller.startSelectorHandlerRunner(Controller.java:1136) at com.sun.grizzly.Controller.start(Controller.java:943) at com.sun.grizzly.Controller.run(Controller.java:813) at java.lang.Thread.run(Thread.java:619) Any ideas of what can cause this? What does this thread do? I am currently on SGCS, Sun GlassFish Communications Server 2.0 ((v2.1 Patch11)(9.1_02 Patch17)) (build b01-p05) OLP and CLB is enabled. Best Regards, Harri |
|
|
Re: CPU consuming thread, help to analyze
by Binod
::
Rate this Message:
It is the selector thread that selects a set of keys that are ready
for IO operations. Hope you are using latest JDK 1.6 available (just to make sure that there is no selector spinning issues with your JDK). Alexy might know if there is any known selector spinning issues with grizzly 1.8.x... - Binod. On 17-Aug-10, at 6:23 PM, Harri Jaakkola wrote: > > Hi, > Bear with me, I am not very familiar in Sailfin/Glassfish code, but > I hope > you are the ones to help... > > I have been running a small 2 instance SGCS cluster with very basic > SIP and > HTTP towards simple test servlets for some hours, and after shutting > down > the client, I can still after several idle hours see ONE of the > instances > consuming CPU. I did some analysis and think this may be the consuming > thread: > > "Thread-15" prio=10 tid=0x00002aab7a7d0000 nid=0x448b runnable > [0x0000000041a08000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java: > 215) > at > sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java: > 69) > - locked <0x00002aaab75fb3b8> (a sun.nio.ch.Util$1) > - locked <0x00002aaab75fb3d0> (a > java.util.Collections$UnmodifiableSet) > - locked <0x00002aaab75f3b68> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) > at > com.sun.grizzly.TCPSelectorHandler.select(TCPSelectorHandler.java:469) > at com.sun.grizzly.Controller.doSelect(Controller.java:369) > at > com.sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java: > 82) > at > com > .sun.grizzly.Controller.startSelectorHandlerRunner(Controller.java: > 1136) > at com.sun.grizzly.Controller.start(Controller.java:943) > at com.sun.grizzly.Controller.run(Controller.java:813) > at java.lang.Thread.run(Thread.java:619) > > Any ideas of what can cause this? What does this thread do? > > I am currently on SGCS, > Sun GlassFish Communications Server 2.0 ((v2.1 Patch11)(9.1_02 > Patch17)) > (build b01-p05) > > OLP and CLB is enabled. > > Best Regards, > Harri > > -- > View this message in context: http://old.nabble.com/CPU-consuming-thread%2C-help-to-analyze-tp29449258p29449258.html > Sent from the SailFin - Development mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: CPU consuming thread, help to analyze
by Oleksiy Stashok
::
Rate this Message:
Hi,
which JDK and OS are you using? Thanks. WBR, Alexey. PS: can you pls. cc me, cause I'm not on the sailfin list. On Aug 17, 2010, at 17:07 , Binod PG wrote: > It is the selector thread that selects a set of keys that are ready > for IO operations. > > Hope you are using latest JDK 1.6 available (just to make sure that > there is no selector spinning > issues with your JDK). > > Alexy might know if there is any known selector spinning issues with > grizzly 1.8.x... > > - Binod. > > On 17-Aug-10, at 6:23 PM, Harri Jaakkola wrote: > >> >> Hi, >> Bear with me, I am not very familiar in Sailfin/Glassfish code, but >> I hope >> you are the ones to help... >> >> I have been running a small 2 instance SGCS cluster with very basic >> SIP and >> HTTP towards simple test servlets for some hours, and after >> shutting down >> the client, I can still after several idle hours see ONE of the >> instances >> consuming CPU. I did some analysis and think this may be the >> consuming >> thread: >> >> "Thread-15" prio=10 tid=0x00002aab7a7d0000 nid=0x448b runnable >> [0x0000000041a08000] >> java.lang.Thread.State: RUNNABLE >> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) >> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java: >> 215) >> at >> sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65) >> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java: >> 69) >> - locked <0x00002aaab75fb3b8> (a sun.nio.ch.Util$1) >> - locked <0x00002aaab75fb3d0> (a >> java.util.Collections$UnmodifiableSet) >> - locked <0x00002aaab75f3b68> (a sun.nio.ch.EPollSelectorImpl) >> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) >> at >> com.sun.grizzly.TCPSelectorHandler.select(TCPSelectorHandler.java: >> 469) >> at com.sun.grizzly.Controller.doSelect(Controller.java:369) >> at >> com >> .sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java:82) >> at >> com >> .sun.grizzly.Controller.startSelectorHandlerRunner(Controller.java: >> 1136) >> at com.sun.grizzly.Controller.start(Controller.java:943) >> at com.sun.grizzly.Controller.run(Controller.java:813) >> at java.lang.Thread.run(Thread.java:619) >> >> Any ideas of what can cause this? What does this thread do? >> >> I am currently on SGCS, >> Sun GlassFish Communications Server 2.0 ((v2.1 Patch11)(9.1_02 >> Patch17)) >> (build b01-p05) >> >> OLP and CLB is enabled. >> >> Best Regards, >> Harri >> >> -- >> View this message in context: http://old.nabble.com/CPU-consuming-thread%2C-help-to-analyze-tp29449258p29449258.html >> Sent from the SailFin - Development mailing list archive at >> Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
Re: CPU consuming thread, help to analyze
by Harri Jaakkola
::
Rate this Message:
Hi,
I am a 64 bit user with /opt/java/bin/java -version java version "1.6.0_16" Java(TM) SE Runtime Environment (build 1.6.0_16-b01) Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode) and cat /etc/SuSE-release SUSE Linux Enterprise Server 10 (x86_64) VERSION = 10 PATCHLEVEL = 3 Regards, Harri
|
|
|
Re: CPU consuming thread, help to analyze
by Binod
::
Rate this Message:
I just checked with Alexy. It sounds like a selector spinning issue
in grizzly 1.8.x that is part of sailfin build you are using. thanks, Binod. On 19-Aug-10, at 1:44 PM, Harri Jaakkola wrote: > > Hi, > I am a 64 bit user with > > /opt/java/bin/java -version > java version "1.6.0_16" > Java(TM) SE Runtime Environment (build 1.6.0_16-b01) > Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode) > > and > > cat /etc/SuSE-release > SUSE Linux Enterprise Server 10 (x86_64) > VERSION = 10 > PATCHLEVEL = 3 > > > Regards, > Harri > > > > Oleksiy Stashok wrote: >> >> Hi, >> >> which JDK and OS are you using? >> >> Thanks. >> >> WBR, >> Alexey. >> >> PS: can you pls. cc me, cause I'm not on the sailfin list. >> >> On Aug 17, 2010, at 17:07 , Binod PG wrote: >> >>> It is the selector thread that selects a set of keys that are ready >>> for IO operations. >>> >>> Hope you are using latest JDK 1.6 available (just to make sure that >>> there is no selector spinning >>> issues with your JDK). >>> >>> Alexy might know if there is any known selector spinning issues with >>> grizzly 1.8.x... >>> >>> - Binod. >>> >>> On 17-Aug-10, at 6:23 PM, Harri Jaakkola wrote: >>> >>>> >>>> Hi, >>>> Bear with me, I am not very familiar in Sailfin/Glassfish code, but >>>> I hope >>>> you are the ones to help... >>>> >>>> I have been running a small 2 instance SGCS cluster with very basic >>>> SIP and >>>> HTTP towards simple test servlets for some hours, and after >>>> shutting down >>>> the client, I can still after several idle hours see ONE of the >>>> instances >>>> consuming CPU. I did some analysis and think this may be the >>>> consuming >>>> thread: >>>> >>>> "Thread-15" prio=10 tid=0x00002aab7a7d0000 nid=0x448b runnable >>>> [0x0000000041a08000] >>>> java.lang.Thread.State: RUNNABLE >>>> at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) >>>> at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java: >>>> 215) >>>> at >>>> sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65) >>>> at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java: >>>> 69) >>>> - locked <0x00002aaab75fb3b8> (a sun.nio.ch.Util$1) >>>> - locked <0x00002aaab75fb3d0> (a >>>> java.util.Collections$UnmodifiableSet) >>>> - locked <0x00002aaab75f3b68> (a sun.nio.ch.EPollSelectorImpl) >>>> at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80) >>>> at >>>> com.sun.grizzly.TCPSelectorHandler.select(TCPSelectorHandler.java: >>>> 469) >>>> at com.sun.grizzly.Controller.doSelect(Controller.java:369) >>>> at >>>> com >>>> .sun.grizzly.SelectorHandlerRunner.run(SelectorHandlerRunner.java: >>>> 82) >>>> at >>>> com >>>> .sun.grizzly.Controller.startSelectorHandlerRunner(Controller.java: >>>> 1136) >>>> at com.sun.grizzly.Controller.start(Controller.java:943) >>>> at com.sun.grizzly.Controller.run(Controller.java:813) >>>> at java.lang.Thread.run(Thread.java:619) >>>> >>>> Any ideas of what can cause this? What does this thread do? >>>> >>>> I am currently on SGCS, >>>> Sun GlassFish Communications Server 2.0 ((v2.1 Patch11)(9.1_02 >>>> Patch17)) >>>> (build b01-p05) >>>> >>>> OLP and CLB is enabled. >>>> >>>> Best Regards, >>>> Harri >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/CPU-consuming-thread%2C-help-to-analyze-tp29449258p29449258.html >>>> Sent from the SailFin - Development mailing list archive at >>>> Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscribe@... >>>> For additional commands, e-mail: dev-help@... >>>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@... >> For additional commands, e-mail: dev-help@... >> >> >> > > -- > View this message in context: http://old.nabble.com/CPU-consuming-thread%2C-help-to-analyze-tp29449258p29479504.html > Sent from the SailFin - Development mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@... > For additional commands, e-mail: dev-help@... > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@... For additional commands, e-mail: dev-help@... |
|
|
|
|
|
RE: CPU consuming thread, help to analyze
by Harri Jaakkola
::
Rate this Message:
The JDK is packaged into the setup I am using which makes it kind of troublesome to do this verification on my own level. Sorry for this.
/Harri
|
| Free embeddable forum powered by Nabble | Forum Help |
