On Fri, May 29, 2015 at 3:30 PM, George Stanchev <gstanc...@serena.com> wrote:
> I don't see where he blamed the developers for anything. The poster even > admitted it was their fault. I think it is reasonable to warn the OP that > any change can result in issue. Even if you're doing everything correctly, > there is a change of running in a new Tomcat issue or a regression or what > not. > > We as developers know that corner cases that have 1% of happening occur > 50% of the time ;-) > > Any application server upgrade should be tested before deployed... > > My 2c > > George > > Thanks George. There was also the change to unpack WAR files by default to the webapps folder (or something along those lines) and the bug related to certain cases of not being able to turn that back off... "A known issue with FastDataInputStream (57173). See the changelog." Not intending to be antagonistic - just trying to give fair warning to OP. -----Original Message----- > From: André Warnier [mailto:a...@ice-sa.com] > Sent: Friday, May 29, 2015 12:12 PM > To: Tomcat Users List > Subject: Re: Problem specifying cipher suites in tomcat6 > > Sean Dawson wrote: > > I had significant problems trying to uncover a change in tomcat7 that > > broke our app when upgrading from 42 to 57, for a couple weeks over > > Christmas holidays. > > > > Turns out it was something we shouldn't have been doing - > > you mean, apart from top-posting here ? > > but it was > > definitely a change in tomcat (51 or so) that resulted in the issue(s). > > > > Just something to keep in mind. > > > > Well yes, but in all truth, if you were doing something which you should > not have been doing - and bonus points for admitting it - then you cannot > really blame the tomcat developers for making a change which broke it, even > over Christmas, can you ? > > At the contrary, you should be grateful : the fact that the change pointed > out the bad thing in your code, may have prevented the later advent of a > nuclear war. That would have been even less fun over Christmas. > > As a concession, maybe George's post below could have been prefixed with > "If your code is well-behaved, .." > > > > > > On Fri, May 29, 2015 at 11:43 AM, George Sexton <geor...@mhsoftware.com> > > wrote: > > > >> > >> On 5/29/2015 5:16 AM, David kerber wrote: > >> > >>> On 5/29/2015 3:32 AM, Ramon Pfeiffer wrote: > >>> > >>>> Sadly, it's a system I inherited last year and now have the pleasure > to > >>>> work with. I can't update Tomcat for I don't know what will break. > >>>> > >>> There's a fair chance that you can update to the latest version of TC 6 > >>> without anything breaking, but of course that's not guaranteed. > >>> > >> I can think of very few instances where a change in Tomcat broke my app. > >> The only one I can really remember was a change that I initiated :) > >> > >> > >> -- > >> George Sexton > >> *MH Software, Inc.* > >> Voice: 303 438 9585 > >> http://www.mhsoftware.com > >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
