camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller <christian.muel...@gmail.com>
Subject Re: Incomplete Messages
Date Wed, 21 Aug 2013 20:39:18 GMT
I suggest to reporg the problem to the sending application. They should
sent the correct content size.
IF you have to deal with this issue, I suggest to post this question to the
mina user list, becausr this isn't really a Camel question.

Best,
Christian
Am 21.08.2013 20:39 schrieb "milltj" <milltj@drop-tank.com>:

> I have been playing with the Mina2 component and have a need to implement
> my
> own decoder.  The messages that I receive have a 28 byte header followed by
> a variable length XML message.  The header contains the length of the XML
> message as well as some other information.  I am running into a problem
> that
> in some cases the reported XML length in the header is greater then the
> what
> is reported when calling in.remaining().  For example, the XML Length
> header
> contains a length of 2735 bytes, but the in.remaining() reports 2020.  if I
> call in.get(byte[]) and pass it a byte array of size 2735, I get an
> UnderrunException.  If I only retrieve the bytes in the buffer then I get
> an
> incomplete message. I have looked at the example at the Mina website but I
> am confused by it, I don't quite follow what it is doing.  Can someone
> point
> me to an example of what I would need to implement in my doDecode(...)
> method that would insure I get a complete message everytime?
>
> Thanks!
> - Tim
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Incomplete-Messages-tp5737696.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message