I got a strange error when using netty(with camel), we use LengthFieldBasedFrameDecoder for communication, sometimes got two messages "merged" into one, and hence the forthcoming data get all wrong.
for example: client send two messages: [10]AAAAAAAAAAAAAAAA and [10]BBBBBBBBBBBBBBBB where [10] is the length bytes and AAAAAAAAAA is the data. but on the server we got [10]AAAAAA[10]BBBBBBBBBBBBBBBBAAAAAAAAAA seems the the first message got split by the second one, so the decoder interpreted the data as: [10]AAAAAA[10]BBBBBBBB and BBBBBBBBAAAAAAAAAA................................................... so that the first message is correct in length but wrong in data, and the second message is wrong in length "BB", and get a much longer data packet. hope I described clearly, anyone met this before? I'm not sure whether it is a netty bug or a camel-netty one, hope someone can help. -- View this message in context: http://camel.465427.n5.nabble.com/buffer-corruption-in-camel-netty-tp5551122p5551122.html Sent from the Camel - Users mailing list archive at Nabble.com.
