[
https://issues.apache.org/jira/browse/CAMEL-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557328#comment-13557328
]
Steven Scott edited comment on CAMEL-5951 at 1/18/13 4:36 PM:
--------------------------------------------------------------
Sorry, I didn't know CamelNettyLocalAddress got added - I was looking at
2.10.2, not the latest code
the
"message.setRemoteAddress(exchange.getIn().getHeader("CamelNettyLocalAddress",
String.class));" typo still applies though
thanks!
was (Author: codingismy11to7):
Sorry, I didn't know CamelNettyLocalAddress - I was looking at 2.10.2, not
the latest code
the
"message.setRemoteAddress(exchange.getIn().getHeader("CamelNettyLocalAddress",
String.class));" typo still applies though
thanks!
> Camel-syslog dataformat broken with netty transport
> ---------------------------------------------------
>
> Key: CAMEL-5951
> URL: https://issues.apache.org/jira/browse/CAMEL-5951
> Project: Camel
> Issue Type: Bug
> Affects Versions: 2.10.2, 2.10.3
> Reporter: Steven Scott
> Assignee: Willem Jiang
> Fix For: 2.9.6, 2.10.4, 2.11.0
>
> Original Estimate: 5m
> Remaining Estimate: 5m
>
> in Rfc3164SyslogDataFormat, the remoteAddress of the SyslogMessage is set
> from the Mina or Netty headers. There's a copy/paste error for Netty: it
> correctly checks for the existence of the CamelNettyRemoteAddress header, but
> then attempts to set the remoteAddress from a CamelMinaRemoteAddress header.
> (there's no camel-syslog component in JIRA)
--
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
