hi Eranda,
We already fixed this issue. Please take a svn update in carbon core.
Thanks,
KasunG
On Tuesday, August 20, 2013, Eranda Sooriyabandara wrote:
> Hi Again,
> As I discussed with KasunG, I tried wka and it worked for super tenant
but when it tries for a different tenant following messa
Hi Again,
As I discussed with KasunG, I tried wka and it worked for super tenant but
when it tries for a different tenant following message appears. I'll try to
investigate more on this tomorrow.
[2013-08-20 00:32:31,222] ERROR
{org.wso2.carbon.context.internal.CarbonContextDataHolder} - Trying t
Hi Pradeep,
This message is not called in the worker node thought the manager sends the
cluster message.
thanks
Eranda
On Mon, Aug 19, 2013 at 9:53 PM, Pradeep Fernando wrote:
> then,
>
> .HazelcastClusterMessageListener.onMessage()
>
> method should get called in the worker node. If not, some
then,
.HazelcastClusterMessageListener.onMessage()
method should get called in the worker node. If not, something wrong with
your cluster setup.
thanks,
--Pradeep
On Mon, Aug 19, 2013 at 9:25 PM, Eranda Sooriyabandara wrote:
> Hi Pradeep,
> Following log appears on the manager node. But worke
Hi Pradeep,
Following log appears on the manager node. But worker node not sync the
artifact from the registry, even there is no ack for the cluster message
reception. Any idea what is happening?
[2013-08-19 21:22:02,974] INFO
{org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} - Sen
Sorry I didn't get you
--Pradeep
sent from my phone
On Aug 19, 2013 9:01 PM, "Eranda Sooriyabandara" wrote:
> Hi Pradeep,
> In the latest pack I see the workers not sync up with the cluster message
> for the registry based dep-sync. But it works for tenants.
>
> thanks
> Eranda
>
>
> On Mon,
Hi Pradeep,
In the latest pack I see the workers not sync up with the cluster message
for the registry based dep-sync. But it works for tenants.
thanks
Eranda
On Mon, Aug 19, 2013 at 12:24 AM, Pradeep Fernando wrote:
> @QA,
>
> Please patch the QA setup with following jar and proceed with tena
Noted.
- Evanthika
On Mon, Aug 19, 2013 at 12:24 AM, Pradeep Fernando wrote:
> @QA,
>
> Please patch the QA setup with following jar and proceed with tenant level
> depsync.
>
> thanks,
> --Pradeep
>
>
> On Mon, Aug 19, 2013 at 12:18 AM, Pradeep Fernando wrote:
>
>> Hi,
>>
>> Kasun and me look
Hi,
Kasun and me looked in to the issue.
The issue has surfaced due to Erandas commit to,
SynchronizeRepositoryRequest#execute() method - setting tenant info to CC.
However, it is the correct approach IMHO.
In the current implementation the cluster message listener always passes
mainConfigContext
i will have a look..
On Tue, Aug 13, 2013 at 3:57 PM, Kasun Gajasinghe wrote:
> The second issue seems to be because of a local issue when configuring the
> wka clustering. I'm trying to re-produce the first issue.
>
> Thanks,
> KasunG
>
>
> On Tue, Aug 13, 2013 at 3:33 PM, Kasun Gajasinghe wr
The second issue seems to be because of a local issue when configuring the
wka clustering. I'm trying to re-produce the first issue.
Thanks,
KasunG
On Tue, Aug 13, 2013 at 3:33 PM, Kasun Gajasinghe wrote:
> Hi,
>
> Tenant Deployment Synchronizing is broken in latest packs. This issue is
> of t
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
Conf
12 matches
Mail list logo
