[
https://issues.apache.org/activemq/browse/SM-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reopened SM-628:
--------------------------------
FYI, we tend to resolve issue when the patches are actually committed (but
maybe we should change that, as we don't make much differences between resolved
and closed: how do you usually use these two states ?)
Wrt to your patch, the idea is good. However, this job should be handled by
the MessageList.
For example, when calling:
receiver.getMessageList().assertMessagesReceived(NUM_MESSAGES);
the assertMessagesReceived calls waitForMessagesToArrive which already waits
for the number of message to arrive. if extending the timeout is sufficient,
maybe we should just change the default timeout in the MessageList from 4000 ms
to much more.
Wdyt ?
> org.apache.servicemix.jbi.nmr.flow.jms.JMSFlowTest
> --------------------------------------------------
>
> Key: SM-628
> URL: https://issues.apache.org/activemq/browse/SM-628
> Project: ServiceMix
> Issue Type: Sub-task
> Components: servicemix-core
> Affects Versions: 3.0
> Reporter: Fritz Oconer
> Fix For: 3.2
>
> Attachments: SMTestCasesPatches.zip
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
