StreamCorruptedException when using CompatibleObjectDecoder/CompatibleObjectEncoder
IanGuedes
iangm at ig.com.br
Mon Mar 16 02:15:26 EDT 2009
Hi Trustin,
I think the problem has something to do with a mistaken read of header /
body part of the serialized object. I haven't tested the ObjectDecoder, so I
don't know if the same problem of the CompatibleObjectDecoder also happens
with it.
Please let us know when you find out what was the real cause, and the
"official" solution :-)
Best regards,
Ian
Trustin Lee-2 wrote:
>
> Doh, nevermind. I can reproduce the problem now.
>
> — Trustin Lee, http://gleamynode.net/
>
> On Mon, Mar 16, 2009 at 2:09 PM, Trustin Lee <tlee at redhat.com> wrote:
>> Hi Ian,
>>
>> Sorry for not replying to your question mistakenly. I know you
>> already worked around the problem, but would you mind if you provide
>> me a simple application that reproduces the problem you experienced?
>> I tried to reproduce the problem with object echo example, but
>> couldn't.
>>
>> Thanks,
>>
>> — Trustin Lee, http://gleamynode.net/
>>
>
--
View this message in context: http://n2.nabble.com/StreamCorruptedException-when-using-CompatibleObjectDecoder-CompatibleObjectEncoder-tp2468712p2484300.html
Sent from the Netty User Group mailing list archive at Nabble.com.
More information about the netty-users
mailing list