camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Scott (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CAMEL-5951) Camel-syslog dataformat broken with netty transport
Date Wed, 16 Jan 2013 16:04:13 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Steven Scott reopened CAMEL-5951:
---------------------------------


Another copy/paste error - set the message.remoteAddress instead of localAddress from the
NETTY_LOCAL_ADDRESS (at least on 2.10.x branch where I was looking)
                
> 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

Mime
View raw message