Hi Rainer,
now I got it what you mean about the steady state.
Thx Ingo
Rainer Jung schrieb:
Hi Ingo,
Ingo Düppe wrote:
Am I'm right, that with the following setting a reply_timeout is
detected when the tomcat doesn't reply within 10 seconds and it will
be set into error if mo
st started (so you need to add the %d value to make them match).
Some more hints about your config included below.
Regards,
Rainer
Ingo Düppe wrote:
Hello,
I found the following lines in my mod_jk.log every 20 to 30 seconds
for all of my instances.
[info] jk_ajp_common.c (1511): Writing
Hello,
I found the following lines in my mod_jk.log every 20 to 30 seconds for
all of my instances.
[info] jk_ajp_common.c (1511): Writing to client aborted or client
network problems
[info] jk_ajp_common.c (1996): (plexus12) request failed, because of
client write error without recovery in
in the dB, you just have to put the address of all the
machines in.
Then if one machine say gets a file upload, it sends that to all the
other machines, but through the direct port to bypass the clustering.
Maybe sorry couldnt help you more
- Original Message - From: "Ingo
up,
something like the MS GUID idea.
No pre-configuration required.
I think it would be very interesting to know why you doing this, think
the guys will then really be abe to give you some good idea's.
- Original Message - From: "Ingo Düppe"
<[EMAIL PROTECTED]&g
Hello,
i run an application within a tomcat cluster. Now I need a unique key
for each server node for the application. My first solution was a
property file within the war file. But this is not so handy on
deployment cycles.
Is there a better way to place a unique identify for each cluster n
Hi Chris,
you are totally right, I didn't saw the solution.
Thx
Ingo
Christopher Schultz schrieb:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ingo,
Ingo Düppe wrote:
is the http session id a global unique id within a tomcat 6.0.13 cluster?
I think a better question is wh
Hello,
is the http session id a global unique id within a tomcat 6.0.13 cluster?
I like to use it as a unique field within the db for user tracking, so
it should be unique within the cluster and time.
Regards
Ingo
-
To start
