You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by afa654321 <af...@yahoo.com> on 2007/01/09 00:13:47 UTC
No appropriate message decoder
Hello,
I've built a client-server(using "SumUp" as a guide). The client sends
variable-length array of bytes.
I was getting the above-mentioned exception in the server, so in order to
simulate the problem I used the Server
program(with no changes) from the "SumUp" example and can re-create the
problem(get the same "ProtocolDecoderException")
the line of code in the server that gets the array from the ByteBuffer is:
byte[] array = new byte[in.remaining()];
in.get(array, 0, in.remaining());
where in is a ref to the ByteBuffer
Any idea as to the cause of the exception?
Thx.
--
View this message in context: http://www.nabble.com/No-appropriate-message-decoder-tf2942800.html#a8228768
Sent from the mina dev mailing list archive at Nabble.com.
Re: No appropriate message decoder
Posted by afa654321 <af...@yahoo.com>.
Thx Trustin.
Problem solved! I was't properly processing the header on the server side!
Trustin Lee wrote:
>
> Hello,
>
> On 1/9/07, afa654321 <af...@yahoo.com> wrote:
>>
>> Hello,
>>
>> I've built a client-server(using "SumUp" as a guide). The client sends
>> variable-length array of bytes.
>> I was getting the above-mentioned exception in the server, so in order to
>> simulate the problem I used the Server
>> program(with no changes) from the "SumUp" example and can re-create the
>> problem(get the same "ProtocolDecoderException")
>>
>> the line of code in the server that gets the array from the ByteBuffer
>> is:
>>
>> byte[] array = new byte[in.remaining()];
>> in.get(array, 0, in.remaining());
>>
>> where in is a ref to the ByteBuffer
>>
>> Any idea as to the cause of the exception?
>
> There are three possible causes in 'No appropriate message decoder'
> method.
>
> 1) You didn't register your message decoder.
> 2) You didn't program your decoder properly.
> 3) Your client has a problem.
>
> We can't cherry-pick the cause of the problem because the information
> you gave us are so vague.
>
> Trustin
> --
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP key fingerprints:
> * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
> * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
>
>
--
View this message in context: http://www.nabble.com/No-appropriate-message-decoder-tf2942800.html#a8246949
Sent from the mina dev mailing list archive at Nabble.com.
Re: No appropriate message decoder
Posted by Trustin Lee <tr...@gmail.com>.
Hello,
On 1/9/07, afa654321 <af...@yahoo.com> wrote:
>
> Hello,
>
> I've built a client-server(using "SumUp" as a guide). The client sends
> variable-length array of bytes.
> I was getting the above-mentioned exception in the server, so in order to
> simulate the problem I used the Server
> program(with no changes) from the "SumUp" example and can re-create the
> problem(get the same "ProtocolDecoderException")
>
> the line of code in the server that gets the array from the ByteBuffer is:
>
> byte[] array = new byte[in.remaining()];
> in.get(array, 0, in.remaining());
>
> where in is a ref to the ByteBuffer
>
> Any idea as to the cause of the exception?
There are three possible causes in 'No appropriate message decoder' method.
1) You didn't register your message decoder.
2) You didn't program your decoder properly.
3) Your client has a problem.
We can't cherry-pick the cause of the problem because the information
you gave us are so vague.
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6