Hi All,
I have configured HA cluster for Identity Cloud, with two Identity Server
(IS) nodes and two Gateway (GW) nodes.
SVN based deployment synchronization is enabled in IS cluster to sync
secondary user stores and in GW cluster to sync synapse configurations.
Soon after the deployment up the
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
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
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,
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,
Hi Shelan,
Please check that and verify.
Cheers,
Anjana.
On Thu, Sep 26, 2013 at 4:08 PM, Afkham Azeez az...@wso2.com wrote:
We can check that by debugging and checking which member got removed
On Thu, Sep 26, 2013 at 3:36 PM, Anjana Fernando anj...@wso2.com wrote:
Hi,
Is that
Hi All,
I'm getting following error in yesterday packs. This is happened while shut
down the server.
[2013-09-26 09:43:52,641] INFO {org.wso2.carbon.core.ServerManagement} -
Waiting for request service completion...
Exception in thread hz.wso2.governance.domain.instance.cached.thread-6
On Thu, Sep 26, 2013 at 9:49 AM, Ajith Vitharana aji...@wso2.com 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,
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 az...@wso2.com wrote:
On Thu, Sep 26, 2013 at 9:49 AM, Ajith
Attaching a possible fix.
On Thu, Sep 26, 2013 at 9:56 AM, Shelan Perera she...@wso2.com 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,
10 matches
Mail list logo
