As stated below profiling (Yourkit is a very good recommendation, you can try
their early access version http://www.yourkit.com/eap/index.jsp) will give you
more insight in your tomcat application.
Sometimes changing your memory / garbage collect parameters can change the
world for you. For
Well... as far as I know there is an option to check if a backend is
available (up to a certain level).
Look in the documentation for ping_mode (mod_jk 1.2.27)
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
Hubert
-Original Message-
From:
to tomcat
failed (recoverable), (attempt=2)
[Mon Feb 02 13:45:18 2009] [8645:3086362304] [error]
ajp_service::jk_ajp_common.c (2426): (host_1) connecting to tomcat
failed.
[Mon Feb 02 13:45:18 2009] host_1 127.0.0.1 POST
/hv/main/nav/processflightqry HTTP/1.1 34.101650
Regards,
Hubert de
default reply_timeout
Hubert de Heer wrote:
Hi,
worker.host_1.socket_timeout=15
This is the root of the problem
cause it imposes the timeout on any socket operation
between mod_jk and tomcat.
What we notice is that Apache will respond with an error 502 Bad Gateway
when a response
Hi,
If you really, really need the manager webapp, you can restrict access
to that one not only by password but also by source-ip, e.g. access is
only allowed from your office IP.
In server.xml:
Context path=/manager
docBase=${catalina.home}/server/webapps/manager debug=0
privileged=true
+DisableReuse and our current
thread busy count dropped to an average of 8.
So we will stick with the DisableReuse and find another use for 2 out of
5 tomcat servers.
Regards,
Hubert de Heer
-Original Message-
From: Bernardo Cabezas [mailto:ber...@bergantells.net]
Sent: 12 January 2009 13:01
Andre,
Have a look at http://www.informit.com/guides/content.aspx?g=javaseqNum=253
for more details about JVM.
A bit more difficult to read but with tons of info about JVM behaviour and
default settings: http://java.sun.com/javase/technologies/hotspot/vmoptions.jsp
So for the SurvivorRatio the
