Is there a reason to have both of the spring-tx bundles in there? I haven't
looked in the two Spring bundles you have listed here but my guess, based on
the "wrap" mention in the stack trace, is that the two bundles are not
created with OSGi manifests so you may be getting a race condition on
classloading. That's a wild ass guess so don't hold me to that. But first
I'd look to see if you need both of those spring transaction managers and
also look at the manifests in the jar/bundles to see if they are OSGi.

There's obviously a mismatch in the Aries bundle and the Spring Bundle that
is being used
org.apache.aries.transaction.internal.AriesPlatformTransactionManager to
org.springframework.transaction.PlatformTransactionManager

OSGi should be able to handle the different major versions but it appears
something is wrong in that regard.

spring-tx                               | 3.2.14.RELEASE_1 | x         |
spring-3.0.6                   | Spring 3.2.x Transaction (TX) support
spring-tx                               | 4.2.4.RELEASE_1  | x         |
spring-3.0.6



--
View this message in context: 
http://servicemix.396122.n5.nabble.com/JpaComponent-Fails-on-doStart-tp5725026p5725042.html
Sent from the ServiceMix - Dev mailing list archive at Nabble.com.

Reply via email to