[jboss-remoting-issues] [JBoss JIRA] Created: (JBREM-1226) Sockets created by bisocket secondary ServerSocket should be configured properly

Ron Sigal (JIRA) jira-events at lists.jboss.org
Tue May 18 11:54:06 EDT 2010


Sockets created by bisocket secondary ServerSocket should be configured properly
--------------------------------------------------------------------------------

                 Key: JBREM-1226
                 URL: https://jira.jboss.org/browse/JBREM-1226
             Project: JBoss Remoting
          Issue Type: Bug
      Security Level: Public (Everyone can see)
    Affects Versions: 2.2.3.SP2, 2.5.2.SP3 (Flounder)
            Reporter: Ron Sigal
            Assignee: Ron Sigal
             Fix For: 2.2.3.SP3, 2.5.2.SP4 (Flounder) 


Sockets created by org.jboss.remoting.transport.socket.SocketServerInvoker are configured by 

   protected void configureSocket(Socket s) throws SocketException
   {
      s.setReuseAddress(getReuseAddress());
      
      if (keepAliveSet)           s.setKeepAlive(keepAlive);
      if (oOBInlineSet)           s.setOOBInline(oOBInline);
      if (receiveBufferSize > -1) s.setReceiveBufferSize(receiveBufferSize);
      if (sendBufferSize > -1)    s.setSendBufferSize(sendBufferSize);
      if (soLingerSet && 
            soLingerDuration > 0) s.setSoLinger(soLinger, soLingerDuration);
      if (trafficClass > -1)      s.setTrafficClass(trafficClass);
   }

but configureSocket() is not called for sockets created by org.jboss.remoting.transport.bisocket.BisocketServerInvoker.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jboss-remoting-issues mailing list