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 - but it was definitely a change in tomcat (51 or so) that resulted in the issue(s). Just something to keep in mind. 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 >
