[
https://issues.apache.org/jira/browse/AMQ-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265233#comment-14265233
]
Timothy Bish commented on AMQ-5468:
-----------------------------------
Given that many MQTT clients will run on potentially unreliable connections
it's probably not a bad idea to add in connection negotiation timeout detection
simillar to that of the OpenWire transport. Unlike STOMP MQTT is binary and
would not be usable in telnet which is why the STOMP transport doesn't
implement this.
> 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
>
> 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)
