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.destroy() clears map instead of destroy #764

Closed
f1ax opened this issue Aug 23, 2013 · 0 comments
Closed

IMap.destroy() clears map instead of destroy #764

f1ax opened this issue Aug 23, 2013 · 0 comments
Assignees
Milestone

Comments

@f1ax
Copy link

f1ax commented Aug 23, 2013

Hazelcast node is on separate JVM.
Native client:

ClientConfig config = new ClientConfig();
config.getGroupConfig().setName( "group" );
config.getGroupConfig().setPassword( "passwd" );
config.addAddress( address );
HazeclastInstance hz = HazelcastClient.newHazelcastClient( config )
IMap inst = hz.getMap( name );
inst.destroy();

Does not actually destroy map, only clears
For example, empty map still presents in getDistributedObjects() after map.destroy()

hazelcast-3.0.1-20130822.144602-33.jar
hazelcast-client-3.0.1-20130822.144618-33.jar

@ghost ghost assigned gurbuzali Aug 23, 2013
gurbuzali pushed a commit to gurbuzali/hazelcast that referenced this issue Aug 26, 2013
mdogan added a commit that referenced this issue Aug 26, 2013
client destroy requests fixed fixes #764
mdogan added a commit that referenced this issue Aug 26, 2013
devOpsHazelcast pushed a commit that referenced this issue Feb 14, 2024
GitOrigin-RevId: 68344dd73dd7352076e22d18676356b213e32013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants