Alessandro Celotti created AMQ-6961:
---------------------------------------
Summary: ActiveMQ broker does not detect dead clients
Key: AMQ-6961
URL: https://issues.apache.org/jira/browse/AMQ-6961
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.15.3
Reporter: Alessandro Celotti
Attachments: activemq.xml.conf
I have a system formed by 1 client producer on an AMQ queue, which uses
OpenWire connection with the broker. The consumers of this broker are embedded
C clients, which are connected to the broker using STOMP transport. When the
consumer clients crash or do not close their connections the broker does not
detect the event and do not close the connection with the consumers. My STOMP
clients set the HEARTBEAT in the CONNECT with the values (1500,1500) and the
broker response with a CONNECTED with the same values. Every second the
consumer clients send a message to the broker to keep alive the connection
using a topic with no subscribers.
I have done some tests installing the broker in Linux and Windows environments
and I have noticed, that in Linux the broker closes the connection after 1:40
minutes, while in Windows after 0:20 seconds. It seems that the reason is due
to the fact that the socket is still ESTABLISHED and populated by the broker
until the maximum buffer size allowed. In fact if I disable the only one
producer this problem does not happen anymore.
I will attach you my activemq.xml configuration.
Thanks,
Alessandro
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
