and the other error is getting printed in logs continuously is as below.
Illegal access: this web application instance has been stopped already.
Could not load [com.hazelcast.client.impl.protocol.ClientMessage]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: I
llegal access: this web application instance has been stopped already.
Could not load [com.hazelcast.client.impl.protocol.ClientMessage].
The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
It looks you had deployed a webapplication with an embedded Hazelcast. Then you undeployed the application from Tomcat, but the application failed to stop Hazelcast instance. You should always stop all Hazelcast instances when an application is being stopped. the simplest thing should be to call HazelcastInstance.shutdown() from a context listener. See an example here: https://www.codejava.net/java-ee/servlet/weblistener-annotation-examples
One of our customers is facing high latency around 4 to 8 mins between publishing a message on an iTopic and receiving the message at subscribers' end. This delay is intermittent and happens around 4-5 times a day. As per the load on the infrastructure and GC utilization is normal. Any suggestions?
Unmatched arguments: cluster, add, --lenient=true, -H, /data, -cc, /config/hazelcast-client.yaml
Did you mean: create-user or change-user-password or update-ldap-password?
3.12.8 Management Center image. With 4.0 release, the way Management Center connects to and communicates with Hazelcast clusters has been changed so we have modified related commands and configurations at our Helm chart as well. To start 3.12.8 Management Center, you need to use 2.10.0 as a chart version --> helm install <name> --set <parameters> --version 2.10.0 hazelcast/hazelcast
Hi all
I am getting
`[0.0.0.0]:8099 [dev] [4.0.2] While sending op error... op: com.hazelcast.internal.cluster.impl.operations.JoinMastershipClaimOp{serviceName='hz:core:clusterService', identityHash=188472785, partitionId=-1, replicaIndex=0, callId=5, invocationTime=1597066923255 (2020-08-10 19:12:03.255), waitTimeout=-1, callTimeout=60000}, error: java.lang.IllegalArgumentException: Target is this node! -> [0.0.0.0]:8099
java.lang.IllegalArgumentException: Target is this node! -> [0.0.0.0]:8099, response: ErrorResponse{callId=5, urgent=true, cause=java.lang.IllegalArgumentException: Target is this node! -> [0.0.0.0]:8099}`
config.setLiteMember(false);
// setting up the local grid server
config.getNetworkConfig().setPublicAddress("0.0.0.0").setPort(8099).setPortAutoIncrement(true);
// setting up the cluster
System.out.println( Arrays.asList(environment).toString());
JoinConfig join = config.getNetworkConfig().getJoin();
join.getMulticastConfig().setEnabled(false);
join.getAwsConfig().setEnabled(false);
join.getTcpIpConfig().setEnabled(true).setMembers(Arrays.asList(environment));
CacheSimpleConfig cacheConfig = new CacheSimpleConfig();
cacheConfig.setName("buckets");
config.addCacheConfig(cacheConfig);```ok. in this case you need to provide details about your environment and topology. clearly setPublicAddress("0.0.0.0") is wrong.
the question is: what should be there instead? (if anything at all)
here is what I know so far:
- you have 2 Hazelcast instances running on 1 server
- there is another instance running on a different service.
- all instances are in the same network
- all 3 instances are supposed to form a single cluster
is :point_up: correct?
setPublicAddress() sets an IP address others should use to talk to this member. this is usually needed when you have multiple networks and what not.for some reason you have
0.0.0.0 which CANNOT ever be used to talk to this member. The address 0.0.0.0 has a special meaning in IP networks.
- use multicast discovery. this is the default. it's simple to use and has no external dependency. but it does not work on most cluster providers as clouds do not allow multicast traffic.
- use static configuration. then you have to know IP address of all your members. I see you use
join.getTcpIpConfig().setEnabled(true).setMembers(Arrays.asList(environment));for this joiner you have to know all IP addresses anyway. - use a discovery plugin. this is the most popular option when deploying in clouds. we have discovery plugins for AWS, Azure, GCP, Kubernetes, Zookeepr, Eureka, etc..
setPublicAddress("127.0.0.1") will work only on a single box. again, remove that. most likely you dont need at all.