Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 5 Jan 2015 23:55:34 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12758816.1417489134000.14894.1420502134942@Atlassian.JIRA>
In-Reply-To: <JIRA.12758816.1417489134000@Atlassian.JIRA>
References: <JIRA.12758816.1417489134000@Atlassian.JIRA>
 <JIRA.12758816.1417489134010@arcas>
Subject: [jira] [Resolved] (AMQ-5468) AMQ MQTT doesn't reject remote
 connection after a long time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Fixed on trunk, you can use the 'transport.connectAttemptTimeout' option to configure how long before the opened connection is kept around without receiving a CONNECT frame from the client.  Default value is set to 30 seconds.

> AMQ MQTT doesn't reject remote connection after a long time 
> ------------------------------------------------------------
>
>                 Key: AMQ-5468
>                 URL: https://issues.apache.org/jira/browse/AMQ-5468
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector, MQTT
>    Affects Versions: 5.9.0, 5.9.1, 5.10.0
>         Environment: Linux
>            Reporter: Nguyen Hong Phu
>            Assignee: Timothy Bish
>             Fix For: 5.11.0
>
>
> Test steps:
> - Using jConsole to explore JMX MBean clientConnectors (MQTT+NIO connector). 
> - Using telnet client connect to MQTT+NIO port
> - On jConsole: clientConnectors/mqtt+nio/remoteAddess appear a new connection with IP and local port which connect to.
> - Close telnet program
> - Waiting a long time (could be more than a day) and view remoteAddess again on jConsole but Remote IP (telnet) does not remove.
> Imagine that if a human open a thousand or million connections to server, AMQ not release connections after short time, then AMQ could be throws the ERROR "To many open files" and it doesn't access new connection.
> In production server (ulimit max-open-files 65000), i'm using 2 thousand clients but after 2 days, many ERROR "To many open files" in activemq.log to be throws.
> On jConsole, number of clientId is equals with clients, but RemoteIP contains more than 65000 IPs.


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