activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nguyen Hong Phu (JIRA)" <>
Subject [jira] [Commented] (AMQ-5468) AMQ MQTT doesn't reject remote connection after a long time
Date Sun, 08 Feb 2015 14:29:35 GMT


Nguyen Hong Phu commented on AMQ-5468:

Thanks Timothy Bish, 

Great :)

I have problem with amq version 5.9.1. Since amq version 5.11 it OK, after 60000 ms, zoombie
of socket session (telnet etc..) auto destroy properly :)

But i have another problem with version 5.10 and above. Comsumer JMS (Resource adapter + Glassfish)
working not properly, i created a problem here:

Many thanks Timothy!

> 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
>            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

View raw message