activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (AMQ-3315) Allow socket option soLinger to be enabled on TcpTransport
Date Thu, 12 May 2011 09:44:47 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Tully reopened AMQ-3315:
-----------------------------


provide option to be able to turn off soLinger, in case on with delay 0 is not sufficient:

so:{code}
transport.soLinger=-1  - SO_LINGER=OFF
transport.soLinger=N (N>0) - SO_LINGER=ON, delay=N
{code}


> Allow socket option soLinger to be enabled on TcpTransport
> ----------------------------------------------------------
>
>                 Key: AMQ-3315
>                 URL: https://issues.apache.org/jira/browse/AMQ-3315
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Transport
>    Affects Versions: 5.5.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: close, soLinger, stomp, tcptransport
>             Fix For: 5.6.0
>
>
> soLinger as a socket option takes two args so it cannot be set via the simple socket
option introspection. It needs an attribute on TcpTransport. It is handy for stomp where connections
are short lived as it can increase the socket.close() turnaround when set to 0.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message