[jira] [Commented] (CAMEL-5510) Competing Consumers fails for jms queue using AdviceWith

["Christian Posta (JIRA)" <ji...@apache.org>]

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

Christian Posta commented on CAMEL-5510:
----------------------------------------

I can confirm these tests pass on master.

I think we should close this and reopen if reporter can reproduce on latest snapshots.
                
> Competing Consumers fails for jms queue using AdviceWith
> --------------------------------------------------------
>
>                 Key: CAMEL-5510
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5510
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-test
>    Affects Versions: 2.9.2
>         Environment: Windows7 x64 Juno Eclipse
>            Reporter: William McDonald
>            Assignee: Claus Ibsen
>            Priority: Minor
>         Attachments: CompetingConsumersBase.java, CompetingConsumersDoesNotWork.java, CompetingConsumersWorks.java
>
>
> I was trying to test two routes that start from the same endpoint.  The endpoint is a jms queue, so it should be able to have multiple consumers attach to it.  When I use the standard CamelTestSupport methodology and let it create and start my context, mock my out points, etc. everything passes (see CompetingConsumersWorks.java).  However when I try and use the strategy of not letting the junit support create everything, ie. 
>         public boolean isUseRouteBuilder() { return false; } 
>         public boolean isUseAdviceWith() { return true; } 
> and try and use AdviceWithRouteBuilder to mock out routes the test doesn't pass (see CompetingConsumersDoesNotWork.java).  I can actually get it to work, but only if I start the context before adding the second set of routes to the context (see comments in code).   

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