You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Oren Kafka (JIRA)" <ji...@apache.org> on 2007/11/04 16:03:50 UTC

[jira] Created: (DIRMINA-468) SSL implementation, message size limitation (16384 bytes, 16K)

SSL implementation, message size limitation (16384 bytes, 16K)
--------------------------------------------------------------

                 Key: DIRMINA-468
                 URL: https://issues.apache.org/jira/browse/DIRMINA-468
             Project: MINA
          Issue Type: Bug
          Components: Filter
    Affects Versions: 1.1.4
         Environment: WIN32
            Reporter: Oren Kafka
            Priority: Critical


Using Mina SSL Filter with messages bigger than 16384 bytes (16K exactly !!!), a problem is encountered.

The details of the problem are:
1) Sending a big SSL message from the server to the client
2) Server is implemented with Mina, client is implemented with regular SSL socket.
3) The message sent is bigger than 16384 bytes on server side.

The problem:
On the client side, only first 16384 bytes  (16 K) are received.





-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (DIRMINA-468) SSL implementation, message size limitation (16384 bytes, 16K)

Posted by "Oren Kafka (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DIRMINA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oren Kafka closed DIRMINA-468.
------------------------------

    Resolution: Invalid

Hi Trustin,
I found the problem while reproducing as you requested and I'm closing the issue.
The problem was in the way of reading the input stream:
I used single read:
read = bis.read(expectedMessageSizeArray))

and changed it now to:
StringBuilder sb = new StringBuilder(i_msgSize);
byte[] byteArray = new byte[((i_msgSize<4096) ? i_msgSize : 4096)];
while ((allReadCounter != i_msgSize) 
                       && ((oneReadCounter = i_inputStream.read(byteArray)) != -1))
{
	sb.append(new String(byteArray,0,oneReadCounter));
	allReadCounter += oneReadCounter;
}

And it's working !!
Thank you very much for your time,
Oren.

> SSL implementation, message size limitation (16384 bytes, 16K)
> --------------------------------------------------------------
>
>                 Key: DIRMINA-468
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-468
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 1.1.4
>         Environment: WIN32
>            Reporter: Oren Kafka
>            Priority: Critical
>
> Using Mina SSL Filter with messages bigger than 16384 bytes (16K exactly !!!), a problem is encountered.
> The details of the problem are:
> 1) Sending a big SSL message from the server to the client
> 2) Server is implemented with Mina, client is implemented with regular SSL socket.
> 3) The message sent is bigger than 16384 bytes on server side.
> The problem:
> On the client side, only first 16384 bytes  (16 K) are received.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DIRMINA-468) SSL implementation, message size limitation (16384 bytes, 16K)

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRMINA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540339 ] 

Trustin Lee commented on DIRMINA-468:
-------------------------------------

It would be also nice if you can provide a reproduceable example code.  My test just works fine.

> SSL implementation, message size limitation (16384 bytes, 16K)
> --------------------------------------------------------------
>
>                 Key: DIRMINA-468
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-468
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 1.1.4
>         Environment: WIN32
>            Reporter: Oren Kafka
>            Priority: Critical
>
> Using Mina SSL Filter with messages bigger than 16384 bytes (16K exactly !!!), a problem is encountered.
> The details of the problem are:
> 1) Sending a big SSL message from the server to the client
> 2) Server is implemented with Mina, client is implemented with regular SSL socket.
> 3) The message sent is bigger than 16384 bytes on server side.
> The problem:
> On the client side, only first 16384 bytes  (16 K) are received.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (DIRMINA-468) SSL implementation, message size limitation (16384 bytes, 16K)

Posted by "Trustin Lee (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DIRMINA-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12540334 ] 

Trustin Lee commented on DIRMINA-468:
-------------------------------------

Could you please provide a DEBUG log of the SSL filter?

> SSL implementation, message size limitation (16384 bytes, 16K)
> --------------------------------------------------------------
>
>                 Key: DIRMINA-468
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-468
>             Project: MINA
>          Issue Type: Bug
>          Components: Filter
>    Affects Versions: 1.1.4
>         Environment: WIN32
>            Reporter: Oren Kafka
>            Priority: Critical
>
> Using Mina SSL Filter with messages bigger than 16384 bytes (16K exactly !!!), a problem is encountered.
> The details of the problem are:
> 1) Sending a big SSL message from the server to the client
> 2) Server is implemented with Mina, client is implemented with regular SSL socket.
> 3) The message sent is bigger than 16384 bytes on server side.
> The problem:
> On the client side, only first 16384 bytes  (16 K) are received.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.