camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Unable to consume syslog messages
Date Wed, 09 Jan 2013 08:42:55 GMT
On Tue, Jan 8, 2013 at 5:56 PM, sscott <> wrote:
> sscott wrote
>> I set up rsyslogd to forward *.* to localhost:5140.  Every log message
>> causes Camel to output an InvalidPayloadException caused by a
>> NoTypeConversionAvailableException with the detail "No type converter
>> available to convert from type:
>> org.jboss.netty.buffer.BigEndianHeapChannelBuffer to the required type:
>> with value BigEndianHeapChannelBuffer(ridx=0,
>> widx=105, cap=105)"
>> When I change the from() to be "mina:", with or without the sync=false and
>> allowDefaultCodec=false options, and change the maven dependencies to
>> camel-mina from camel-netty, the same exceptions are thrown with the
>> detail "No body available of type: on: Message: [Body
>> is null]. Caused by: No type converter available to convert from type:
>> null to the required type: with value null."
> In case anybody ever has this problem in the future, it was caused by using
> maven-assembly-plugin to package all the code into a jar-with-dependencies.
> I'm assuming it's a TypeConverter / MANIFEST.MF issue.

Thanks for sharing your solution to the problem.

Yeah be careful with the packaginging an uber JAR thingy. The content
in the various files in the META-INF dir need to be merged together,
and not override each other.

> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message