Databases
StackOverflow2013
Postsdbo
POTestNG multithreaded test with Spring @Transactional
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTestNG multithreaded test with Spring @Transactional
    primarykey
    data
    text
    <p>I am using TestNG to test persistence Spring modules (JPA+Hibernate) using AbstractTransactionalTestNGSpringContextTests as a base class. All important parts @Autowired, @TransactionConfiguration, @Transactional work just fine.</p> <p>The problem comes when I am trying to run test in parallel threads with threadPoolSize=x, invocationCount=y TestNG annotation.</p> <pre><code>WARNING: Caught exception while allowing TestExecutionListener [org.springframework.test.context.transaction.TransactionalTestExecutionListener@174202a] to process 'before' execution of test method [testCreate()] for test instance [DaoTest] java.lang.IllegalStateException: Cannot start new transaction without ending existing transaction: Invoke endTransaction() before startNewTransaction(). at org.springframework.test.context.transaction.TransactionalTestExecutionListener.beforeTestMethod(TransactionalTestExecutionListener.java:123) at org.springframework.test.context.TestContextManager.beforeTestMethod(TestContextManager.java:374) at org.springframework.test.context.testng.AbstractTestNGSpringContextTests.springTestContextBeforeTestMethod(AbstractTestNGSpringContextTests.java:146) </code></pre> <p>... Has anybody faced this problem?</p> <p>Here is the code:</p> <pre><code>@TransactionConfiguration(defaultRollback = false) @ContextConfiguration(locations = { "/META-INF/app.xml" }) public class DaoTest extends AbstractTransactionalTestNGSpringContextTests { @Autowired private DaoMgr dm; @Test(threadPoolSize=5, invocationCount=10) public void testCreate() { ... dao.persist(o); ... } ... </code></pre> <p><strong>Update:</strong> It seems that AbstractTransactionalTestNGSpringContextTests maintains transaction only for main thread when all other test threads don't get their own transaction instance. The only way to solve that is to extend AbstractTestNGSpringContextTests and maintain transaction programmatically (instead of @Transactional annotation) per each method (i.e. with TransactionTemplate):</p> <pre><code>@Test(threadPoolSize=5, invocationCount=10) public void testMethod() { new TransactionTemplate(txManager).execute(new TransactionCallbackWithoutResult() { @Override protected void doInTransactionWithoutResult(TransactionStatus status) { // transactional test logic goes here } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USGennady Shumakher
    1. USGennady Shumakher
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTestNG multithreaded test with Spring @Transactional
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTestNG multithreaded test with Spring @Transactional
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POTestNG multithreaded test with Spring @Transactional
      1. This table or related slice is empty.
      1. VTUpMod
    1. COfor the sake of curiosity - try defining your `DaoMgr` in prototype scope and see if the result is the same
      singulars
      1. POTestNG multithreaded test with Spring @Transactional
      1. USBozho
    2. COannotating DaoMgr has no effect. But AbstractTransactionalTestNGSpringContextTests is annotated with @Transactional, so all test methods start transaction before daoMgr is accessed.
      singulars
      1. POTestNG multithreaded test with Spring @Transactional
      1. USGennady Shumakher
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload