[Qc]2016-06-28 23:11:13,517 WARN [New I/O worker #2] Com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode (77) | [Dubbo] Decode RPC Invocation failed:null, Dubbo version:2.8.4, current host:127.0.0.1
Java.io.EOFException
At Java.io.DataInputStream.readFully (datainputstream.java:197)
At Java.io.DataInputStream.readUTF (datainputstream.java:609)
At Java.io.DataInputStream.readUTF (datainputstream.java:564)
At Com.alibaba.dubbo.common.serialize.support.fst.FstObjectInput.readUTF (fstobjectinput.java:78)
At Com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode (decodeablerpcinvocation.java:130)
At Com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode (decodeablerpcinvocation.java:74)
At Com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody (dubbocodec.java:138)
At Com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode (exchangecodec.java:134)
At Com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode (exchangecodec.java:95)
At Com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.decode (dubbocountcodec.java:46)
At Com.alibaba.dubbo.remoting.transport.netty.nettycodecadapter$internaldecoder.messagereceived ( nettycodecadapter.java:134)
At Org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream (simplechannelupstreamhandler.java:70)
At Org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream (defaultchannelpipeline.java:564)
At Org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream (defaultchannelpipeline.java:559)
At Org.jboss.netty.channel.Channels.fireMessageReceived (channels.java:268)
At Org.jboss.netty.channel.Channels.fireMessageReceived (channels.java:255)
At Org.jboss.netty.channel.socket.nio.NioWorker.read (nioworker.java:88)
At Org.jboss.netty.channel.socket.nio.AbstractNioWorker.process (abstractnioworker.java:109)
At Org.jboss.netty.channel.socket.nio.AbstractNioSelector.run (abstractnioselector.java:312)
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)
At Java.util.concurrent.threadpoolexecutor$worker.run (threadpoolexecutor.java:615)
At Java.lang.Thread.run (thread.java:745)
Preliminary inference is FST jar packet conflict problem, to be validated after the line.
Can get off work, Dubbo FST failure of the problem is done. Is the bug that dubbo2.8.4 uses Fst,kryo to serialize.
Today's detours, if the first check on the GitHub on the commit record will not spend so much time:
I typed the network data that Dubbo called to find the problem:
This place is the number of parameters, is-1 caused the failure of the parse behind. The next time you use Dubbo 2.8.5.
