[ 
https://issues.apache.org/jira/browse/DIRMINA-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084271#comment-17084271
 ] 

Jonathan Valliere commented on DIRMINA-1123:
--------------------------------------------

You cannot set the buffer sizes BEFORE accept() is called because 
http://man7.org/linux/man-pages/man2/accept.2.html the socket does not exist 
until accept() is called and the new file descriptor is returned  As you 
stated, this is AFTER the initial handshake is done.  
https://stackoverflow.com/questions/5968132/are-socket-options-inherited-across-accept-from-the-listening-socket
  I could set the options on the server-socket regardless but it won't fix your 
problem unless the underlying OS supports inheritance.

> Receive buffer size is never set for NIO acceptor
> -------------------------------------------------
>
>                 Key: DIRMINA-1123
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-1123
>             Project: MINA
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 2.0.22, 2.1.3
>            Reporter: Marcin L
>            Assignee: Jonathan Valliere
>            Priority: Minor
>         Attachments: case dumps.png, case1.pcap, case2.pcap, case3.pcap
>
>
> Acceptor window size can't be increased beyond OS defaults.
> It seems the receive buffer size is properly set for 
> org.apache.mina.transport.socket.nio.NioSocketConnector, but it is not set at 
> all forĀ org.apache.mina.transport.socket.nio.NioSocketAcceptor before socket 
> is bound.
> org.apache.mina.core.polling.AbstractPollingIoAcceptor.Acceptor#registerHandles
>  comment states that receive buffer size should be initialised, but thenĀ 
> org.apache.mina.transport.socket.nio.NioSocketAcceptor#open does not do it.,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to