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/07/16 08:04:35 UTC
[jira] [Created] (CAMEL-5444) camel-jms - Log at INFO level if
shared replyTo queues are in use, as they are not as fast as temporary or
exclusive queues
Claus Ibsen created CAMEL-5444:
----------------------------------
Summary: camel-jms - Log at INFO level if shared replyTo queues are in use, as they are not as fast as temporary or exclusive queues
Key: CAMEL-5444
URL: https://issues.apache.org/jira/browse/CAMEL-5444
Project: Camel
Issue Type: Improvement
Components: camel-jms
Affects Versions: 2.10.0
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.11.0
See nabble
http://camel.465427.n5.nabble.com/fyi-SI-tp5716049.html
We should log at INFO (maybe even WARN level) if shared reply queues are in use as they are not as fast. They have their purposes though, such as a shared clustered queue, or if a queue is used by other apps too (not ideally thought).
Temporary and Exclusive reply queues are faster.
See the JMS docs at the _request reply_ section, for much more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-5444) camel-jms - Log at INFO level if
shared replyTo queues are in use, as they are not as fast as temporary or
exclusive queues
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5444:
-------------------------------
Affects Version/s: 2.9.2
Fix Version/s: 2.10.1
2.9.3
> camel-jms - Log at INFO level if shared replyTo queues are in use, as they are not as fast as temporary or exclusive queues
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5444
> URL: https://issues.apache.org/jira/browse/CAMEL-5444
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.9.2, 2.10.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/fyi-SI-tp5716049.html
> We should log at INFO (maybe even WARN level) if shared reply queues are in use as they are not as fast. They have their purposes though, such as a shared clustered queue, or if a queue is used by other apps too (not ideally thought).
> Temporary and Exclusive reply queues are faster.
> See the JMS docs at the _request reply_ section, for much more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-5444) camel-jms - Log at INFO level if
shared replyTo queues are in use, as they are not as fast as temporary or
exclusive queues
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-5444.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Updated JMS doc as well with a table having a summary etc.
> camel-jms - Log at INFO level if shared replyTo queues are in use, as they are not as fast as temporary or exclusive queues
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5444
> URL: https://issues.apache.org/jira/browse/CAMEL-5444
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.9.2, 2.10.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/fyi-SI-tp5716049.html
> We should log at INFO (maybe even WARN level) if shared reply queues are in use as they are not as fast. They have their purposes though, such as a shared clustered queue, or if a queue is used by other apps too (not ideally thought).
> Temporary and Exclusive reply queues are faster.
> See the JMS docs at the _request reply_ section, for much more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-5444) camel-jms - Log at INFO level if
shared replyTo queues are in use, as they are not as fast as temporary or
exclusive queues
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-5444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13414874#comment-13414874 ]
Claus Ibsen commented on CAMEL-5444:
------------------------------------
Now there is a WARN log, when Camel/route is starting:
2012-07-16 08:24:41,711 [main ] WARN PersistentQueueReplyManager - Endpoint[activemq://queue:foo?replyTo=bar&replyToType=Shared] is using a shared reply queue, which is not as fast as alternatives. See more detail at the section 'Request-reply over JMS' at http://camel.apache.org/jms
> camel-jms - Log at INFO level if shared replyTo queues are in use, as they are not as fast as temporary or exclusive queues
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-5444
> URL: https://issues.apache.org/jira/browse/CAMEL-5444
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.9.2, 2.10.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/fyi-SI-tp5716049.html
> We should log at INFO (maybe even WARN level) if shared reply queues are in use as they are not as fast. They have their purposes though, such as a shared clustered queue, or if a queue is used by other apps too (not ideally thought).
> Temporary and Exclusive reply queues are faster.
> See the JMS docs at the _request reply_ section, for much more details.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira