Hi Aruna,

Thanks very much it works!

I just wondering why my freshly built product-apim [1] is not detecting
correct version of carbon-commons. There is a md5sum mismatch between,
dev-carbon-common [2] org.wso2.carbon.deployment.synchronizer and my
product's  org.wso2.carbon.deployment.synchronizer jar. That means, we have
a sync mismatch between wso2-dev/carbon-commons and /carbon-commons ?

Regards
Roshan.


[1] https://github.com/wso2/product-apim

[2] https://github.com/wso2-dev/carbon-commons


On Fri, Aug 15, 2014 at 11:19 AM, Aruna Karunarathna <ar...@wso2.com> wrote:

> Hi Roshan,
>
> Please try build [1]  and copy org.wso2.carbon.deployment.synchronizer to
> patches folder.
>
> [1]. https://github.com/wso2-dev/carbon-commons
>
> Regards,
> Aruna
>
>
> On Thu, Aug 14, 2014 at 6:24 PM, Roshan Wijesena <ros...@wso2.com> wrote:
>
>> Hi Devs,
>>
>> I built product apim using GIT. Even-though product built successfully,
>> when I am  starting  product
>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException is
>> throwing periodically .
>>
>> I have disabled "registry based" dep sync in my carbon.xml.
>>
>> exception is.
>>
>> [2014-08-14 18:15:58,089] ERROR - CarbonDeploymentSchedulerTask
>> Deployment synchronization commit for tenant -1234 failed
>> java.lang.RuntimeException:
>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
>> Repository found for type registry
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:116)
>>  at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.deploymentSyncCommit(CarbonDeploymentSchedulerTask.java:207)
>> at
>> org.wso2.carbon.core.deployment.CarbonDeploymentSchedulerTask.run(CarbonDeploymentSchedulerTask.java:128)
>>  at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>>  at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>>  at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>  at java.lang.Thread.run(Thread.java:745)
>> Caused by:
>> org.wso2.carbon.deployment.synchronizer.DeploymentSynchronizerException: No
>> Repository found for type registry
>>  at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getDefaultDeploymentSyncConfiguration(CarbonRepositoryUtils.java:209)
>> at
>> org.wso2.carbon.deployment.synchronizer.internal.repository.CarbonRepositoryUtils.getActiveSynchronizerConfiguration(CarbonRepositoryUtils.java:113)
>>  at
>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerServiceImpl.commit(DeploymentSynchronizerServiceImpl.java:96)
>> ... 9 more
>>
>>
>> Similer issue has been reported [1].
>>
>> https://wso2.org/jira/browse/CARBON-14067
>>
>> what could be the cause?
>>
>> Thanks.
>>
>> --
>> Roshan Wijesena.
>> Senior Software Engineer-WSO2 Inc.
>> Mobile: *+94752126789*
>> Email: ros...@wso2.com
>> *WSO2, Inc. :** wso2.com <http://wso2.com/>*
>> lean.enterprise.middleware.
>>
>> _______________________________________________
>> Dev mailing list
>> Dev@wso2.org
>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>
>>
>
>
> --
>
> * Aruna Sujith Karunarathna* | Software Engineer
> WSO2, Inc | lean. enterprise. middleware.
> #20, Palm Grove, Colombo 03, Sri Lanka
> Mobile: +94 71 9040362 | Work: +94 112145345
> Email: ar...@wso2.com | Web: www.wso2.com
>
>



-- 
Roshan Wijesena.
Senior Software Engineer-WSO2 Inc.
Mobile: *+94752126789*
Email: ros...@wso2.com
*WSO2, Inc. :** wso2.com <http://wso2.com/>*
lean.enterprise.middleware.
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to