You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this way i used the same transaction used by the extension to insert entities in my db, because if i create another transaction the ARJUNA016051: thread is already associated with a transaction! appears.
So, i was performing some test for a while and discover that everytime i execute any test that use the same transaction that APE( arquillian-persistence-extension ), the entity is persist first and the datasets after. So i'm wonder why this happen and the most importatn how can avoid it?
Greets
César
UPDATE-------------------
Here the trace from server
Hi, sorry for laaaaaate response. Does it still affect you with the latest version? Can you make a Gist or Github project out of it and report in JIRA?
I have this code:
In this way i used the same transaction used by the extension to insert entities in my db, because if i create another transaction the ARJUNA016051: thread is already associated with a transaction! appears.
So, i was performing some test for a while and discover that everytime i execute any test that use the same transaction that APE( arquillian-persistence-extension ), the entity is persist first and the datasets after. So i'm wonder why this happen and the most importatn how can avoid it?
Greets
César
UPDATE-------------------
Here the trace from server
The text was updated successfully, but these errors were encountered: