Thanks for the reply. If we upgrade to 3.2.4, it means we won't have any
more HTTP 500 Internal Server Error?

Marina


-----Original Message from Denis Balazuc on December 10, 2001 5:09 PM


Unless you are willing to spend a little bit of time reconfiguring Tomcat,
and maybe modify your install scripts, you can stick to Tomcat 3.2.x
(currently 3.2.4). So you can upgrade from 3.2.2 to 3.2.4 without any
worries. Just make sure you keep a copy of your webapps and your server.xml
file.

If you want to move to Tomcat 4.0.x, this will require a bit of
configuration and deployement, so it's up to you.
You should not have to change your servlets code however, even not have to
recompile it, so it's a smooth transition.
I actually spent more time reading Tomcat 4.0 docs than actually installing
and migrating my 3.2 webapps.....

However, I have ran into a slight problem....
Our include statements <@include> were a bit messy... althought Tomcat 3.2
was happy with the mess, Tomcat 4.0 is stricter and we had to change our
includes (actually clean them) to have our webapps 100% functional....but
this is only because we did things wrong (I think...) and that 3.2 was
accepting the wronginess of our code....

Hope this helps
Denis



----- Original Message from "Pieters, Marina" on December 10, 2001 04:51 PM

> Our company has a web application created by Java servlets; and this
> application runs on the Apache/Tomcat  server (Sun). Since July 2001,  the
> server was down with the" HTTP 500" error message about 12 times. Each
time,
> we have to restart Tomcat"; but lately, this problem occurs more
frequently.
>
>
> Our version of Tomcat is 3.2.2. We have been told that there might be a
bug
> in that version. We are planning to upgrade to the latest version 4.0.x.
> Where can we find the information about how to upgrade to the new version?
> Do we need to recompile the code? Is it the right decision to upgrade to
an
> other version? or is there better solution to avoid this problem?
>
> Thanks in advance.
>
> Marina
>
> --
> To unsubscribe:   <mailto:[EMAIL PROTECTED]>
> For additional commands: <mailto:[EMAIL PROTECTED]>
> Troubles with the list: <mailto:[EMAIL PROTECTED]>

--
To unsubscribe:   <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>

Reply via email to