Yes, as a final precaution, let's just catch the exception and log it.
public void clear() {
if (hazelcastInstance.getLifecycleService().isRunning()) {
try{
map.clear();
}catch(HazelcastInstanceNotActiveException e){
log.debug("", e);
}
}
}
On Thu, Oct 10, 2013 at 8:02 PM, Shelan Perera <[email protected]> wrote:
> Hi Azeez,
>
> In the DistMap we have handled all these cases and still we can get this
> at shutdowns very rarely. Can this be a race condition that when it was
> checking the instance was active and just after that it was not.
>
> public void clear() {
> if (hazelcastInstance.getLifecycleService().isRunning()) {
> map.clear();
> }
> }
>
>
> Thanks
>
>
>
> On Thu, Oct 10, 2013 at 12:04 AM, Evanthika Amarasiri
> <[email protected]>wrote:
>
>> I see this when shutting down the ESB server. This is with Pre-M4 packs.
>>
>> [2013-10-10 12:16:35,510] INFO - ServerManagement Starting to switch to
>> maintenance mode...
>> [2013-10-10 12:16:35,511] INFO - PassThroughHttpSSLListener Stopping
>> Pass-through HTTPS Listener..
>> [2013-10-10 12:16:35,514] ERROR - PermissionUpdater Error when clearing
>> the permission cache for tenant : 3
>> com.hazelcast.core.HazelcastInstanceNotActiveException: Hazelcast
>> instance is not active!
>> at com.hazelcast.spi.impl.InvocationImpl.doInvoke(InvocationImpl.java:121)
>> at com.hazelcast.spi.impl.InvocationImpl.invoke(InvocationImpl.java:106)
>> at
>> com.hazelcast.spi.impl.OperationServiceImpl.invokeOnPartitions(OperationServiceImpl.java:490)
>> at
>> com.hazelcast.spi.impl.OperationServiceImpl.invokeOnAllPartitions(OperationServiceImpl.java:424)
>> at
>> com.hazelcast.map.proxy.MapProxySupport.clearInternal(MapProxySupport.java:477)
>> at
>> com.hazelcast.map.proxy.MapProxyImpl.clearInternal(MapProxyImpl.java:44)
>> at com.hazelcast.map.proxy.MapProxyImpl.clear(MapProxyImpl.java:388)
>> at
>> org.wso2.carbon.core.clustering.hazelcast.HazelcastDistributedMapProvider$DistMap.clear(HazelcastDistributedMapProvider.java:144)
>> at org.wso2.carbon.caching.impl.CacheImpl.removeAll(CacheImpl.java:585)
>> at
>> org.wso2.carbon.user.core.authorization.AuthorizationCache.clearCache(AuthorizationCache.java:181)
>> at
>> org.wso2.carbon.user.core.authorization.JDBCAuthorizationManager.clearPermissionTree(JDBCAuthorizationManager.java:873)
>> at
>> org.wso2.carbon.core.internal.permission.update.PermissionUpdater.remove(PermissionUpdater.java:104)
>> at
>> org.wso2.carbon.core.internal.permission.update.PermissionUpdateAxis2ConfigurationContextObserver.terminatingConfigurationContext(PermissionUpdateAxis2ConfigurationContextObserver.java:36)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.doPreConfigContextTermination(TenantAxisUtils.java:525)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.terminateTenantConfigContext(TenantAxisUtils.java:487)
>> at
>> org.wso2.carbon.core.multitenancy.utils.TenantAxisUtils.cleanupTenants(TenantAxisUtils.java:436)
>> at
>> org.wso2.carbon.core.multitenancy.MultitenantServerManager$TenantCleanupTask.run(MultitenantServerManager.java:73)
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> at java.lang.Thread.run(Thread.java:724)
>>
>> Regards,
>> Evanthika
>>
>>
>> On Thu, Sep 26, 2013 at 9:58 PM, Shelan Perera <[email protected]> wrote:
>>
>>> Hi,
>>> I had already added the above fix when we got this error (did not
>>> realize when attaching the patch as I referred 420 accidently. The patch
>>> had resolved the original error reported. So in this case I have applied a
>>> new fix ( improvement) to fix the new issue in
>>> 186489. The root cause for this issue is in their map, queue
>>> implementations.since we are using our dist wrapper map we have fixed for
>>> maps but for queues or other hazelcast native data structure s are prone to
>>> this error. AFAIU This error is harmless too.
>>> ~sent from mobile~
>>> On Sep 26, 2013 4:45 PM, "Anjana Fernando" <[email protected]> wrote:
>>>
>>> Hi Shelan,
>>>
>>> Please check that and verify.
>>>
>>> Cheers,
>>> Anjana.
>>>
>>>
>>> On Thu, Sep 26, 2013 at 4:08 PM, Afkham Azeez <[email protected]> wrote:
>>>
>>>> We can check that by debugging and checking which member got removed
>>>>
>>>>
>>>> On Thu, Sep 26, 2013 at 3:36 PM, Anjana Fernando <[email protected]>wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Is that memberRemoved event coming because, the server is shutting
>>>>> down? .. as in .. telling that, he himself got removed from the cluster?
>>>>> ..
>>>>> which seems a bit strange .. anyways .. if this is the case .. the patch
>>>>> looks OK, and I guess we don't need it for memberAdded right? ..
>>>>>
>>>>> Cheers,
>>>>> Anjana.
>>>>>
>>>>>
>>>>> On Thu, Sep 26, 2013 at 10:00 AM, Shelan Perera <[email protected]>wrote:
>>>>>
>>>>>> Attaching a possible fix.
>>>>>>
>>>>>>
>>>>>> On Thu, Sep 26, 2013 at 9:56 AM, Shelan Perera <[email protected]>wrote:
>>>>>>
>>>>>>> Yes i fixed same in some other places as well. I think it is better
>>>>>>> to check in the
>>>>>>> memberRemoved() and memberAdded() so it will cover most of the
>>>>>>> other scenarios as well.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Sep 26, 2013 at 9:53 AM, Afkham Azeez <[email protected]>wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On Thu, Sep 26, 2013 at 9:49 AM, Ajith Vitharana
>>>>>>>> <[email protected]>wrote:
>>>>>>>>
>>>>>>>>> ntask
>>>>>>>>
>>>>>>>>
>>>>>>>> The ntask ClusterGroupCommunicator.isLeader code has to be
>>>>>>>> changed to first check whether the Hazelcast lifecycle service is
>>>>>>>> active
>>>>>>>> before calling into Hazelcast
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Afkham Azeez*
>>>>>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>>>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>>>>>> * <http://www.apache.org/>**
>>>>>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>>>>>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>>>>>> twitter:
>>>>>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>>>>>> *
>>>>>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>>>>>> *
>>>>>>>> *
>>>>>>>> *Lean . Enterprise . Middleware*
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Shelan Perera*
>>>>>>>
>>>>>>> Senior Software Engineer
>>>>>>> **
>>>>>>> Integration Technology Group
>>>>>>> *WSO2, Inc. : wso2.com*
>>>>>>> lean.enterprise.middleware.
>>>>>>>
>>>>>>> *Blog* : blog.shelan.org
>>>>>>> *Linked-i*n :
>>>>>>> http://www.linkedin.com/pub/shelan-perera/a/194/465
>>>>>>> *Twitter* : https://twitter.com/#!/shelan
>>>>>>>
>>>>>>> *Mobile* : +94 772 604 402
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> *Shelan Perera*
>>>>>>
>>>>>> Senior Software Engineer
>>>>>> **
>>>>>> Integration Technology Group
>>>>>> *WSO2, Inc. : wso2.com*
>>>>>> lean.enterprise.middleware.
>>>>>>
>>>>>> *Blog* : blog.shelan.org
>>>>>> *Linked-i*n :
>>>>>> http://www.linkedin.com/pub/shelan-perera/a/194/465
>>>>>> *Twitter* : https://twitter.com/#!/shelan
>>>>>>
>>>>>> *Mobile* : +94 772 604 402
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> *Anjana Fernando*
>>>>> Technical Lead
>>>>> WSO2 Inc. | http://wso2.com
>>>>> lean . enterprise . middleware
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> *Afkham Azeez*
>>>> Director of Architecture; WSO2, Inc.; http://wso2.com
>>>> Member; Apache Software Foundation; http://www.apache.org/
>>>> * <http://www.apache.org/>**
>>>> email: **[email protected]* <[email protected]>* cell: +94 77 3320919
>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>*
>>>> twitter:
>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
>>>> *
>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez*
>>>> *
>>>> *
>>>> *Lean . Enterprise . Middleware*
>>>>
>>>
>>>
>>>
>>> --
>>> *Anjana Fernando*
>>> Technical Lead
>>> WSO2 Inc. | http://wso2.com
>>> lean . enterprise . middleware
>>>
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>
>
> --
> *Shelan Perera*
>
> Senior Software Engineer
> **
> Integration Technology Group
> *WSO2, Inc. : wso2.com*
> lean.enterprise.middleware.
>
> *Blog* : blog.shelan.org
> *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465
> *Twitter* : https://twitter.com/#!/shelan
>
> *Mobile* : +94 772 604 402
>
>
--
*Afkham Azeez*
Director of Architecture; WSO2, Inc.; http://wso2.com
Member; Apache Software Foundation; http://www.apache.org/
* <http://www.apache.org/>**
email: **[email protected]* <[email protected]>* cell: +94 77 3320919
blog: **http://blog.afkham.org* <http://blog.afkham.org>*
twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez>
*
linked-in: **http://lk.linkedin.com/in/afkhamazeez*
*
*
*Lean . Enterprise . Middleware*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
