org.jboss.as.txn.service.internal.tsr

Class JCAOrderedLastSynchronizationList

java.lang.Object

org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList

All Implemented Interfaces:

Synchronization

public class JCAOrderedLastSynchronizationList
extends Object
implements Synchronization

This class was added to: 1. workaround an issue discussed in https://java.net/jira/browse/JTA_SPEC-4 whereby the JCA Synchronization(s) need to be called after the JPA Synchronization(s). Currently the implementation orders JCA relative to all interposed Synchronizations, if this is not desirable it would be possible to modify this class to store just the JPA and JCA syncs and the other syncs can simply be passed to a delegate (would need the reference to this in the constructor). 2. During afterCompletion the JCA synchronizations should be called last as that allows JCA to detect connection leaks from frameworks that have not closed the JCA managed resources. This is described in (for example) http://docs.oracle.com/javaee/5/api/javax/transaction/TransactionSynchronizationRegistry .html#registerInterposedSynchronization(javax.transaction.Synchronization) where it says that during afterCompletion "Resources can be closed but no transactional work can be performed with them"

Constructor Summary

Constructors

Constructor and Description
JCAOrderedLastSynchronizationList()

Method Summary

Modifier and Type	Method and Description
void	afterCompletion(int status)
void	beforeCompletion() Exceptions from Synchronizations that are registered with this TSR are not trapped for before completion.
void	registerInterposedSynchronization(Synchronization synchronization) This is only allowed at various points of the transaction lifecycle.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

JCAOrderedLastSynchronizationList

public JCAOrderedLastSynchronizationList()

Method Detail

registerInterposedSynchronization

public void registerInterposedSynchronization(Synchronization synchronization)
                                       throws IllegalStateException,
                                              SystemException

This is only allowed at various points of the transaction lifecycle.

Parameters:

synchronization - The synchronization to register

Throws:

IllegalStateException - In case the transaction was in a state that was not valid to register under

SystemException - In case the transaction status was not known

beforeCompletion

public void beforeCompletion()

Exceptions from Synchronizations that are registered with this TSR are not trapped for before completion. This is because an error in a Sync here should result in the transaction rolling back. You can see that in effect in these classes: https://github.com/jbosstm/narayana/blob/5.0.4.Final/ArjunaCore/arjuna/classes /com/arjuna/ats/arjuna/coordinator/TwoPhaseCoordinator.java#L91 https://github.com/jbosstm/narayana/blob/5.0.4.Final/ArjunaJTA /jta/classes/com/arjuna/ats/internal/jta/resources/arjunacore/SynchronizationImple.java#L76

Specified by:

beforeCompletion in interface Synchronization

afterCompletion

public void afterCompletion(int status)

Specified by:

afterCompletion in interface Synchronization