[
https://issues.apache.org/jira/browse/AMQ-9748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010642#comment-18010642
]
Lionel Cons commented on AMQ-9748:
----------------------------------
Also, the problem happens only on some brokers so the problem might be linked
to specific (STOMP) clients.
OTOH, the ActiveMQ metrics (here {{CurrentConnectionsCount}}) should always
match what the OS reports, regardless of the client behavior...
> Incorrect CurrentConnectionsCount metric
> ----------------------------------------
>
> Key: AMQ-9748
> URL: https://issues.apache.org/jira/browse/AMQ-9748
> Project: ActiveMQ Classic
> Issue Type: Bug
> Affects Versions: 6.1.5
> Reporter: Lionel Cons
> Priority: Major
>
> In some cases, the current number of connections (as reported via JMX) is not
> correct.
> We did not find any easy way to reproduce the problem. It seems to happen
> when there are some rapid re-connections from the client side. Then the
> counter stays wrong (too high) until the broker is restarted.
> Here is for instance what can currently be seen on one broker:
> {code}
> # jolokia http://localhost:61705/api/jolokia read
> 'org.apache.activemq:type=Broker,brokerName=*' CurrentConnectionsCount
> {"org.apache.activemq:brokerName=lhcb_mb129.cern.ch,type=Broker":{"CurrentConnectionsCount":4955}}
> # netstat --tcp -n | grep ESTABLISHED | wc -l
> 63
> {code}
> So ActiveMQ reports 4955 active/current connections but the OS (Linux here)
> disagrees.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
