camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-3566) camel-jms - Add option logWarnWhenReplyToIsDiscarded to disable WARN log if JMSReplyTo is being discarded
Date Thu, 20 Jan 2011 15:19:43 GMT

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

Hadrian Zbarcea commented on CAMEL-3566:
----------------------------------------

The MEP of the route is totally irrelevant for a particular processor on the route (it is
relevant to the from consumer).
If replyTo is set on a JMS endpoint, that would be an InOut exchange and it's most likely
by intent. I agree that logging at WARN is a sure way to make camel look lousy. 

My proposal is to log at INFO, not add config.

> camel-jms - Add option logWarnWhenReplyToIsDiscarded to disable WARN log if JMSReplyTo
is being discarded
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3566
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3566
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jms
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.6.0
>
>
> If you dont care about an InOnly MEP exchange which uses an jms endpoint that has a replyTo
set, then it woud log that at WARN that the reply to is being discarded. This happens at WARN
level. Some people may just want to ignore this, and thus we need a {{logWarnWhenReplyToIsDiscarded}}
option they can set to false.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message