Hi Alexey,
The SSL problem can be reproduced by running the MQ 4.4 broker
with STOMP protocol support enabled (which uses Grizzly framework)
and a simple STOMP Java client. I'll give you a pointer for MQ 4.4
build4 and the test client with instruction.
Thanks,
amy
----- Original Message -----
From: Oleksiy Stashok <Oleksiy.Stashok_at_Sun.COM>
Date: Tuesday, March 24, 2009 2:39 pm
Subject: Re: problem receiving large size message over SSL
To: users_at_grizzly.dev.java.net
Hi Amy,
it will help a lot, if you can attach the testcase sources to
reproduce the issue.
Thanks.
WBR,
Alexey.
On Mar 24, 2009, at 21:14 , Amy Kang wrote:
> Hi,
>
> When receiving large size message, e.g. 10M (or sometime even smaller
> like 10K), over SSL, Grizzly seems silently stops calling my
> protocol parser
> after iterates a few times with its ByteBuffer state repeately shown
> in
> ProtocolParser.hasNextMessage:
>
> _buffer=java.nio.HeapByteBuffer[pos=16384 lim=33320 cap=33320]
>
> however for TCP, the same code has no problem receiving 10M or
> even larger size messages.
>
> (attached logs for SSL case)
>
> Thanks,