Hi Jaromir,
Thanks for your response.
Yes, ours is an web application running on Tomcat. Hazelcast is packaged inside WAR. I am not sure whether it is related to application re-deployment or not. Our IT admin guys says that our application was up when this issue occurred, so I am assuming that it is not related to re-deployment.
I've few questions and it will be great if I can get answer to those:
- Does this issue cause any functional impact?
- What are possible reasons for this issue to happen?
- Does it make sense to shutdown hazelcast instance when my application is stopped? As of now, we are not doing it and I think it makes sense to do it. But I am not sure if this is the reason we are seeing this exception in our application.
PFA, code that we use in our application for Hazelcast.
Thanks,
Aman