[
https://issues.apache.org/jira/browse/OPENEJB-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Obarymski updated OPENEJB-2127:
-------------------------------------
Description:
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 and the message is sent to a destination
If the app under test listenes on a JMS topic then the message is effectively
lost (the app under test 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.
was:
Hi,
W use OpenEJB for integration testing (with use of the ApplicationComposer
JUnit runner).
We've observed that sometimes JMS consumers are registered after test is
started and the message is sent to destination
If the test case involves JMS topic then the message is effectively lost and
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.
> 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 and the message is sent to a destination
> If the app under test listenes on a JMS topic then the message is effectively
> lost (the app under test 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)
