0 Replies Latest reply on Jun 6, 2016 3:13 AM by Nicklas Karlsson

    Database seeding (persistence extension) and transactions

    Nicklas Karlsson Master

      (something for bmajsak)?

       

      Using the latest and greatest of Arquillian + extensions on a WF10

       

      If I have a dummy test that just calls a stored procedure (that doesn't touch the data). Fine.

      I add some seeding data, I get a "unable to commit transaction" (more on that later)

      I add the @Transactional(value = TransactionMode.ROLLBACK), works fine again (understandable since the default mode is commit)

       

      So it would appear that seeding the database makes the transaction dirty, is this by design or just not doable in any other way?

       

      Back to *why* I cannot commit: I get a

       

      Caused by: org.jboss.arquillian.test.spi.ArquillianProxyException: javax.transaction.RollbackException : ARJUNA016053: Could not commit transaction.
      [Proxied because : Original exception caused: class java.lang.ClassNotFoundException: org.jboss.jca.core.spi.transaction.local.LocalXAException]
      
      

       

      Which is a bit strange since my test DS is not XA. Pointers?

       

      I also get some

       

      10:08:51,540 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 170) WFLYUT0021: Registered web context: /525248d2-f44a-424c-9bce-c2cb9cdbc8da
      10:08:51,616 INFO  [org.jboss.as.server] (management-handler-thread - 31) WFLYSRV0010: Deployed "525248d2-f44a-424c-9bce-c2cb9cdbc8da.war" (runtime-name : "525248d2-f44a-424c-9bce-c2cb9cdbc8da.war")
      10:08:55,551 ERROR [stderr] (default task-64) Bad Base64 input character at 0: 40(decimal)
      

       

      but I don't think they are related(?)

       

      Thanks in advance,

      Nik