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 (Created) (JIRA)" <ji...@apache.org> on 2011/12/20 07:39:30 UTC
[jira] [Created] (CAMEL-4800) camel-jms - Include details about
correlation id in exchange timeout exception if a reply message did not
come back
camel-jms - Include details about correlation id in exchange timeout exception if a reply message did not come back
-------------------------------------------------------------------------------------------------------------------
Key: CAMEL-4800
URL: https://issues.apache.org/jira/browse/CAMEL-4800
Project: Camel
Issue Type: Improvement
Components: camel-jms
Affects Versions: 2.8.3, 2.9.0
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 2.8.4, 2.9.1
This helps make it easier to spot situations when doing request/reply over JMS and the reply message is not received within the timeout period.
And then the reply messages comes later.
Then it should be easier to spot in the logs when the timeout occurred, and the correlation ID should be in the logs, so you can correlate these two situations.
--
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-4800) camel-jms - Include details about
correlation id in exchange timeout exception if a reply message did not
come back
Posted by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4800.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.9.1)
2.10
Also reduced noise in log to not include stacktraces if an unknown correlation id was received in the reply queue.
> camel-jms - Include details about correlation id in exchange timeout exception if a reply message did not come back
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4800
> URL: https://issues.apache.org/jira/browse/CAMEL-4800
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.8.3, 2.9.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.4, 2.10
>
>
> This helps make it easier to spot situations when doing request/reply over JMS and the reply message is not received within the timeout period.
> And then the reply messages comes later.
> Then it should be easier to spot in the logs when the timeout occurred, and the correlation ID should be in the logs, so you can correlate these two situations.
--
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-4800) camel-jms - Include details about
correlation id in exchange timeout exception if a reply message did not
come back
Posted by "Hadrian Zbarcea (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-4800:
-----------------------------------
Affects Version/s: (was: 2.9.0)
Fix Version/s: (was: 2.10)
2.9.0
> camel-jms - Include details about correlation id in exchange timeout exception if a reply message did not come back
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4800
> URL: https://issues.apache.org/jira/browse/CAMEL-4800
> Project: Camel
> Issue Type: Improvement
> Components: camel-jms
> Affects Versions: 2.8.3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.8.4, 2.9.0
>
>
> This helps make it easier to spot situations when doing request/reply over JMS and the reply message is not received within the timeout period.
> And then the reply messages comes later.
> Then it should be easier to spot in the logs when the timeout occurred, and the correlation ID should be in the logs, so you can correlate these two situations.
--
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