Switchyard Netty TCP binding - Automatic Serialization of returned Object doesn't work

[vkasala]

Hello,

I am trying to write simple app, which has TCP biding. Signature of method is:

OrderAck processTwoWay(SimpleOrder order);

TCP biding is set to sync=true - to indicate Request - Response, allowDefaultCodec=false and all other config is set to default as Switchyard editor set. OrderAck implements serializable.

My problem is that when this object is returned following error occurs:

12:31:53,415 WARN  [org.apache.camel.component.netty.NettyConsumer] (New I/O worker #289) Caused by: [org.apache.camel.CamelExchangeException - Cannot write response to /127.0.0.1:58123. Exchange[Message: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<orderAck accepted="false" xmlns="urn:jboss-soa:order-service:1.0">

    <simpleOrder id="1">

        <items>

            <item sku="2">

                <count>3</count>

                <pricePerUnit>4.0</pricePerUnit>

            </item>

        </items>

        <name>processTwoWay</name>

        <quantity>1</quantity>

    </simpleOrder>

</orderAck>

]. Caused by: [java.lang.IllegalArgumentException - unsupported message type: class org.jboss.soa.qa.shared.data.OrderAck]]: org.apache.camel.CamelExchangeException: Cannot write response to /127.0.0.1:58123. Exchange[Message: <?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<orderAck accepted="false" xmlns="urn:jboss-soa:order-service:1.0">

    <simpleOrder id="1">

        <items>

            <item sku="2">

                <count>3</count>

                <pricePerUnit>4.0</pricePerUnit>

            </item>

        </items>

        <name>processTwoWay</name>

        <quantity>1</quantity>

    </simpleOrder>

</orderAck>

]. Caused by: [java.lang.IllegalArgumentException - unsupported message type: class org.jboss.soa.qa.shared.data.OrderAck]

    at org.apache.camel.component.netty.handlers.ServerResponseFutureListener.operationComplete(ServerResponseFutureListener.java:53) [camel-netty-2.10.0.redhat-60024.jar:2.10.0.redhat-60024]

    at org.jboss.netty.channel.DefaultChannelFuture.notifyListener(DefaultChannelFuture.java:427)

    at org.jboss.netty.channel.DefaultChannelFuture.notifyListeners(DefaultChannelFuture.java:413)

    at org.jboss.netty.channel.DefaultChannelFuture.setFailure(DefaultChannelFuture.java:380)

    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.write0(AbstractNioWorker.java:249)

    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.writeFromTaskLoop(AbstractNioWorker.java:152)

    at org.jboss.netty.channel.socket.nio.AbstractNioChannel$WriteTask.run(AbstractNioChannel.java:335)

    at org.jboss.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:366)

    at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:290)

    at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90)

    at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178)

    at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)

    at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)

    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

    at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

Could somebody provide simple example of how to set correct the object serialization? Thank you.

Viliam Kasala

[vkasala]

Hello,

so I've been researching for a while in the topic of Netty and Switchyard Netty TCP Binding. I had problem with communication of my client with Composite service ( TCP binding ). The problem was caused because I set allowDefaultCodec=false and left parameters encoder, decoder empty. You have to specify some coders/encoders.

First of all, here (Example for adding TCP (Netty) encoder/decoders (registry?)) is simple example of using predefined coders(encoders/decoders), which must be registered in Netty TCP Binding properties. With String encoders and decoders you can use own client, which will send string data into SW Netty TCP binding and Switchyard automatically transforms object. Also when you are using IN-OUT (parameter sync=true) communication model, you have to return object of type String. Otherwise previously mentioned error will be also thrown.

Secondly, when you are using Composite reference TCP Netty binding, which refers on Composite Service Netty TCP binding, you can set paramater allowDefaultCodec=true and everything will work well. Or you can set Object encoder and decoder on both endpoints.

See ya!

[vkasala]

And I have also another question:

Is it possible to use automatic serialization of IN-OUT parameters without using some Netty client (e.g. class Socket) ?

Thanks a lot!

[kcbabo]

When you say "automatic serialization", do you mean setting allowDefaltCode=true?  If so, then I believe that will only work with Netty clients:

ObjectEncoder (The Netty Project API Reference (3.2.6.Final))

If you implement a custom encoder/decoder, then the client can send whatever they want without any knowledge of Netty.

[kcbabo]

When you say "automatic serialization", do you mean setting allowDefaltCode=true?  If so, then I believe that will only work with Netty clients:

ObjectEncoder (The Netty Project API Reference (3.2.6.Final))

If you implement a custom encoder/decoder, then the client can send whatever they want without any knowledge of Netty.

[vkasala]

When I said "automatic serialization", I meant allowDefaultCode=false. I misread the default documentation for Netty Camel. Now I understand.

Is also Netty TCP Binding Endpoint capable of automatic serialization of thrown exception? e.g. OrderAck processTwoWay(SimpleOrder order) throw OrderException?

Thank you.