You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2013/01/11 01:18:13 UTC

[jira] [Assigned] (CAMEL-5951) Camel-syslog dataformat broken with netty transport

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

Willem Jiang reassigned CAMEL-5951:
-----------------------------------

    Assignee: Willem Jiang
    
> 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
>   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