Pardon the final line of my posting should have read:
So should we upgrade to Tomcat 4.1.31 or to 4.1.34 -
what is best practice given our problem?
"Nicolouw M. Kruger" <nick (AT) silvermoongroup (DOT) comwrote in message news:
"Mark Thomas" <markt (AT) apache (DOT) orgwrote in message
news:452922BA.7040307 (AT) apache (DOT) org
The Apache Tomcat team is proud to announce the immediate availability
of Tomcat 4.1.34 stable. This build contains numerous bug fixes,
documentation updates, and other improvements.
Apache Tomcat is an implementation of the Java Server Pages 1.2 and Java
Servlet 2.3 specifications.
Please refer to the release notes for a complete list of changes.
Downloads:
The Apache Tomcat Team
We are running Tomcat 4.1.29 on Windows 2003 Server at present with
multiple
WebApps of which some are very unstable in terms of session reliability,
especially those using the Model View Controller pattern. We were (until a
week ago) thinking of upgrading to Tomcat 4.1.31 but now this posting that
4.1.34 has now been voted stable. primary motivation to upgrade to
4.1.31 was due to major user issues with Tomcat session handling,
specifically timeouts that are occurring illogically; in fact almost
exactly
as described by Glenn Nielsen in Bugzilla bug 15463, comment #9, dated 3
May
#c9
(plus some other session bugs that were fixed in 4.1.31)
Now given the stable 4.1.34 we have to choose between upgrading from
4.1.29
to either 4.1.31 or 34 - it looks to us that going to 4.1.34 might be the
better choice (overall) since it is now the latest quality release from
Apache (plus it has the bug fixes that we wanted in 4.1.31) but then we
are
not sure if the API changes as per the 4.1.34 release notes could
complicate
our upgrade attempt. It appears that between 4.1.29 and 4.1.31 there were
no
internal changes at API release level, whereas for 4.1.34 several updates
are reported, e.g. Apache Ant (ant.jar) is at 1.5.1 for both Tomcat
4.1.29/31 but now at 1.6.5 in Tomcat 4.1.34.
So should we upgrade to 4.1.31 or to 4.1.31 - what is best practice given
our problem?
Your expert advice will be valued
Nicolouw
--
To start a new topic, e-mail: users (AT) tomcat (DOT) apache.org
To unsubscribe, e-mail: users-unsubscribe (AT) tomcat (DOT) apache.org
For additional commands, e-mail: users-help (AT) tomcat (DOT) apache.org

Nicolouw M. Kruger wrote:
Pardon the final line of my posting should have read:

So should we upgrade to Tomcat 4.1.31 or to 4.1.34 -
what is best practice given our problem?

Personally, I would upgrade to 4.1.34 (but I would say that wouldn't
I?). As well as the numerous Tomcat bug fixes the updates to the
libraries and the latest connectors also fix a number of issues.

The other advantage is that if you hit an issue and need a fix then
the upgrade to get that fix will be smaller.

Ultimately it is up to you.

Mark

To start a new topic, e-mail: users (AT) tomcat (DOT) apache.org
To unsubscribe, e-mail: users-unsubscribe (AT) tomcat (DOT) apache.org
For additional commands, e-mail: users-help (AT) tomcat (DOT) apache.org