You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/10/09 09:20:02 UTC

[jira] [Created] (CAMEL-5694) camel-jms - Should also allow multiple consumers on queues

Claus Ibsen created CAMEL-5694:
----------------------------------

             Summary: camel-jms - Should also allow multiple consumers on queues
                 Key: CAMEL-5694
                 URL: https://issues.apache.org/jira/browse/CAMEL-5694
             Project: Camel
          Issue Type: Bug
          Components: camel-jms
    Affects Versions: 2.10.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
            Priority: Minor
             Fix For: 2.11.0, 2.10.2


If having 2+ routes that consumes from the same queue, then that should be allowed.

Its a bit unusual though for queues in Camel as you most likely want to use the same route for the same queue. But there is nothing in the JMS spec that forbids this.



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

[jira] [Updated] (CAMEL-5694) camel-jms - Should also allow multiple consumers from multiple routes from the same queue

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5694:
-------------------------------

    Summary: camel-jms - Should also allow multiple consumers from multiple routes from the same queue  (was: camel-jms - Should also allow multiple consumers on queues)
    
> camel-jms - Should also allow multiple consumers from multiple routes from the same queue
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5694
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5694
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.10.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.11.0, 2.10.2
>
>
> If having 2+ routes that consumes from the same queue, then that should be allowed.
> Its a bit unusual though for queues in Camel as you most likely want to use the same route for the same queue. But there is nothing in the JMS spec that forbids this.

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

[jira] [Resolved] (CAMEL-5694) camel-jms - Should also allow multiple consumers from multiple routes from the same queue

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5694.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.9.4
    
> camel-jms - Should also allow multiple consumers from multiple routes from the same queue
> -----------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5694
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5694
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.10.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.4, 2.11.0, 2.10.2
>
>
> If having 2+ routes that consumes from the same queue, then that should be allowed.
> Its a bit unusual though for queues in Camel as you most likely want to use the same route for the same queue. But there is nothing in the JMS spec that forbids this.

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