When the transaction starts to commit, a "Sychronization" object that
openjpa registered gets called and tries to flush the work your
session bean + jpa entities did to the database. Something is going
wrong during this flush but unfortunately the cause is not getting
logged. One possiblilty is that the tables weren't created
correctly in your database, perhaps because the non-jta-datasource is
not actually set up properly. You might be able to check the tables
using the admin console db browser or a 3rd party tool.
There's a jira open for this already, but I don't know if anyone is
actively working on fixing it.
thanks
david jencks
On Feb 5, 2009, at 10:31 PM, axiez wrote:
I have an entity being accessed through stateless session bean. JSE
Client
running on a different JVM accesses the bean. Client through
exception. Log
entries of application serve are given below which say TX required.
Isn't it
managed by container?
11:44:37,500 INFO [OpenEJB] invoking method create on a1/AccountBean
11:44:42,328 INFO [OpenEJB] finished invoking method create
11:45:05,765 INFO [Transaction] TX Required: Started transaction
org.apache.geronimo.transaction.manager.transactioni...@f2b103
11:45:06,375 INFO [Runtime] Starting OpenJPA 1.0.3
11:45:07,765 INFO [Transaction] TX Required: setRollbackOnly() on
transaction
org.apache.geronimo.transaction.manager.transactioni...@f2b103
11:45:07,843 INFO [Transaction] TX Required: Rolling back transaction
org.apache.geronimo.transaction.manager.transactioni...@f2b103
--
View this message in context:
http://www.nabble.com/-Transaction--TX-Required%3A-Started-transaction-tp21867304s134p21867304.html
Sent from the Apache Geronimo - Users mailing list archive at
Nabble.com.
