+1
try {
lock.unlock();
} catch (HazelcastInstanceNotActiveException e) {
if(!ServerStatus.STATUS_SHUTTING_DOWN.equals(ServerStatus.getCurrentStatus())){
log.error(Could not release Hazelcast
coordinator
How about ignoring this exception for the moment. This is an harmless error
log it seems. Until we find a proper way to fix this we can ignore this
exception. This exception occurs during the server shutdown and it does not
do any harm.
ILock lock =
There is a method to check in CarbonKernel if the server is shutting down.
It sets the SHUTTING_DOWN status or something like that. So what we could
do is this;
* try {*
*lock.unlock();*
*} catch (HazelcastInstanceNotActiveException e) {*
*
Hi Azeez,
This exception does not get logged in the coordinator node, only in all
other nodes. So this error happens when they are blocked to get the
distributed lock. Yeah we can implement your suggestion for the unlock
scenario, but for the lock scenario we still don't have a solution other
Can do the same thing, and catch the exception on lock as well, and ignore
if the status is SHUTTING_DOWN
On Thu, Oct 16, 2014 at 11:06 AM, Sameera Jayasoma same...@wso2.com wrote:
Hi Azeez,
This exception does not get logged in the coordinator node, only in all
other nodes. So this error
Hi Azeez,
We are currently doing testing in carbon 4.3.0 with the latest hazelcast
3.2.6 upgrade. And when shutting down a server using (ctrl +c ) following
error occurred.
This was reported earlier also here [1] in carbon 4.2.0.
Exception in thread Cluster [wso2.as.domain] coordinator elector
