activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-5587) AMQP shutdown transport if no connection attempt received after a configurable delay.
Date Fri, 13 Feb 2015 22:10:12 GMT

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

Timothy Bish resolved AMQ-5587.
-------------------------------
    Resolution: Fixed

Add a connect check in the inactivity monitor to account for opened
connections that might drop but not be spotted, in the case where the
connect frame is lost this can lead to connections that aren't fully
opened and won't be cleaned up until the broker detects the socket has
failed.

By default the connection timer is set to 30 seconds, if no connect
frame is read by then the connection is dropped.  The broker can be
configured via the 'transport.connectAttemptTimeout' URI option, a value

> AMQP shutdown transport if no connection attempt received after a configurable delay.
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-5587
>                 URL: https://issues.apache.org/jira/browse/AMQ-5587
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 5.10.0, 5.10.1, 5.11.0, 5.11.1, 5.10.2
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.12.0
>
>
> When a socket level connection is made to the AMQP TransportConnector where the client
end does not initiate a new AMQP connection we should shutdown the Transport after a configurable
inactivity duration (default at 30sec). 
> A similar feature was added for MQTT in AMQ-5468



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message