Willem Jiang created CAMEL-8576:
-----------------------------------

             Summary: Added a option to let camel netty take the message body 
as byte buffer
                 Key: CAMEL-8576
                 URL: https://issues.apache.org/jira/browse/CAMEL-8576
             Project: Camel
          Issue Type: Improvement
          Components: el-netty camel-netty4
            Reporter: Willem Jiang
            Assignee: Willem Jiang
             Fix For: 2.16.0


When using the camel-netty to send the syslog server we need to convert the 
message body into ChannelBuffer otherwise we will get complain from Netty just 
like this.
{code}
[org.jboss.netty.channel.socket.nio.AbstractNioSelector] Unexpected exception 
in the selector loop.
java.lang.IllegalArgumentException: unsupported message type: class [B
        at 
org.jboss.netty.channel.socket.nio.SocketSendBufferPool.acquire(SocketSendBufferPool.java:52)
        at 
org.jboss.netty.channel.socket.nio.NioDatagramWorker.write0(NioDatagramWorker.java:260)
        at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:151)
        at 
org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:335)
        at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:372)
        at 
org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:296)
        at 
org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:89)
        at 
org.jboss.netty.channel.socket.nio.NioDatagramWorker.run(NioDatagramWorker.java:343)
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)[:1.7.0_71]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.7.0_71]
        at java.lang.Thread.run(Thread.java:745)[:1.7.0_71]
{code}
It could be handy if we just have a option in the netty endpoint for it.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to