You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2016/04/08 17:08:25 UTC

[jira] [Commented] (OPENEJB-2127) Jms consumers registered after test is started

    [ https://issues.apache.org/jira/browse/OPENEJB-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15232307#comment-15232307 ] 

Romain Manni-Bucau commented on OPENEJB-2127:
---------------------------------------------

Hi Jacek,

1. which version does it affects? Normally MDBs are started before tests start since several releases.
2. do you have a test case on a public repository (github/bitbucket/...) reproducing it?

Thanks,
Romain

> Jms consumers registered after test is started
> ----------------------------------------------
>
>                 Key: OPENEJB-2127
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-2127
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: tests
>            Reporter: Jacek Obarymski
>
> Hi,
> W use OpenEJB for integration testing (with use of the ApplicationComposer JUnit runner).
> We've observed that sometimes JMS consumers are registered after the test is started. 
> If the app under test, listens on a JMS topic, then the message is effectively lost (the app never receives it) and the test fails. This happens occasionally on slower machines.
> This is because the test is started before the app is fully deployed with all JMS consumers registered.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)