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] [Resolved] (AMQ-3315) Allow socket option soLinger to be enabled on TcpTransport
Date Wed, 11 May 2011 13:35:47 GMT

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

Gary Tully resolved AMQ-3315.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1101866&view=rev

On the broker side, the options need to be prefixed with 'transport.' such that they are applied
to accepted sockets. On the client the prefix is not needed.
For example, in broker configuration to enable keepAlive and soLinger for immediate return
from close for stomp, use:
<transportConnectors>
      <transportConnector uri="stomp://localhost:61613?transport.keepAlive=true&amp;transport.soLinger=0"/>
</transportConnectors>

> 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