Ronen,
The biggest issues I have seen are
1. Tomcat 4 strictly adheres to the DTD for the web.xml for web applications
where as some version of Tomcat 3 did not. The DTD for the web.xml is
specfied in the Servlet specs available at
http://java.sun.com/products/servlet/download.html. I do not remember the
actual error returned but it fairly obvious.
2. As specifed in the release notes for Tomcat 4
Starting with Tomcat 4.1.12, the invoker servlet is no longer available by
default in all webapp. Enabling it for all webapps is possible by editing
$CATALINA_HOME/conf/web.xml to uncomment the "/servlet/*" servlet-mapping
definition.
Using the invoker servlet in a production environment is not recommended and
is unsupported.
3. As specifed in the release notes for Tomcat 4
Unix symlinks will not work when used in a web application to link resources
located outside the web application root directory.
This behavior is optional, and the "allowLinking" flag may be used to
disable
the check.
I include an email from the list specifing the fix athough I have not
actually implemented it.
4. For the most CPU intensive webapp I saw a factor of 2 increase (>6 secs
to 3 to 4 secs) in speed. All others stayed about the same but they had sub
second responses to begin with so I was not expecting an increase.
5. Tomcat 4 comes with the Coyote JK connector turned on by default. But
the original JK/ajp connector is still available. The coyote connector is
technically for use with the JK2 module for apache2 but it appears to work
for JK with apache 1.3 and apache 2.0. It does load info from
$TOMCAT_HOME/conf/jk2.properties but the default file has everything
commented out. It would be good to validate you apps against both
connectors and see which works best for you. I am currently doing this on
our test server and so far have not noticed any significant difference.
Jeff
-----Original Message-----
From: Ronen Shenkar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 26, 2002 6:27 AM
To: Tomcat Users List
Subject: Tomcat 3.2 versus 4.1
Hi,
I'm considering upgrading from Tomcat 3.2 to Tomcat 4.1.
I wonder if the performance and other improvements between the two releases
are major and if the upgrade itself is painful.
Is there a document instructing how to do such an upgrade?
Thanks, ronen
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--- Begin Message ---
-----Original Message-----
From: Bob McCormick [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 21, 2002 12:18 PM
To: Tomcat Users List
Subject: RE: Status of Symbolic Links on Linux/TC 4.1.12???
OK - thanks. Didn't realize that this version is alpha. Don't wish to
play with an alpha version for what we're doing.
I was able to get this to work with 4.1.12 by the doing the following:
In the server.xml I turned on the context for ROOT and added a
<Resource> as follows:
<Context path="" docBase="ROOT" debug="0">
<Resources className="org.apache.naming.resources.FileDirContext"
allowLinking="true" caseSensitive="false" />
</Context>
I would imagine you can add the above Resource to any context and it
will follow the symlinks.
Thanks...Bob
On Thu, 2002-11-21 at 10:58, Turner, John wrote:
>
>
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.15-alpha/bi
> n/
>
> John
>
>
> > -----Original Message-----
> > From: Bob McCormick [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, November 21, 2002 1:50 PM
> > To: Tomcat Users List
> > Subject: Re: Status of Symbolic Links on Linux/TC 4.1.12???
> >
> >
> > Hi Bill,
> >
> > OK - sounds good. Now, how do I find the 4.1.15? I went to the
> > binaries and see that there is only 4.1.12. I a bit new to Tomcat, so
> > I'm groping a bit here.
> >
> > Thanks..Bob
> >
> >
> > On Wed, 2002-11-20 at 22:41, Bill Barker wrote:
> > > It should be pretty much working in 4.1.15 now (as long as
> > you configure the
> > > Resources yourself). From 4.1.13, you can also get it to
> > work by setting
> > > the caseSensitive="false" attribute on the Resources tag.
> > >
> > > "Bob McCormick" <[EMAIL PROTECTED]> wrote in message
> > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > > Hi All,
> > > >
> > > > Have checked the archives and see that someone was having
> > a problem with
> > > > being able to access URL's via Tomcat 4.1.x that contain
> > a symbolic
> > > > link. I too am having this problem and was hoping to
> > only use TomCat to
> > > > serve up content.
> > > >
> > > > Would anyone be able to tell me whether this is just an
> > overlooked bug,
> > > > specified setting in the security settings somewhere or
> > flat-out not
> > > > going to be something that is supported any longer. We'd
> > really like to
> > > > NOT have to use Apache to have on less thing to worry
> > about, and so any
> > > > information on this particular would be GREATLY appreciated.
> > > >
> > > > Thanks...Bob
> > > >
> > > > Bob McCormick
> > > > IST
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--- End Message ---
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
