Skip to content

Instantly share code, notes, and snippets.

16:08:13,151 INFO [org.jboss.as.jpa] (default task-1) tx.status = 0
16:08:13,155 WARN [com.arjuna.ats.arjuna] (Transaction Reaper Worker 0) ARJUNA012121: TransactionReaper::doCancellations worker Thread[Transaction Reaper Worker 0,5,main] successfully canceled TX 0:ffff7f000001:499dacbf:53ebc566:10
16:08:13,151 ERROR [org.jboss.as.ejb3] (default task-1) WFLYEJB0458: Failure in caller transaction.: java.lang.IllegalStateException: No transaction is running
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getTransactionImple(TransactionSynchronizationRegistryImple.java:228)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionSynchronizationRegistryImple.getResource(TransactionSynchronizationRegistryImple.java:125)
at org.jboss.as.jpa.transaction.TransactionUtil.getEntityManagerInTransactionRegistry(TransactionUtil.java:129) [wildfly-jpa-9.0.0.Alpha1-SNAPSHOT.jar:9.0.0.Alpha1-SNAPSHOT]
at org.jboss.as.jpa.transaction.Tran
@scottmarlow
scottmarlow / gist:0151c9ac776f090e3f43
Created August 19, 2014 19:12
tx timeout with servlet + ut
2014-08-19 15:05:38,511 TRACE [org.jboss.as.jpa] (MSC service thread 1-4) install persistence unit definitions for war TxTimeoutTestCase.war
2014-08-19 15:05:38,511 TRACE [org.jboss.as.jpa] (MSC service thread 1-4) adding 'vfs:/content/TxTimeoutTestCase.war/WEB-INF/classes/' to annotation index map
2014-08-19 15:05:38,512 TRACE [org.jboss.as.jpa] (MSC service thread 1-4) returning global (module) Persistence Provider org.hibernate.jpa.HibernatePersistenceProvider
2014-08-19 15:05:38,512 TRACE [org.jboss.as.jpa] (MSC service thread 1-4) returning global (module) Persistence Provider org.hibernate.ejb.HibernatePersistence
2014-08-19 15:05:38,513 TRACE [org.jboss.as.jpa] (MSC service thread 1-4) added PersistenceUnitService (phase 2 of 2) for 'service jboss.persistenceunit."TxTimeoutTestCase.war#mypc"'. PU is ready for injector action.
2014-08-19 15:05:38,520 INFO [org.jboss.as.arquillian] (MSC service thread 1-2) Arquillian deployment detected: ArquillianConfig[service=jboss.arquillian.config."TxTimeoutTestCa
@scottmarlow
scottmarlow / gist:aeefc5505ffa953f5688
Created August 19, 2014 19:41
tx timeout with servlet + ut (trace logging also set for TM)
2014-08-19 15:36:55,735 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "TxTimeoutTestCase.war" (runtime-name : "TxTimeoutTestCase.war")
2014-08-19 15:36:55,965 TRACE [com.arjuna.ats.jta] (default task-1) BaseTransaction.begin
2014-08-19 15:36:55,965 TRACE [com.arjuna.ats.arjuna] (default task-1) StateManager::StateManager( 2, 0 )
2014-08-19 15:36:55,966 TRACE [com.arjuna.ats.arjuna] (default task-1) BasicAction::BasicAction()
2014-08-19 15:36:55,966 TRACE [com.arjuna.ats.arjuna] (default task-1) BasicAction::Begin() for action-id 0:ffff7f000001:70db886:53f3a72e:e
2014-08-19 15:36:55,967 TRACE [com.arjuna.ats.arjuna] (default task-1) BasicAction::actionInitialise() for action-id 0:ffff7f000001:70db886:53f3a72e:e
2014-08-19 15:36:55,968 TRACE [com.arjuna.ats.arjuna] (default task-1) ActionHierarchy::ActionHierarchy(1)
2014-08-19 15:36:55,968 TRACE [com.arjuna.ats.arjuna] (default task-1) ActionHierarchy::add(0:ffff7f000001:70db886:53f3a72e:e, 1)
2014-08-19 15:36:55,972 TRACE [
@scottmarlow
scottmarlow / gist:b7fe320f5a2ea7969170
Created August 22, 2014 13:18
tx scoped pc with ORM "Skipping JTA sync registration due to auto join checking"
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.jta] (Thread-8 (HornetQ-client-global-threads-411174393)) BaseTransaction.begin^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads-411174393)) StateManager::StateManager( 2, 0 )^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads-411174393)) BasicAction::BasicAction()^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads-411174393)) BasicAction::Begin() for action-id 0:ffffc0a8022e:-64f4f7ab:53f45bf2:9ef4^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads-411174393)) BasicAction::actionInitialise() for action-id 0:ffffc0a8022e:-64f4f7ab:53f45bf2:9ef4^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads-411174393)) ActionHierarchy::ActionHierarchy(1)^M
2014-08-20 08:35:08,694 TRACE [com.arjuna.ats.arjuna] (Thread-8 (HornetQ-client-global-threads
@scottmarlow
scottmarlow / gist:db59c4de54a9c546001f
Created September 18, 2014 01:40
jenkins-cli.jar + Bogus chunk size
java -jar /home/smarlow/jenkins/jenkins-cli.jar -s http://jenkins.mw.lab.eng.bos.redhat.com/hudson/ -i /home/smarlow/.ssh/id_rsa_nocrypt.key get-job tck7-wildfly-integration
Exception in thread "main" java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at hudson.cli.CLI.connectViaCliPort(CLI.java:211)
at hudson.cli.CLI.<init>(CLI.java:134)
15:20:50,800 FATAL [org.jboss.wfink.ejb30.SFTestBean] (EJB default - 1) CONSTRUCT
15:20:51,029 WARN [com.arjuna.ats.jta] (EJB default - 2) ARJUNA016073: Current transaction is not an AtomicAction!
15:20:51,064 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 2) WFLYEJB0034: EJB Invocation failed on component SFTestBean for method public abstract void org.jboss.wfink.ejb30.SFTest.createKeyValue(java.lang.String,java.lang.String): javax.ejb.EJBException: javax.persistence.TransactionRequiredException: WFLYJPA0060: Transaction is required to perform this operation (either use a transaction or extended persistence context)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191) [wildfly-ejb3-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276) [wildfly-ejb3-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.jav
15:32:57,817 FATAL [org.jboss.wfink.ejb30.SLTestBean] (EJB default - 1) CONSTRUCT
15:32:57,852 WARN [com.arjuna.ats.jta] (EJB default - 1) ARJUNA016073: Current transaction is not an AtomicAction!
15:32:57,858 ERROR [org.jboss.as.ejb3.invocation] (EJB default - 1) WFLYEJB0034: EJB Invocation failed on component SLTestBean for method public abstract void org.jboss.wfink.ejb30.SLTest.createKeyValue(java.lang.String,java.lang.String): javax.ejb.EJBException: javax.persistence.TransactionRequiredException: WFLYJPA0060: Transaction is required to perform this operation (either use a transaction or extended persistence context)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:191) [wildfly-ejb3-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:276) [wildfly-ejb3-9.0.0.Alpha2-SNAPSHOT.jar:9.0.0.Alpha2-SNAPSHOT]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.jav
@scottmarlow
scottmarlow / 7.9.2 Provider Responsibilities
Created November 12, 2014 14:49
JPA 2.1 spec section on 7.9.2 Provider Responsibilities
7.9.2 Provider Responsibilities
The Provider has no knowledge of the distinction between transaction-scoped and extended persistence
contexts. It provides entity managers to the container when requested and registers for transaction synchronization notifications.
* When EntityManagerFactory.createEntityManager is invoked, the provider must create and return a new entity manager. If a JTA transaction is active and the persistence context is of type SynchronizationType.SYNCHRONIZED, the provider must register for synchronization notifications against the JTA transaction.
* When EntityManager.joinTransaction is invoked, the provider must register for synchronization notifications against the current JTA transaction if a previous joinTransaction invocation for the transaction has not already been processed.
* When the JTA transaction commits, if the persistence context is of type SynchronizationType.SYNCHRONIZED or has otherwise been joined to the transaction, the provider must flush all modified entity stat
@scottmarlow
scottmarlow / 7.9.1 Container Responsibilities
Created November 12, 2014 15:09
EE JPA container responsibilities
7.9.1 Container Responsibilities
For the management of a transaction-scoped persistence context, if there is no EntityManager already associated with the JTA transaction:
* The container creates a new entity manager by calling EntityManagerFactory.createEntityManager when the first invocation of an entity manager with PersistenceContextType.TRANSACTION occurs within the scope of a business method executing in the JTA transaction.
* After the JTA transaction has completed (either by transaction commit or rollback), the container closes the entity manager by calling EntityManager.close. [86] Note that the JTA transaction may rollback in a background thread (e.g., as a result of transaction timeout), in which case the container should arrange for the entity manager to be closed but the EntityManager.close method should not be concurrently invoked while the application is in an EntityManager invocation.
The container must throw the TransactionRequiredException if a transaction-scoped persistence context is
EE.5.10 TransactionSynchronizationRegistry References
The JTA TransactionSynchronizationRegistry interface may be used by system level components such as persistence managers that may be packaged with EJB or web application components. Such components can find an appropriate object implementing the TransactionSynchronizationRegistry interface by looking up the JNDI name java:comp/TransactionSynchronizationRegistry or by requesting injection of a TransactionSynchronizationRegistry object using the Resource annotation. The authenticationType and shareable elements of the Resource annotation must not be specified. The container is only required to provide the java:comp/TransactionSynchronizationRegistry name, or inject a TransactionSynchronizationRegistry object, for those components that can validly make use of it. Any such reference to a TransactionSynchronizationRegistry object is only valid within the component instance that performed the lookup. See the individual component definitions for further informat