ncorrect log level "warn") is corrected in the
next release (by changing documentation and default - not code), the first
thing, throwing out fdatasync - should still be done.
Greetings,
Rainer Jung
At 10:54 20.04.01 , you wrote:
Could you be more explicit.
OS, mod_
We're using apache 1.3.33 with tomcat 5.0.16, connected via mod_jk, on
Solaris.
This is very outdated. You shuld update to TC 5.0.30 and mod_jk 1.2.8.
What I'm observing is that load-balancing isn't working. We have a
couple of machines dedicated to our XML interface, and have apache
Now,
Depends on the OS. Usually the system decides which interface to use
depending on the routing table. E.g. on Solaris:
netstat -rnv shows:
Destination Mask Gateway Device Mxfrg
Rtt Ref Flg Out In/Fwd
---
Hi Dennis,
i tried with
15/conf/server.xml:tcpListenAddress=192.168.0.180
25/conf/server.xml:tcpListenAddress=192.168.0.30
and otherwise the same cluster config which you posted on tomcat-dev. No
problem with membership and multicast, no exception.
So there must
Hi Dennis,
assuming you have a valid cluster config you don't need to start/stop the
DeltaManager yourself.
Session attributes are only replicated, if they are serializable and the
changes to the attributes are applied via setAttribute. If your attribute
e.g. is a HashMap and you change an entry
See, the thing is, we have a 3rd party library that saves information in
the session. It doesn't call setAttribute every time it changes the
data. DeltaManager appears to ignore the useDirtyFlag. With
SimpleTcpReplicationManager, I can set useDirtyFlag to false and we get
the desired
For some reason during startup tomcat writes (!) the file
tomcat-users.xml. It does it in the way that it writes to
tomcat-users.xml.new and then renames that file to tomcat-users.xml. At
least that's what was in the 5.0 code. I assume that didn't change with
5.5.
As a consequence the user
CVS head now includes an improvement:
1) If the directory containing tomcat-users.xml is not writeable you
will get a nice warning instead of a strange exception.
2) You can configure the MemoryUserDatabase with the attribute
readonly=true. Then there will be not write attempt at all.
Take a look at
./org/apache/catalina/util/ServerInfo.properties
in CATALINA_HOME/server/lib/catalina.jar.
It contains:
server.info=Apache Tomcat/5.5.10
server.number=5.5.10.0
You can put different values in there and deploy the new properties file in
directory before lib directory in it.
Paul Singleton wrote:
Rainer Jung wrote:
Take a look at
./org/apache/catalina/util/ServerInfo.properties
in CATALINA_HOME/server/lib/catalina.jar.
It contains:
server.info=Apache Tomcat/5.5.10
server.number=5.5.10.0
You can put different values
That should not work!
The correct way to configure session stickyness is to use jvmRoute (which
you already did) and then giving the workers the same names as the
jvmRoute. That is instead of bl_worker_dev use dev_alexis and instead
of bl_worker_noah use noah_alexis as the worker names.
You
OK, thanks Mladen: I have to correct myself.
1) Traditional use
Until mod_jk 1.2.6 there was no concept of domains. You had to specify the
worker name to be exactly the same as the jvmRoute to make sticky sessions
work. This way of configuring stickyness is wel known to mod_jk users.
2) I
/ balance_workers
- sticky_session (1)
- sticky_session_force (0)
- method (0=BYREQUESTS)
- lock (O=OPTIMISTIC)
- recover_time (60, also mimimum 60)
per balanced worker:
- lbfactor (1)
- domain (NULL)
- redirect (NULL)
- disabled (0)
- stopped (0)
I hope this helps.
Viel Spaß wünscht
Rainer Jung
I think having multiple load balancing workers for the same group of
target servers is not a problem.
You simply define load balancers e.g. lb1, lb2 etc.
Which load balancer is chosen is determined by your JkMount directives. So
if you have different apps app1, app2 etc. on your tomcats having
redirect etc. attributes.
Sorry!
Rainer Jung wrote:
The balanced workers behind lb1, lb2 etc. are allowed to have the same
name, because each load balancer has it's own list of balanced workers
with associated attributes. I expect no problem from a clash of names of
balanced workers
Hi Steve,
not a bug in 1.2.6 either:
You have used the attribute balance_workers:
worker.router.balance_workers=worker1,worker2
Version 1.2.6 only knew about balanced_workers. See the tiny difference?
In 1.2.14 you can use either of both and balance_workers take precendence.
Steve Dodge
Which platform/OS? I've no experience on Win, but I never experienced a
tomcat crash on unix/linux. Nevertheless five comments:
0) jk2 is no longer under development. The only active connector
development for apache is mod_jk and mod_proxy (for the upcoming apache
2.1/2.2).
1) If you really want
Hi,
that should be fixed in 5.0.30 and in 5.5. Compare
http://cvs.apache.org/viewcvs.cgi/jakarta-tomcat-catalina/modules/cluster/src/share/org/apache/catalina/cluster/session/DeltaRequest.java?r1=1.7r2=1.7.2.1diff_format=h
and
http://issues.apache.org/bugzilla/show_bug.cgi?id=31328.
We use a
Hi,
documentation says:
Display ... the number of currently active sessions that fall within
ten-minute ranges of their actual timeout times.
Actual timeout times does not mean from now, but instead in general.
It does not relate to when the session has been used last time. Since all
sessions
19 matches
Mail list logo
