Changed the code to have the connection within the user transaction it now works.
Thanks JBoss Support!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3837050#3837050
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3837050
Thanks for the quickly reply. I put on the tracing as recommended and here is the
rollback section:
2004-05-19 14:19:36,814 TRACE
[org.jboss.resource.connectionmanager.JBossManagedConnectionPool] supplying
ManagedConnection from pool: [EMAIL PROTECTED]
2004-05-19 14:19:36,814 TRACE
Here is the DB logs. I see an autocommit=1 and no transaction markers, so that is why
it is not rolling back. Any idea why?
040519 15:43:23 17 Connect [EMAIL PROTECTED] on eCity
| 17 Init DB ecity
| 17 Query select round('inf'),
That is because you are still allocating the connection in ejbCreate()
If you really want to do this (I don't recommend it) you need to:
1) Change deploy/transaction-service.xml to have SpecComplaint=true
2) Define a resource-ref for your ejb that has something like the
following example taken
Read READ THIS FIRST on how to debug transaction problems.
You might also find it useful to set TRACE loggin on org.jboss.ejb.plugins
Throwing Exception does not cause a transaction rollback.
Exiting a method without doing a commit() or rollback() on your user transaction
is an error on your
