[
https://issues.apache.org/activemq/browse/CAMEL-2721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59361#action_59361
]
Claus Ibsen commented on CAMEL-2721:
------------------------------------
I wonder if we should have 2 options for fine grained control
- noReplyLogLevel
- disconnectOnNoReply
Then you can control the logging level, eg WARN by default. And you can turn it
OFF as well.
And then the option option can dictate if the session should be close or not
(as it does now).
> Camel-mina logs a warning if an InOut connection does not send a reply
> ----------------------------------------------------------------------
>
> Key: CAMEL-2721
> URL: https://issues.apache.org/activemq/browse/CAMEL-2721
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-mina
> Affects Versions: 2.2.0
> Reporter: Cott Lang
> Fix For: 2.3.0, 2.4.0
>
>
> I have an application that receives UDP packets and only occasionally replies
> when conditions warrant.
> This works okay, except when I have an empty body on Out, I get this in the
> log:
> {code}
> Cannot write body since its null, closing session: Exchange[Message: [Body is
> null]]
> {code}
> Is there some other way to indicate a response shouldn't be sent? Looking in
> MinaConsumer, nothing jumps out at me. :)
> If not, it seems like this should be DEBUG.
> Thanks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
