and you'll also have to factor in a little re-configuration too, for example 
the much-debated logging (i.e Logger removal in 5.5), and also a slightly 
different JNDI datasource setup. if it's any interest to you we've had 5.5.4 
(sensibly or not) running our production and dev servers for 2 weeks with only 
1 issue which was related to a connector anyway I think.

Allistair.

> -----Original Message-----
> From: Tim Funk [mailto:[EMAIL PROTECTED]
> Sent: 29 November 2004 16:39
> To: Tomcat Users List
> Subject: Re: Tomcat 5.0.x or 5.5.x in production
> 
> 
> 5.5.5 is about to be tagged "soon." (See the dev list)
> 
> If there are no showstoppers in that release - I (IMO) would say its 
> realistic to start consider moving your 5.0.X releases to 
> 5.5. But be warned 
> that if you have custom modules (valves, realms, etc) against 
> 5.0 - you will 
> need to recompile them (and of course test).
> 
> -Tim
> 
> David Boyer wrote:
> 
> > We've been using Tomcat 5.0.x in production for the past 
> nine months or
> > so. There appear to be numerous benefits to moving to 5.5.x, not the
> > least of which being that it's the current focus of development.
> >  
> > With 5.5.4 being labeled 'stable', I'm interested in moving 
> our sites
> > to 5.5.x.
> >  
> > Is 5.5.4 being regarded as being at least as stable/reliable as
> > 5.0.28?
> >  
> > Thanks!
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> 
-------------------------------------------------------
QAS Ltd.
Developers of QuickAddress Software
<a href="http://www.qas.com";>www.qas.com</a>
Registered in England: No 2582055
Registered in Australia: No 082 851 474
-------------------------------------------------------
</FONT>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to