On Mon, May 18, 2015 at 12:30 PM, Mark Thomas markt at apache.org wrote:
Once a request/response has been put into async mode, control passes to
the async processing. i.e. from that point onwards the container should
not be writing to the response until the application returns control to
the
Hi Christopher and all,
Since JavaMelody is quite often named to monitor Tomcat in this mailing list
and is open-source, JavaMelody could be added in the FAQ/Monitoring wiki
page indeed. I can send a one phrase description if you want.
Or can someone add me in the ContributorsGroup of the Tomcat
Zoran Avtarovski wrote
5. Garbage collector time spikes to 24.0. I think with JavaMelody it means
that GC took 24% of of the CPU??
Yes, 24% in % GC time in JavaMelody means that 24% of the CPU. And this is a
lot, if longer than a few seconds.
Zoran Avtarovski wrote
So I think our issues are
Hi Miguel,
First, javamelody.war is *optional*. I suggest to try javamelody without
using it.
You may read the user guide for help with this:
http://code.google.com/p/javamelody/wiki/UserGuide
(if you have an exception, please copy the complete stack-trace)
Then, there is an issue with Tomcat
Hi all,
I work on JavaMelody and I can speak about the question of jconsole or
javamelody for Tomcat monitoring.
The main differences between jconsole and javamelody is IMHO that jconsole will
be used occasionally in QA or production for a few minutes or a few hours,
whereas javamelody will be
