activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-5468) AMQ MQTT doesn't reject remote connection after a long time
Date Mon, 08 Dec 2014 23:01:13 GMT


Timothy Bish commented on AMQ-5468:

You can add the keepAlive option to your transport connector and configure the OS to check
on a more regular interval than the default two hour value.  When you close the telnet session
you leave a half open socket and the broker needs the TCP stack to signal that it has gone
so keepAlive would be a good solution.  

> AMQ MQTT doesn't reject remote connection after a long time 
> ------------------------------------------------------------
>                 Key: AMQ-5468
>                 URL:
>             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
> 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

View raw message