Thank you Konstantin for pointing this out. This was not visible in the Release Notes nor on the migration page Apache Tomcat - Migration Guide - Tomcat 7.0.x (see at the end for migration from 7.0.x to 7.0.y). Anyway I'm still confused that the same library loaded twice could cause such an issue.
Thanks, Xavier. Apache Tomcat - Migration Guide - Tomcat 7.0.x Select a configuration file, old version and new version from the boxes below and then click "View differences" to see the differences. The differences will be shown in a new tab/window. View on tomcat.apache.org Preview by Yahoo On Tuesday, July 8, 2014 10:09 AM, Konstantin Kolinko <knst.koli...@gmail.com> wrote: 2014-07-08 11:27 GMT+04:00 Xavier Outhier <xouth...@yahoo.fr>: > Hi Filip, > > thanks for the tip. It was effectively a duplicated jar in the war and in the > common lib of tomcat: it was jpa.jar. :) > What I do not understand is how the same jar can cause an issue, especially > when it was working fine with previous version of Tomcat. > There must be something that has been changed between 7.0.50 and 7.0.52. %| > There was a change in 7.0.52. Explained here: https://issues.apache.org/bugzilla/show_bug.cgi?id=55943#c13 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
