[jbossts-issues] [JBoss JIRA] (JBTM-1945) Test failed: test_215(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest)

[Tom Jenkinson (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Jenkinson updated JBTM-1945:
--------------------------------

    Description: 
Test failed: test_215(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest)

Intermittent failure seems to have been triggered by: https://github.com/jbosstm/narayana/commit/e0e5d7ab58e377ad6eb43e1737baa716d1c4836e

Nothing obvious in the commit so setting up a repeating job

It seems that calling receive on a JMS session while the connection is stopped, then in a different thread call start a few seconds later means that hornetq may not restart delivery of messages. If you have a timed receive at the end of the wait period the message is available for delivery.

I will raise a HQ issue but for ourselves I am changing the algorithm so that we do not call connection.start after the receive.

  was:
Intermittent failure seems to have been triggered by: https://github.com/jbosstm/narayana/commit/e0e5d7ab58e377ad6eb43e1737baa716d1c4836e

Nothing obvious in the commit so setting up a repeating job


    
> Test failed: test_215(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest)
> ---------------------------------------------------------------------------
>
>                 Key: JBTM-1945
>                 URL: https://issues.jboss.org/browse/JBTM-1945
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: BlackTie
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 5.0.0.M5
>
>
> Test failed: test_215(org.jboss.narayana.blacktie.jatmibroker.xatmi.CSTest)
> Intermittent failure seems to have been triggered by: https://github.com/jbosstm/narayana/commit/e0e5d7ab58e377ad6eb43e1737baa716d1c4836e
> Nothing obvious in the commit so setting up a repeating job
> It seems that calling receive on a JMS session while the connection is stopped, then in a different thread call start a few seconds later means that hornetq may not restart delivery of messages. If you have a timed receive at the end of the wait period the message is available for delivery.
> I will raise a HQ issue but for ourselves I am changing the algorithm so that we do not call connection.start after the receive.

--
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