camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5951) Camel-syslog dataformat broken with netty transport
Date Sat, 19 Jan 2013 06:42:17 GMT


Willem Jiang commented on CAMEL-5951:

Hi Steven,

It's my bad, I didn't update the code after I copy past it.
I just commit a quick fix for it, please feel free to check out the code and verify it.

> Camel-syslog dataformat broken with netty transport
> ---------------------------------------------------
>                 Key: CAMEL-5951
>                 URL:
>             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
> (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:

View raw message