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 issu
2014-07-08 11:27 GMT+04:00 Xavier Outhier :
> 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 previo
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
These errors may happen when you have two libraries that both contain the
class javax.persistence.spi.PersistenceProvider
search the libraries (*.jar) in both tomcat and your WAR file, and see if
there are multiple instances of the above named class
On Thu, Jul 3, 2014 at 9:28 AM, Xavier Outhier
Hi,
we have an application that is running under Tomcat. We are trying to upgrade
to latest version 7.0.54 from 7.0.39.
As 7.0.54 lead to some errors, we tried to find out which version broke the
application. The result is that the issue appears with 7.0.52 and is not
present until 7.0.50.
The
