On Tue, Jun 12, 2012 at 6:32 PM, Nuwan Dias <[email protected]> wrote:

> Hi Kasun,
>
> Your change wasn't committed to trunk right? (I am not able to do an svn
> update right now since I am in a network which requires basic auth). If so,
> could you check by reverting the change made on the
> DeploymentSynchronizerServiceImpl class?
>
>
I'm sorry, I misunderstood your previous reply. That modification was still
in my working copy. Thanks for pointing that out.

BTW, I was under the impression that you will be working on *that* issue.
Is it?

Thanks,
--KasunG



> Thanks,
> NuwanD.
>
>
> On Tue, Jun 12, 2012 at 10:15 PM, Kasun Gajasinghe <[email protected]>wrote:
>
>>
>>
>> On Tue, Jun 12, 2012 at 5:49 AM, Nuwan Dias <[email protected]> wrote:
>>
>>> Hi Kasun,
>>>
>>> Does your build contain the modifications you made for the patch
>>> attached on the mail thread titled  'CHECKOUT_BEFORE_CHECK_IN error in
>>> Deployment Synchronizer Write Only mode' ?
>>
>>
>> Yes Nuwan, this was built yesterday. The changes were for depsync
>> component, right?
>>
>> Thanks,
>> --KasunG
>>
>>
>>>
>>> Thanks,
>>> NuwanD.
>>>
>>>
>>> On Tue, Jun 12, 2012 at 1:31 AM, Kasun Gajasinghe <[email protected]>wrote:
>>>
>>>>
>>>> This error appear periodically, but when I enabled the deployment
>>>> synchronizer via UI, the error printing stopped.
>>>>
>>>>
>>>> On Mon, Jun 11, 2012 at 3:54 PM, Kasun Gajasinghe <[email protected]>wrote:
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> Got this error when I was trying to build AppServer pack today. Is
>>>>> this my build issue or is there remaining work to be done on renaming the
>>>>> supertenant id for AppServer?
>>>>>
>>>>>
>>>>> [2012-06-11 15:37:43,257] ERROR
>>>>> {org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask} -
>>>>>  Deployment synchronization update for tenant -1234 failed
>>>>> java.lang.RuntimeException:
>>>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
>>>>> repository synchronizer has not been engaged for the file path:
>>>>> /home/kasun/wso2/trunk/platform/products/as/modules/distribution/wso2as-5.0-SNAPSHOT/repository/deployment/server/
>>>>>  at
>>>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:78)
>>>>> at
>>>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncUpdate(CarbonDeploymentSchedulerTask.java:103)
>>>>>  at
>>>>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:74)
>>>>> at
>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
>>>>>  at
>>>>> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
>>>>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
>>>>>  at
>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
>>>>> at
>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
>>>>>  at
>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
>>>>> 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)
>>>>> Caused by:
>>>>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: A
>>>>> repository synchronizer has not been engaged for the file path:
>>>>> /home/kasun/wso2/trunk/platform/products/as/modules/distribution/wso2as-5.0-SNAPSHOT/repository/deployment/server/
>>>>>  at
>>>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.getSynchronizer(DeploymentSynchronizerServiceImpl.java:125)
>>>>>  at
>>>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.update(DeploymentSynchronizerServiceImpl.java:61)
>>>>> ... 11 more
>>>>>
>>>>>
>>>>> 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://blog.kasunbg.org* <http://blog.kasunbg.org>*
>>>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>>>>> *
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> *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://blog.kasunbg.org* <http://blog.kasunbg.org>*
>>>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>>>> *
>>>>
>>>>
>>>
>>>
>>> --
>>> Nuwan Dias
>>>
>>> Software Engineer - WSO2, Inc.
>>> Integration Technologies Team
>>> email : [email protected]
>>> Phone : +94 777 775 729
>>>
>>>
>>
>>
>> --
>> *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://blog.kasunbg.org* <http://blog.kasunbg.org>*
>> twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
>> *
>>
>>
>
>
> --
> Nuwan Dias
>
> Software Engineer - WSO2, Inc.
> Integration Technologies Team
> email : [email protected]
> Phone : +94 777 775 729
>
>


-- 
*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://blog.kasunbg.org* <http://blog.kasunbg.org>*
twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>*
*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to