hi Eranda, We already fixed this issue. Please take a svn update in carbon core.
Thanks, KasunG On Tuesday, August 20, 2013, Eranda Sooriyabandara <[email protected]> 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 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 to set the domain from 1 to -1234 > java.lang.IllegalStateException: Trying to set the domain from 1 to -1234 > at org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantId(CarbonContextDataHolder.java:1552) > at org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:208) > at org.wso2.carbon.context.PrivilegedCarbonContext.setTenantId(PrivilegedCarbonContext.java:197) > at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:62) > at org.wso2.carbon.core.CarbonAxisConfigurator.runDeployment(CarbonAxisConfigurator.java:419) > at org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest.doDeployment(SynchronizeRepositoryRequest.java:86) > at org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest.execute(SynchronizeRepositoryRequest.java:74) > at org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener.onMessage(HazelcastClusterMessageListener.java:54) > at com.hazelcast.impl.ListenerManager.callListener(ListenerManager.java:419) > at com.hazelcast.impl.ListenerManager.callListeners(ListenerManager.java:334) > at com.hazelcast.impl.BaseManager$2.run(BaseManager.java:1392) > at com.hazelcast.impl.executor.ParallelExecutorService$ParallelExecutorImpl$ExecutionSegment.run(ParallelExecutorService.java:212) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > at com.hazelcast.impl.ExecutorThreadFactory$1.run(ExecutorThreadFactory.java:45) > [2013-08-20 00:32:31,223] ERROR {org.wso2.carbon.context.internal.CarbonContextDataHolder} - Trying to set the domain from wso2.com to carbon.super > java.lang.IllegalStateException: Trying to set the domain from wso2.comto > carbon.super > at org.wso2.carbon.context.internal.CarbonContextDataHolder.setTenantDomain(CarbonContextDataHolder.java:1601) > at org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:245) > at org.wso2.carbon.context.PrivilegedCarbonContext.setTenantDomain(PrivilegedCarbonContext.java:234) > at org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.runAxisDeployment(CarbonDeploymentSchedulerTask.java:63) > at org.wso2.carbon.core.CarbonAxisConfigurator.runDeployment(CarbonAxisConfigurator.java:419) > at org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest.doDeployment(SynchronizeRepositoryRequest.java:86) > at org.wso2.carbon.core.deployment.SynchronizeRepositoryRequest.execute(SynchronizeRepositoryRequest.java:74) > at org.wso2.carbon.core.clustering.hazelcast.HazelcastClusterMessageListener.onMessage(HazelcastClusterMessageListener.java:54) > at com.hazelcast.impl.ListenerManager.callListener(ListenerManager.java:419) > at com.hazelcast.impl.ListenerManager.callListeners(ListenerManager.java:334) > at com.hazelcast.impl.BaseManager$2.run(BaseManager.java:1392) > at com.hazelcast.impl.executor.ParallelExecutorService$ParallelExecutorImpl$ExecutionSegment.run(ParallelExecutorService.java:212) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > at com.hazelcast.impl.ExecutorThreadFactory$1.run(ExecutorThreadFactory.java:45) > > thanks > Eranda > > On Mon, Aug 19, 2013 at 10:14 PM, Eranda Sooriyabandara <[email protected]> wrote: > > 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 <[email protected]> wrote: > > 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 <[email protected]> wrote: > > 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} - Sent [SynchronizeRepositoryRequest{tenantId=1, tenantDomain='wso2.com', messageId=f3d0afa3-1485-4a63-8ad4-6b8282f80a1d}] > thanks > Eranda > > > > On Mon, Aug 19, 2013 at 9:15 PM, Pradeep Fernando <[email protected]> wrote: > > Sorry I didn't get you.... > > --Pradeep > sent from my phone > > On Aug 19, 2013 9:01 PM, "Eranda Sooriyabandara" <[email protected]> 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, Aug 19, 2013 at 12:24 AM, Pradeep Fernando <[email protected]> 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 <[email protected]> wrote: > > 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 to the execute() method. Hence during the doDeployment() method call, the super-tenant CarbonAxisConfigurator get picked instead of TenantAxisConfigurator. > > thought of handling the multi-tenant aspects after message being passed to the receiving side. (af -- ~~--~~ Sending this mail via my phone. Do excuse any typo or short replies
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
