Hi,
Tenant Deployment Synchronizing is broken in latest packs. This issue is of
two fold.
1. Tenants fail to update their svn repository when a cluster message is
received. [1] The actual issue is that although the cluster message,
SynchronizeRepositoryRequest, has the correct tenant id, the
ConfigurationContext object passed by worker node is the CC of super
tenant. The cluster message receiver node is supposed to pass the correct
ConfigurationContext to SynchronizeRepositoryRequest#execute method. It
seems like the HazelcastClusteringAgent is not tenant aware.
2. Manager nodes fails to send cluster message - The reason is
that ClusteringAgent that is used to send the cluster message is null.
Noticed this in local setup even for super-tenant. Seems to be intermittent
since this is apparently working in the 9thAug QA setup.
CarbonDeploymentSchedulerTask#sendRepositorySyncMessage
CarbonCoreDataHolder.getInstance().getMainServerConfigContext().
getAxisConfiguration().getClusteringAgent(); ==>
null
https://wso2.org/jira/browse/CARBON-14346
Thanks,
KasunG
--
*Kasun Gajasinghe*
Software Engineer;
Development Technologies Team, WSO2 Inc.; http://wso2.com
,
*email: **kasung AT spamfree wso2.com
** cell: **+94 (77) 678-0813*
*linked-in: *http://lk.linkedin.com/in/gajasinghe
*
*
*blog: **http://kasunbg.org* <http://kasunbg.org>
*
twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
*
*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
