[jbossts-issues] [JBoss JIRA] (JBTM-1293) ATBridgeTest#testSimple counter isn't incremented

Paul Robinson (JIRA) jira-events at lists.jboss.org
Tue Jan 8 03:10:08 EST 2013


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

Paul Robinson edited comment on JBTM-1293 at 1/8/13 3:09 AM:
-------------------------------------------------------------

For now, I've increased the TRANSPORT_TIMEOUT from 30s to 60s which might help.

I've also added some debug output to confirm that it is the TRANSPORT_TIMEOUT that is firing. 

These changes are now merged in. If this issue doesn't happen again before M2, close it as resolved.
                
      was (Author: paul.robinson):
    For now, I've increased the TRANSPORT_TIMEOUT from 30s to 60s which might help.

I've also added some debug output to confirm that it is the TRNASPORT_TIMEOUT that is firing. 
                  
> ATBridgeTest#testSimple counter isn't incremented
> -------------------------------------------------
>
>                 Key: JBTM-1293
>                 URL: https://issues.jboss.org/browse/JBTM-1293
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Testing, TXFramework
>            Reporter: Paul Robinson
>            Assignee: Paul Robinson
>             Fix For: 5.0.0.M2
>
>   Original Estimate: 3 days
>          Time Spent: 6 hours
>  Remaining Estimate: 2 days, 2 hours
>
> See:
> http://172.17.131.2/view/Narayana+BlackTie/job/jbossts-narayana-java7/21/artifact/txframework/target/surefire-reports/org.jboss.narayana.txframework.functional.ATBridgeTest-output.txt
> {code}
>     @Test
>     public void testSimple() throws Exception
>     {
>         ut.begin();
>         client.incrementCounter(1);
>         ut.commit();
>         ut.begin();
>         int counter = client.getCounter();
>         ut.commit();
>         Assert.assertEquals(1, counter);
>     }
> {code}
> Even though the first transaction should have committed an update to the counter, it is still set to zero in the second transaction. 
> This happens intermittently (once so far). It also happened on Beacon which is notorious for test failures caused by things going slowly. I would suspect that the bridged JTA transaction in the first transaction hasn't quite finished the commit when the second transaction is begun.
> If the WS-AT coordinator sends an async commit to the participants and an async committed to the client, then this problem could happen if the client's 'committed' is received before the participant's 'commit' message.
> To verify this we need to check that the coordinator sends an async (@OneWay) commit message to the participant. In which case the simplest solution is to add a 3sec delay between the two transactions. We should also look for other tests that may be affected.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list