On Fri, Sep 2, 2011 at 9:26 PM, Konstantin Kolinko <knst.koli...@gmail.com> wrote: > 2011/9/2 Javier Barroso <javibarr...@gmail.com>: >> That mean that I can use channelSocket.maxPort in tomcat 6.0.20 ? I >> read about an new alias maxport, but I suppose I can use still >> channelSocket.maxPort. > > Only if you are lucky, because it depends whether port or maxPort is > set first (in that old version of Tomcat). > https://issues.apache.org/bugzilla/show_bug.cgi?id=49521 > > You may have better luck with upgrading *.sh scripts in bin and > enabling CATALINA_PID file. Later versions of those scripts do check > whether other instance is running before starting Tomcat using the > value in CATALINA_PID file. It might be easier to you than upgrading > Tomcat itself. Ok, I guess I should not have many problem from tomcat point of view (we have a very basic (well, somethings are cluster configured and that is not basic (should all tomcat from cluster have the same version, or I can update one by one?))), but our customers tell us "tested with tomcat 6.0.xx (where xx is fixed)" ..
>> Upgrading all tomcats here could be a problem >> with applications :( > > 1. Upgrading 6.0.x to 6.0.y there should not be any issues in applications. > > The following web form allows to compare configuration files between releases: > http://tomcat.apache.org/migration.html#Tomcat_6.0.x_configuration_file_differences Thank you for that link! It seems very useful > > 2. If you keep using the old version you should consider the issues listed on > http://tomcat.apache.org/security-6.html Ok, I could use that as excuses for my boss (they say ("if work, don't touch")) Thank you very much! --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
