Hi Lahiru, I've had a quick look at trunk - the exception actually ripples up from the MINA ByteBuffer.getString() call.
Are you sure that your message content is UTF-8 ? Most of the reports of this issue with MINA appear to be caused by binary/non-UTF-8 content in text messages. Regards, Marnie On Fri, Nov 26, 2010 at 1:08 PM, Lahiru Gunathilake <[email protected]>wrote: > Hi Marnie, > > Thanks Marnie for your response. > > No, i do not think this is a timing issue, even when I debug I am getting > this error. It's a good news that this is a known issue. > > Are you capable of reading messages larger than 1 MB ? If you are using any > configuration can you please post here ? That will be very useful ! > > Lahiru > > On Fri, Nov 26, 2010 at 6:23 PM, Marnie McCormack < > [email protected]> wrote: > > > Hi Lahiru, > > > > There's a JIRA about this exception/issue - QPID-2902. > > > > Does it fail for you reliably ? I wonder if there's a timing issue here > > since it didn't occur all the time on the CI instance. > > > > Marnie > > > > On Fri, Nov 26, 2010 at 12:14 PM, Lahiru Gunathilake <[email protected] > > >wrote: > > > > > Hi Devs, > > > > > > When I consume a big message with 1MB file size and pick it from Qpid > > > Queue, > > > I am getting an error like this > > > > > > avax.jms.JMSException: Could not decode string data: > > > java.nio.charset.MalformedInputException: Input length = 1<br> at > > > > > > > > > org.apache.qpid.client.message.JMSTextMessage.getText(JMSTextMessage.java:150) > > > > > > After debugging the code, I feel like this happen, due to a malformed > > input > > > stream coming for the client. > > > > > > Can I increase the frame-size of the client and get this message in to > a > > > single frame ? Is there any other solution to this error. > > > > > > Regards > > > Lahiru > > > > > >
