Hi Romain,
Hi all,
finally I wrote a little sample to reproduce the strange JPA behavior.
Please, download it from github:
git clone https://github.com/diuis/test-jpa-tx.git
change directory:
cd test-jpa-tx/
and run TomEE 1.5.1:
mvn package tomee:run
I wrote a simple REST service; you could
Thanks for the report!
Here the fix: https://issues.apache.org/jira/browse/TOMEE-720
Using commons dbcp instead of tomcat jdbc you shouldn't get this behavior
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog:
Hi Romain,
yes, there are the 'adujsting persistence unit' lines in the log.
INFO: Auto-linking resource-ref 'jdbc/quartz' in bean
bravofly-scheduler-2.0-SNAPSHOT.Comp to Resource(id=jdbc/indexer)
Nov 12, 2012 9:44:35 AM org.apache.openejb.config.AutoConfig
processResourceRef
INFO: Auto-linking
It seems not that bad
do you think you can reproduce it in a unit test or a simple
maven/ant/gradle project?
*Romain Manni-Bucau*
*Twitter: @rmannibucau https://twitter.com/rmannibucau*
*Blog: **http://rmannibucau.wordpress.com/*http://rmannibucau.wordpress.com/
*LinkedIn:
I can try.
Thank you,
Demis Gallisto
--
View this message in context:
http://openejb.979440.n4.nabble.com/TomEE-1-5-1-SNAPSHOT-strange-JPA-behavior-tp4658500p4658533.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
