Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NetworkingService JMX Problem - clientConnectionCount #15681

Closed
mesutcelik opened this issue Oct 4, 2019 · 0 comments · Fixed by #15861
Closed

NetworkingService JMX Problem - clientConnectionCount #15681

mesutcelik opened this issue Oct 4, 2019 · 0 comments · Fixed by #15861

Comments

@mesutcelik
Copy link
Contributor

@mesutcelik mesutcelik commented Oct 4, 2019

Hi,

I am trying to trace a weird problem in Hazelcast Management Beans.

In 3.11.4, ConnectionManagerMBean.getCurrentClientConnections is returning correct value

However, If I switch to 3.12.2, I expect the same is returned by NetworkingServiceMBean. getCurrentClientConnections but it is not the case.

This is the output from VisualVM. The value is displayed as Unavailable

Apparently, this problem causes a parsing problem in Prometheus jmx_exporter used in Hazelcast Docker Image. Here is the related issue raised in hazelcast-docker repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.