[jboss-jira] [JBoss JIRA] (WFLY-10201) There are in doubt transactions that should be rolled back after communication failure

[Flavia Rainone (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557625#comment-13557625 ] 

Flavia Rainone commented on WFLY-10201:
---------------------------------------

I'm adding a dependency on the WFLY-10174. If wildfly-transaction-client 1.0.3.Final comes before 1.1.0.Final, this will require an update.

> There are in doubt transactions that should be rolled back after communication failure
> --------------------------------------------------------------------------------------
>
>                 Key: WFLY-10201
>                 URL: https://issues.jboss.org/browse/WFLY-10201
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: Flavia Rainone
>            Assignee: Flavia Rainone
>
> We have two servers, one deployment on each.
> TX impl: jta
> there is remote outbound connection on the EAP 1 for EJB call from EAP1 to EAP2
> outbound connection points to socket proxy which is managable (communication can be stopped) and forward communication to EAP2 (location that should be used in remote outbound connection without socket proxy)
> Scenario:
>     call servlet on EAP 1 which trigger EJB on the EAP 1
>     EJB enlists dummy xa resource and writes to DB
>     EJB call EJB on the EAP 2 via remote outbound connection
>     EJB on the server 2 enlists dummy xa resource and writes to DB and return
>     at the exit of the prepare phase in dummy xa resource on EAP 2 communication (socket proxy) is killed
>     Transaction is supposed to be rolled back.
> However, we can see that there are prepared resources on the EAP 2 that have not been rolled back
> [INFO] Transaction
> 		Xid:< formatId=131077, gtrid_length=29, bqual_length=37, tx_uid=0:ffff0a280499:6a6c4aa6:59885e66:12, node_name=0, branch_uid=0:ffff0a280499:6a6c4aa6:59885e66:27, subordinatenodename=1, eis_name=0 > 
> 		Type:StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction/SubordinateAtomicAction/JCA 
> 		ParentNodeName:0 
> 		Participant:false 
> 		CreationTime:Mon, 07 Aug 2017 14:35:11 +0200 
> 		AgeInSeconds:128 
> 		Id:0:ffff0a280499:-166fadbf:59885e75:10 
> 		Participant
> 			HeuristicValue:-1 
> 			Status:PREPARED 
> 			JndiName:java:/TestXAResource 
> 			GlobalTransactionId:[B at 4e1b1193 
> 			HeuristicStatus:UNKNOWN 
> 			NodeName:null 
> 			Timeout:0 
> 			FormatId:-1 
> 			BranchQualifier:[B at 39a95e4c 
> 			Type:/StateManager/AbstractRecord/XAResourceRecord 
> 			Participant:true 
> 			EisProductVersion:EAP Test 
> 			ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord 
> 			EisProductName:Crash Recovery Test 
> 			Id:0:ffff0a280499:-166fadbf:59885e75:1a 
> 		Participant
> 			HeuristicValue:-1 
> 			Status:PREPARED 
> 			JndiName:java:jboss/eap2-ds-jndi 
> 			GlobalTransactionId:[B at 5c4ce097 
> 			HeuristicStatus:UNKNOWN 
> 			NodeName:null 
> 			Timeout:0 
> 			FormatId:-1 
> 			BranchQualifier:[B at 6945cfc7 
> 			Type:/StateManager/AbstractRecord/XAResourceRecord 
> 			Participant:true 
> 			EisProductVersion:9.3.15 
> 			ClassName:com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord 
> 			EisProductName:PostgreSQL 
> 			Id:0:ffff0a280499:-166fadbf:59885e75:22 
> [INFO] ..........................................................................................
> There is no evidence (eap1.server.log) that periodic recovery process is looking for in doubt transactions on the other server that could be rolled back.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)