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

IMap MBean is not created when client reconnects to cluster #12417

Closed
yozank opened this issue Feb 22, 2018 · 2 comments
Closed

IMap MBean is not created when client reconnects to cluster #12417

yozank opened this issue Feb 22, 2018 · 2 comments

Comments

@yozank
Copy link
Contributor

@yozank yozank commented Feb 22, 2018

MBean for IMap is not created when client uses cached map proxy.

When the client disconnects from the cluster, it does not clear the cache for distributed object proxies. To get a proxy for a distributed object, we see proxyManager.getOrCreateProxy(serviceName, name) is called.
Then in getOrCreateProxy, proxy is obtained from cache.

The scenario as follows:

Member is up with JMX enabled. Client connects and creates a map. In a for loop, it puts data to map.
MBean for the map is monitored via JMX.
Member is restared.
Client reconnects to member and continues to put entries on the map.
Now, MBean cannot be monitored via JMX.
Here expectation is the recreation of MBean after client reconnects and operates on the map.

@sancar sancar modified the milestones: 3.10, 3.9.4 Feb 23, 2018
@jerrinot
Copy link
Contributor

@jerrinot jerrinot commented Feb 23, 2018

I assume this is an issue only when there is a single cluster member? is it correct?

as when you have a multiple members and restart one of them then on a join it'll receive a list of created distributed objects.

@yozank
Copy link
Contributor Author

@yozank yozank commented Feb 26, 2018

When you restart individual cluster members there is no problem. When the-only-jmx-enabled-member-of-a-cluster reconnects to a jmx-disabled-cluster, it receives the list of distributed objects and creates MBeans.

However, when a client reconnects to a fully shutdown&restarted cluster, MBean for IMap is not created.

@sancar sancar self-assigned this Feb 27, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 8, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 9, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 9, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 9, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 14, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 14, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 22, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 23, 2018
sancar added a commit to sancar/hazelcast that referenced this issue Mar 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

4 participants
You can’t perform that action at this time.