You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by musafir <ne...@gmail.com> on 2015/08/18 17:50:55 UTC
cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57 (jdk7)..
os:centos 6.6 ...seeing high cpu spike after upgrade.... doing top
and thread dump shows only thread that is always using cpu is:
"ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon
prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on condition
[0x00007ff803ffe000]
java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1513)
at java.lang.Thread.run(Thread.java:745)
disabled backgroundProcessorDelay (backgroundProcessorDelay=-1)
..don't see any thread that is always using cpu..
Q: why backgroundProcessorDelay will cause cpu spike. Is this disabled
in tomcat6 by default?
Q: will disabling backgroundProcessorDelay cause any other
performance issues with tomcat7.
Thanks for Help!!
Regards
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Felix Schumacher <fe...@internetallee.de>.
Am 18.08.2015 um 19:08 schrieb Mark Thomas:
> On 18/08/2015 17:10, musafir wrote:
>> On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org> wrote:
>>
>>> On 18/08/2015 16:50, musafir wrote:
>>>> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57 (jdk7)..
>>>> os:centos 6.6 ...seeing high cpu spike after upgrade.... doing top
>>>> and thread dump shows only thread that is always using cpu is:
>>> How have you matched the thread using CPU in top with the thread in the
>>> thread dump?
>>>
>>> Mark
>>>
>>>
>>>> "ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon
>>>> prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on condition
>>>> [0x00007ff803ffe000]
>>>> java.lang.Thread.State: TIMED_WAITING (sleeping)
>>>> at java.lang.Thread.sleep(Native Method)
>>>> at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1513)
>>>> at java.lang.Thread.run(Thread.java:745)
>>>>
>>>> disabled backgroundProcessorDelay (backgroundProcessorDelay=-1)
>>>> ..don't see any thread that is always using cpu..
>>>>
>>>> Q: why backgroundProcessorDelay will cause cpu spike. Is this disabled
>>>> in tomcat6 by default?
>>>> Q: will disabling backgroundProcessorDelay cause any other
>>>> performance issues with tomcat7.
>>>>
>>>>
>>>> Thanks for Help!!
>>>>
>>>> Regards
>>>>
>>> Hi Mark
>>> pid java
>>>
>>> top -H -p pid for thread id cpu eating thread
>>>
>>> kill -3 pid for thread dump
>>>
>>> and hexa nid for thread id
> Then it looks like you did something wrong because the thread you
> identified is sleeping. It won't be using any CPU.
Maybe just at the wrong time.
Could it be, that you have lots of jars or webapps installed in your
tomcat, that are scanned for annotations? That would explain a
difference between tomcat 6 (no scan) and 7 (scan).
Regards,
Felix
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Musafir,
On 8/19/15 1:57 PM, musafir wrote:
> [The] thread was sleeping at that point of time during initial
> capture....ran jstack few times.. going through tomcat source for
> thisjava thread and verifying tomcat 7 config we identified
> reloadable was set true for one of the application's
> context..disabling it fixed issue ..
That suggests that your application is reloading a lot. Are there
issues with your clock and/or file timestamps in the future?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJV1N1aAAoJEBzwKT+lPKRYONcP/jTy6KCqahJQ/l0D5KJIFx7v
I0n2qoXCATR2nQtsmMR+O7lftgMYLrfzDCztj50GE/9OgOKlXHAWFizVEIfIv7a8
nOW31Sx6qNPQZxdjMvKwMGlP2epotc5k8LacnYlmZULUKABPOZ64g/qmT+AhHkI6
UdkqCie7jk+++297UGkoc8tQnjG6lRIklHR/5JlQD5DlVOdPGfGR7/D9r+p38Ac5
a+/Si1s5dnqM2wr3/xr547E6b83alN09hJDZmrvp4UfaJkYUVAsx1qNHecEVNouJ
0Jz5kUW0fuyo2d2PClvf7I5V+TpnZCiZb7NEFIYvo1Xuu7FdOwf/qzprSj0vMVNn
runOICA1egl1XSVZEIX1J3+gMc3EClhTyv9iTLdkSn7UBGZ2l/7E0uzgqDb2zmwf
bWz8BjCZShEI7iRaBqKGj7QhyVoDoiCKgEgpiQyn7TocTT4Kkj6e5ifjr47fEcnE
w6XToU9tDfM4EwU0b472V5l8Qj7fR+plu09wtpbp2tTYPOhGoNDBjWBEhUhzr3Jq
Ybn3MwDLBcHKTvfPOW+vyNNR3YifgafKKFCrfR8VcA78Ajz2tSes2DXytrZ5AEkC
ikuCZnVyZL0yjF6JJgvK0TaXKbAIBVvUNVn2nyVcrhwfThg9A3FYBnE0moZuOIf0
KteTytw3pXcfUyyo4LwI
=M0W4
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by musafir <ne...@gmail.com>.
On Tue, Aug 18, 2015 at 1:46 PM, Mark Thomas <ma...@apache.org> wrote:
> On 18/08/2015 18:16, Christopher Schultz wrote:
> > Musafir,
> >
> > On 8/18/15 1:08 PM, Mark Thomas wrote:
> >> On 18/08/2015 17:10, musafir wrote:
> >>> On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org>
> >>> wrote:
> >>>
> >>>> On 18/08/2015 16:50, musafir wrote:
> >>>>> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57
> >>>>> (jdk7).. os:centos 6.6 ...seeing high cpu spike after
> >>>>> upgrade.... doing top and thread dump shows only thread
> >>>>> that is always using cpu is:
> >>>>
> >>>> How have you matched the thread using CPU in top with the
> >>>> thread in the thread dump?
> >>>>
> >>>> Mark
> >>>>
> >>>>
> >>>>> "ContainerBackgroundProcessor[StandardEngine[Catalina]]"
> >>>>> daemon prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on
> >>>>> condition [0x00007ff803ffe000] java.lang.Thread.State:
> >>>>> TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native
> >>>>> Method) at
> >>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
> > run(ContainerBase.java:1513)
> >>>>>
> >>>>
> > at java.lang.Thread.run(Thread.java:745)
> >>>>>
> >>>>> disabled backgroundProcessorDelay
> >>>>> (backgroundProcessorDelay=-1) ..don't see any thread that is
> >>>>> always using cpu..
> >>>>>
> >>>>> Q: why backgroundProcessorDelay will cause cpu spike. Is this
> >>>>> disabled in tomcat6 by default? Q: will disabling
> >>>>> backgroundProcessorDelay cause any other performance issues
> >>>>> with tomcat7.
> >>>>>
> >>>>>
> >>>>> Thanks for Help!!
> >>>>>
> >>>>> Regards
> >>>>>
> >>>>
> >>>> Hi Mark pid java
> >>>>
> >>>> top -H -p pid for thread id cpu eating thread
> >>>>
> >>>> kill -3 pid for thread dump
> >>>>
> >>>> and hexa nid for thread id
> >
> >> Then it looks like you did something wrong because the thread you
> >> identified is sleeping. It won't be using any CPU.
> >
> > Assuming that the thread has been mis-identified, could it be this?
> >
> > https://bz.apache.org/bugzilla/show_bug.cgi?id=58151
> >
> > That bug was filed/fixed against trunk/8.0. Any chance there is a
> > similar bug in Tomcat 7?
>
> It doesn't look like it. That bug was introduced when the non-blocking
> I/O support was added in Tomcat 8. The reads in Tomcat 7 look OK.
>
> top + lwp id + thread dump is the way to get to the bottom of this.
> Something isn't right in the description above.
>
> Mark
>
thread was sleeping at that point of time during initial capture....ran
jstack few times.. going through tomcat source for thisjava thread and
verifying tomcat 7 config we identified reloadable was set true for one
of the application's context..disabling it fixed issue .. Appreciate
everyone's response..
[root@app01 logs]# echo $(date) && jstack -F 590848 |awk '/Thread
'593818:' /,/^$/'
Tue Aug 18 12:42:34 CDT 2015
Attaching to process ID 590848, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.75-b04
Thread 593818: (state = IN_NATIVE)
- java.io.UnixFileSystem.canonicalize0(java.lang.String) @bci=0 (Compiled
frame; information may be imprecise)
- java.io.UnixFileSystem.canonicalize(java.lang.String) @bci=140, line=172
(Compiled frame)
- java.io.File.getCanonicalPath() @bci=27, line=618 (Compiled frame)
- org.apache.naming.resources.FileDirContext.file(java.lang.String)
@bci=39, line=774 (Compiled frame)
-
org.apache.naming.resources.FileDirContext.doGetAttributes(java.lang.String,
java.lang.String[]) @bci=2, line=398 (Compiled frame)
-
org.apache.naming.resources.BaseDirContext.getAttributes(java.lang.String,
java.lang.String[]) @bci=41, line=1157 (Compiled frame)
-
org.apache.naming.resources.BaseDirContext.getAttributes(java.lang.String)
@bci=3, line=1110 (Compiled frame)
-
org.apache.naming.resources.ProxyDirContext.getAttributes(java.lang.String)
@bci=35, line=882 (Compiled frame)
- org.apache.catalina.loader.WebappClassLoader.modified() @bci=57,
line=1026 (Compiled frame)
- org.apache.catalina.loader.WebappLoader.modified() @bci=11, line=500
(Interpreted frame)
- org.apache.catalina.loader.WebappLoader.backgroundProcess() @bci=8,
line=420 (Compiled frame)
- org.apache.catalina.core.ContainerBase.backgroundProcess() @bci=70,
line=1345 (Compiled frame)
-
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(org.apache.catalina.Container,
java.lang.ClassLoader) @bci=27, line=1546 (Compiled frame)
-
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(org.apache.catalina.Container,
java.lang.ClassLoader) @bci=115, line=1556 (Compiled frame)
-
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(org.apache.catalina.Container,
java.lang.ClassLoader) @bci=115, line=1556 (Compiled frame)
-
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run()
@bci=108, line=1524 (Interpreted frame)
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)
[root@app01 logs]# echo $(date) && jstack -F 590848 |awk '/Thread
'593818:' /,/^$/'
Tue Aug 18 12:42:37 CDT 2015
Attaching to process ID 590848, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 24.75-b04
Thread 593818: (state = BLOCKED)
- java.lang.Thread.sleep(long) @bci=0 (Interpreted frame)
-
org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run()
@bci=46, line=1513 (Interpreted frame)
- java.lang.Thread.run() @bci=11, line=745 (Interpreted frame)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Mark Thomas <ma...@apache.org>.
On 18/08/2015 18:16, Christopher Schultz wrote:
> Musafir,
>
> On 8/18/15 1:08 PM, Mark Thomas wrote:
>> On 18/08/2015 17:10, musafir wrote:
>>> On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org>
>>> wrote:
>>>
>>>> On 18/08/2015 16:50, musafir wrote:
>>>>> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57
>>>>> (jdk7).. os:centos 6.6 ...seeing high cpu spike after
>>>>> upgrade.... doing top and thread dump shows only thread
>>>>> that is always using cpu is:
>>>>
>>>> How have you matched the thread using CPU in top with the
>>>> thread in the thread dump?
>>>>
>>>> Mark
>>>>
>>>>
>>>>> "ContainerBackgroundProcessor[StandardEngine[Catalina]]"
>>>>> daemon prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on
>>>>> condition [0x00007ff803ffe000] java.lang.Thread.State:
>>>>> TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native
>>>>> Method) at
>>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
> run(ContainerBase.java:1513)
>>>>>
>>>>
> at java.lang.Thread.run(Thread.java:745)
>>>>>
>>>>> disabled backgroundProcessorDelay
>>>>> (backgroundProcessorDelay=-1) ..don't see any thread that is
>>>>> always using cpu..
>>>>>
>>>>> Q: why backgroundProcessorDelay will cause cpu spike. Is this
>>>>> disabled in tomcat6 by default? Q: will disabling
>>>>> backgroundProcessorDelay cause any other performance issues
>>>>> with tomcat7.
>>>>>
>>>>>
>>>>> Thanks for Help!!
>>>>>
>>>>> Regards
>>>>>
>>>>
>>>> Hi Mark pid java
>>>>
>>>> top -H -p pid for thread id cpu eating thread
>>>>
>>>> kill -3 pid for thread dump
>>>>
>>>> and hexa nid for thread id
>
>> Then it looks like you did something wrong because the thread you
>> identified is sleeping. It won't be using any CPU.
>
> Assuming that the thread has been mis-identified, could it be this?
>
> https://bz.apache.org/bugzilla/show_bug.cgi?id=58151
>
> That bug was filed/fixed against trunk/8.0. Any chance there is a
> similar bug in Tomcat 7?
It doesn't look like it. That bug was introduced when the non-blocking
I/O support was added in Tomcat 8. The reads in Tomcat 7 look OK.
top + lwp id + thread dump is the way to get to the bottom of this.
Something isn't right in the description above.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Musafir,
On 8/18/15 1:08 PM, Mark Thomas wrote:
> On 18/08/2015 17:10, musafir wrote:
>> On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org>
>> wrote:
>>
>>> On 18/08/2015 16:50, musafir wrote:
>>>> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57
>>>> (jdk7).. os:centos 6.6 ...seeing high cpu spike after
>>>> upgrade.... doing top and thread dump shows only thread
>>>> that is always using cpu is:
>>>
>>> How have you matched the thread using CPU in top with the
>>> thread in the thread dump?
>>>
>>> Mark
>>>
>>>
>>>> "ContainerBackgroundProcessor[StandardEngine[Catalina]]"
>>>> daemon prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on
>>>> condition [0x00007ff803ffe000] java.lang.Thread.State:
>>>> TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native
>>>> Method) at
>>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.
run(ContainerBase.java:1513)
>>>>
>>>
at java.lang.Thread.run(Thread.java:745)
>>>>
>>>> disabled backgroundProcessorDelay
>>>> (backgroundProcessorDelay=-1) ..don't see any thread that is
>>>> always using cpu..
>>>>
>>>> Q: why backgroundProcessorDelay will cause cpu spike. Is this
>>>> disabled in tomcat6 by default? Q: will disabling
>>>> backgroundProcessorDelay cause any other performance issues
>>>> with tomcat7.
>>>>
>>>>
>>>> Thanks for Help!!
>>>>
>>>> Regards
>>>>
>>>
>>> Hi Mark pid java
>>>
>>> top -H -p pid for thread id cpu eating thread
>>>
>>> kill -3 pid for thread dump
>>>
>>> and hexa nid for thread id
>
> Then it looks like you did something wrong because the thread you
> identified is sleeping. It won't be using any CPU.
Assuming that the thread has been mis-identified, could it be this?
https://bz.apache.org/bugzilla/show_bug.cgi?id=58151
That bug was filed/fixed against trunk/8.0. Any chance there is a
similar bug in Tomcat 7?
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJV02hnAAoJEBzwKT+lPKRYHuYP/3rS+QDW1ERhFtj1UrZ2tuxJ
ds0Pw+SFY7x0SYW4WZrhEBRYSSgjwFH/Q7MZn6jaovh2Alk/xIfBsa9NKpsgGrfj
dqNJAQF8JEw47W+tphXqO+ZlSqkiCa1h7nBLdS6/I7Ev2202IPPeDfVxUxgM8IAE
2Qec2u3NkHrkmP0jMZmnJmB6LS8XuL/QEuuQoz/EtC9PQrMOZu3/p554zjq2qFO9
uQif3Iqf2c/ISfT0ETrSbwcM5wpjGJeSG9vyQ27cFCrSVEYJlvaWibycKLLOhH46
KmyQmTZ55O5Y7tI9dsIYzrWxhkxAHuzIsUadeW4X6+3FYNJzFccmiz6+WkqckBPl
ZbxRcH+ZoqgUYxE5Xdpxcyo4TbxU4AYCkwZzIS7kIhTVUi1Q07qcKKb8K9RX7YDI
b6psvp1KK0rU+gxwFDqdvwIshaS3R3fhSd1QF1d3oZz0VhGFQ6IUJBni2sp1n7Tf
/UvD9c7iXRrne5TfrGDu4GwxRcPyLBDOVjrOx70lGVajpyh8wOVWOSvaRwE2RIg6
4BbC/cAX89Ql8i1u5DwNsCOIGudOURqO6GvB4SZMbJHBWFFbFCxDa9YP2+UjWQbL
2lzR1FSYWD11TNuQbiUHaDzjxwsdWyzD/rLzXHAkBpl+PSBmDnGAxqUlv0w0UJnq
xuae1n8DDdkkJymSl8hM
=KDsj
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Mark Thomas <ma...@apache.org>.
On 18/08/2015 17:10, musafir wrote:
> On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org> wrote:
>
>> On 18/08/2015 16:50, musafir wrote:
>>> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57 (jdk7)..
>>> os:centos 6.6 ...seeing high cpu spike after upgrade.... doing top
>>> and thread dump shows only thread that is always using cpu is:
>>
>> How have you matched the thread using CPU in top with the thread in the
>> thread dump?
>>
>> Mark
>>
>>
>>> "ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon
>>> prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on condition
>>> [0x00007ff803ffe000]
>>> java.lang.Thread.State: TIMED_WAITING (sleeping)
>>> at java.lang.Thread.sleep(Native Method)
>>> at
>> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1513)
>>> at java.lang.Thread.run(Thread.java:745)
>>>
>>> disabled backgroundProcessorDelay (backgroundProcessorDelay=-1)
>>> ..don't see any thread that is always using cpu..
>>>
>>> Q: why backgroundProcessorDelay will cause cpu spike. Is this disabled
>>> in tomcat6 by default?
>>> Q: will disabling backgroundProcessorDelay cause any other
>>> performance issues with tomcat7.
>>>
>>>
>>> Thanks for Help!!
>>>
>>> Regards
>>>
>>
>> Hi Mark
>> pid java
>>
>> top -H -p pid for thread id cpu eating thread
>>
>> kill -3 pid for thread dump
>>
>> and hexa nid for thread id
Then it looks like you did something wrong because the thread you
identified is sleeping. It won't be using any CPU.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by musafir <ne...@gmail.com>.
On Tue, Aug 18, 2015 at 11:57 AM, Mark Thomas <ma...@apache.org> wrote:
> On 18/08/2015 16:50, musafir wrote:
> > Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57 (jdk7)..
> > os:centos 6.6 ...seeing high cpu spike after upgrade.... doing top
> > and thread dump shows only thread that is always using cpu is:
>
> How have you matched the thread using CPU in top with the thread in the
> thread dump?
>
> Mark
>
>
> > "ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon
> > prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on condition
> > [0x00007ff803ffe000]
> > java.lang.Thread.State: TIMED_WAITING (sleeping)
> > at java.lang.Thread.sleep(Native Method)
> > at
> org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1513)
> > at java.lang.Thread.run(Thread.java:745)
> >
> > disabled backgroundProcessorDelay (backgroundProcessorDelay=-1)
> > ..don't see any thread that is always using cpu..
> >
> > Q: why backgroundProcessorDelay will cause cpu spike. Is this disabled
> > in tomcat6 by default?
> > Q: will disabling backgroundProcessorDelay cause any other
> > performance issues with tomcat7.
> >
> >
> > Thanks for Help!!
> >
> > Regards
> >
>
> Hi Mark
> pid java
>
> top -H -p pid for thread id cpu eating thread
>
> kill -3 pid for thread dump
>
> and hexa nid for thread id
>
>
> Regards
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: cpu spike after upgrade from tomcat 6.0.36 to tomcat 7.0.57
Posted by Mark Thomas <ma...@apache.org>.
On 18/08/2015 16:50, musafir wrote:
> Hello, ugraded tomcat from 6.0.36(jdk 6) to tomcat7.0.57 (jdk7)..
> os:centos 6.6 ...seeing high cpu spike after upgrade.... doing top
> and thread dump shows only thread that is always using cpu is:
How have you matched the thread using CPU in top with the thread in the
thread dump?
Mark
> "ContainerBackgroundProcessor[StandardEngine[Catalina]]" daemon
> prio=10 tid=0x00007ff8fc599800 nid=0xc1d2e waiting on condition
> [0x00007ff803ffe000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1513)
> at java.lang.Thread.run(Thread.java:745)
>
> disabled backgroundProcessorDelay (backgroundProcessorDelay=-1)
> ..don't see any thread that is always using cpu..
>
> Q: why backgroundProcessorDelay will cause cpu spike. Is this disabled
> in tomcat6 by default?
> Q: will disabling backgroundProcessorDelay cause any other
> performance issues with tomcat7.
>
>
> Thanks for Help!!
>
> Regards
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org