How'd you get around this issue:
https://issues.apache.org/jira/browse/CAMEL-3607 ??
By default it looks like netty uses receiveBuffer size of 768, I can't
figure out how to configure the netty component to allow 1024 (which of
course syslog should handle).
I see this in the logs
Body:BigEndi
Hi Guys,
Whats the plan to get onto Spring 3.1?
I'm a heavy Grails user and Camel routing is core to every app my company
develops on Grails.
The near pending release of Grails 2.0 (which embeds Spring 3.1) is tracking
the Spring 3.1 release schedule
(http://jira.grails.org/secure/ReleaseNote.
Sounds good to me. I'm just above novice when it comes to Camel, but I've
got some cycles, how do you want to proceed?
--
View this message in context:
http://camel.465427.n5.nabble.com/syslog-RFC-5424-dataformat-component-tp5015386p5039198.html
Sent from the Camel Development mailing list arch
How would you like to proceed?
It'd also be nice to handle the structured data un/marshal with a map or
something. Perhaps a property on the SyslogMessage object?
--
View this message in context:
http://camel.465427.n5.nabble.com/syslog-RFC-5424-dataformat-component-tp5015386p5018448.html
Sen
The spec does not say anything about backwards compatibility, but I believe
much of the syslog code in the existing component is reusable.
ASSUMPTIONS: we handle TLS / SSL etc with the netty / mina layer. SYSLOG4J
is being used right now, but likely optional. Writing and parsing RFC5424 is
not t
The current syslog is using an outdated RFC 3164. Since, I'm in need of a
syslog RFC 5424 component I've created one that current wraps syslog4j for
the marshalling, the rest I can pretty much copy and extend the existing
syslog implementation.
Questions
1) I'm open to contributing this, do you
