Spring2.5 + Weblogic 10.1 + JPA (Kodo) = UnexpectedRollbackException

Question

Hi,
I'm facing a strange problem when creating a sample JPA application using Spring 2.5 and Weblogic 10.1.
The example consists of 2 entities, Team and Player. All works well with simple attributes, and with a OneToOne relation between Team and Player.
However, configuring a OneToMany relation from team to player (squad), and adding 2 players to the squad causes an UnexpectedRollbackException caused by a Weblogic RollbackException. It tells you to look for the nested exceptions, but they are nowhere to be found (domain log, server log, log4j log)
The same annotations, but used with hibernate and managing tx myself works perfect.
I provide the code and config below, if more is needed just shout.
Any ideas?
After I turned kodo logging on, I noticed tha 3 insert statements are inserted for players (although there are only 2)
Code and a previous discussion are available on [url http://forum.springframework.org/showthread.php?t=49018]. As the format there is very readable, and to avoid mistakes I post a link here, and not the full source again B-)
Ideas? Hints? Tips?
Thanks,
Nico

Answer 1

Hi,
In the mean time we identified the culprit.
The problem was caused because there was a foreign key on the database between Player and Team. Apparently, Kodo does not always perform the inserts in the "correct" order, and then you bump into a referential constraint error of course. (found this because a colleague could not reproduce the problem...his DB was created by the Mappingtool, which just creates an index but does not enforce referential integrity)
This error than was "swallowed" (logged at the - invisible - TRACE level of the kodo.Runtime log-channel) and converted into the puzzling UnexpectedRollbackException.
Another Kodo puzzler: my persistence.xml looks like this
     <persistence-unit name="sample" transaction-type="JTA">
          <provider>kodo.persistence.PersistenceProviderImpl</provider>
          <jta-data-source>jdbc/testapp</jta-data-source>
          <properties>
               <property name="openjpa.Connection2UserName" value="usr" />
               <property name="openjpa.Connection2Password" value="pwd" />
               <property name="openjpa.Connection2URL"
                    value="jdbc:oracle:thin:@db-info" />
               <property name="openjpa.Connection2DriverName"
                    value="oracle.jdbc.driver.OracleDriver" />
               <property name="kodo.Log" value="SQL=TRACE, JDBC=TRACE, Runtime=TRACE" />
               <property name="kodo.ConnectionFactoryProperties"
                    value="PrettyPrint=true, PrettyPrintLineLength=100" />
          </properties>
     </persistence-unit>
If I omit the connection info, and only specify the datasource, it fails to collect the sequence_table...I read about this in [url http://forums.bea.com/thread.jspa?threadID=300004109], but it seems odd to me...
I want to hide the connection info from my application by using a datasource, but am forced to specify it anyway for my persistence "helper"...