I have implemented an service application in java with MuleSoft 3.5.1 that it works in cluster server, and sometimes I get an error "Hazelcast instance is not active!" and the all service are bloked, so I must restart both server to resolve the problem. The hazelcast-3.1.6.jar is in my project.
ERROR 2015-06-22 09:39:00,425 [[gs_p_api_QA-vGS_P_0_1_18].http1_connector.receiver.06] org.mule.exception.DefaultMessagingExceptionStrategy:
*****************************************************************************
Message : Hazelcast instance is not active! (com.hazelcast.core.HazelcastInstanceNotActiveException). Message payload is of type: HashMap
Code : MULE_ERROR-29999
--------------------------------------------------------------------------------
Exception stack is:
1. Hazelcast instance is not active! (com.hazelcast.core.HazelcastInstanceNotActiveException)
com.hazelcast.spi.impl.ProxyServiceImpl$ProxyRegistry:220 (null)
2. Hazelcast instance is not active! (com.hazelcast.core.HazelcastInstanceNotActiveException). Message payload is of type: HashMap (org.mule.api.MessagingException)
org.mule.execution.ExceptionToMessagingExceptionExecutionInterceptor:32 (http://www.mulesoft.org/docs/site/current3/apidocs/org/mule/api/MessagingException.html)
--------------------------------------------------------------------------------
Root Exception stack trace:
com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!
at com.hazelcast.spi.impl.ProxyServiceImpl$ProxyRegistry.<init>(ProxyServiceImpl.java:220)
at com.hazelcast.spi.impl.ProxyServiceImpl$ProxyRegistry.<init>(ProxyServiceImpl.java:207)
at com.hazelcast.spi.impl.ProxyServiceImpl$1.createNew(ProxyServiceImpl.java:69)
+ 3 more (set debug level logging or '-Dmule.verbose.exceptions=true' for everything)
********************************************************************************
How can I resolve this problem definitively?
I hit the similar exception of "com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast instance is not active!" when running a web app. In my case, it was caused by OutOfMemory, though it was not obvious initially.
I reckon you may have a memory issue, which causes the HashMap getting too large perhaps.