MSerraInsiel wrote:
> Hi all, We have a java web application (deployed on Tomcat 5.5 with java 1.4)
> that has never had CPU problems. Some
>
> days ago we deployed a new version, that had non significant differences,
> and since this deploy we got frequent CPU
>
> 100% usage. users could not w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MSerraInsiel,
On 3/20/2009 10:48 AM, MSerraInsiel wrote:
> java is 1.4.2, the SO is Linux, but we could not dump the consuming thread
> because of the -Xrs option. Now we removed it, but we have old libraries and
> no CPU problem. In an identical test
java is 1.4.2, the SO is Linux, but we could not dump the comsuming thread
because of teh -Xrs option. Now we removed it, but we have old libraries and
no CPU problem. In an identical test environment the same problem does not
arise, even with -Xrs option and new libraries version.
Any ideas?
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
MSerraInsiel,
On 3/20/2009 5:40 AM, MSerraInsiel wrote:
> Hi all, We have a java web application (deployed on Tomcat 5.5 with java 1.4)
> that has never had CPU problems.
Take thread dumps while the CPU is pegged. You didn't mention your Java
version
Hi, Andrea,
Look at this: http://iusr.spaces.live.com/blog/cns!69F4725ED815E770!408.entry
A summary of mine after resolving the same problem.
It's quite clear from the thread dump to tell which thread is running
into a JSP page.
Cheers,
Jerome
On Wed, May 7, 2008 at 10:19 PM, Andrea Di Muro <[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrea,
Andrea Di Muro wrote:
| Hello everyone, I have a Tomcat server with several domains configured
| and sometimes I can see that the tomcat process uses 100-190% (dual
| processor) and hangs up.
| I think that one of my customer has uploaded a j
