Hi
I'm running Tomcat 5.5.25 (eventually I'll be upgrading to the latest, but due
to my development team, I won't be able to quickly). I was wondering if the
new 1.2.28 is backwards compatible with Tomcat 5.5.25. I'd really like to use
some of the new features before upgrading to the new
Ya, right now it's a really big pain in the rear to maintain all these extra
configs, especially when we jump between different databases when they go under
maintenance, and multiply that between the number of applications we have
now...
If anybody else knows a way around this, I'd apprec
Hi,
I currently use deployment descriptor xml files to describe both the war file
to deployed and the session persistence info (configs+db info). Currently we
use a connectionURL that specifies db complete db info
(user/pass/db/port/sid)-- I would like to know if I can specify a datasourc
Hi,
We use a combination of Tomcat 5.5.25, mod_jk (v1.25) and sun one web server
(v6.1).The Sun Java web server points to 5 instances of tomcat as specified
in our obj.conf and worker.properties.
I know that currently if the application is not in a started state and Tomcat
is up and r
Hi,
I'm running Tomcat 5.5.25 on Solaris, and we are using a lot of environment
entries in our applications. I have the environment entry specified in the
conf/server.xml and also declared in the conf/context.xml.One thing I
noticed is that our server.xml continually populates it's own co
our JVM route to
jvmRoute="worker1", as I believe the jvmRoute value has to match the name
of the worker.
Filip
Eddie Yee wrote:
Hi,
I am not sure if this is a bug, but it appears that my sticky sessions
configuration don't want to stick. I am running two servers with tomca
Hi,
I am not sure if this is a bug, but it appears that my sticky sessions
configuration don't want to stick. I am running two servers with tomcat
5.5.20 (configured as single servers ie. no session replication) with
standard ajp13 connector (8009) and one web server running iPlanet 6 with
