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: gerhardus.geldenh...@gta-t
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 mor
range 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 e
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 Heer
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:
Hubert
-Original Message-
From: Toby Kurien [mailto:tobyis7...@gm
Hello,
We run a setup with 3 Apache servers with mod_jk (2.2.6 / 1.2.26) and 10
tomcat instances running on 5 servers (tomcat 5.5.26 / RHEL4).
We used the combination of connectionTimeout & connection_pool_timeout,
both set to 5min (connectionTimeout="30",
connection_pool_timeout=300). But we
Andre,
Have a look at http://www.informit.com/guides/content.aspx?g=java&seqNum=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
