> Internal / external, it's just a matter of preference and what works for your
> app. The internal (i.e. bundled with the JVM) classes are more convenient to
> use, but you have no choice
> as to the version you get. With external JARs you can use a specific
> version, often more recent than
Hello,
My problem is not directly related to Tomcat but to any web container...
A while ago we developed a webservice interface to our Java web-app. At that
time we needed Java 5 compatibility, that's why we used the JAX-WS RI 2.2.5
package.
Now we increased the system requirement for our web-
Hello,
we have a problem on a customer's server which we never had in many years of
working with Tomcat.
The customer runs a Windows 2008R2 with Tomcat 6.0.29 und Java 1.6.0_20
The situation when the problem occurs is always this:
Our web-apps logs that suddenly the MS SQL Server on the same serv
> That sounds like you looked at ps or similar output, not a thread dump. Take
> an actual JVM thread dump and see where the worker threads are during the
> busy periods.
Wrong, to identify the thread in question I looked with Sysinternals Process
Explorer which thread ID caused the 100% CPU.
-Ursprüngliche Nachricht-
Von: André Warnier [mailto:a...@ice-sa.com]
Gesendet: Mittwoch, 20. Juli 2011 11:06
An: Tomcat Users List
Betreff: Re: server status reports long request times
Hello Andre
"a certain client" related to the entries in the "client" column of the
mentioned serve
Hello,
>From time to time we have customers experiencing Tomcat going to 100% CPU.
>One customer sent us the output from the server status page from the Tomcat
>6.0.32 Manager web-app. This page reports a lot of HTTP connector requests
>belonging to a certain client with stage value "S" and "
Hmm, context.xml? I know only of server.xml. At least on Windows. Here is a
context snippet for server.xml which disables session persistence.
Michael
-
To unsubscribe,
