Hi Isuru, Thanks for reporting this. I have merged the fix related to this on carbon-commons master branch. Will update the thread after testing both svn based and registry based depsync.
Regards, Manoj *Manoj Kumara* Software Engineer WSO2 Inc. http://wso2.com/ *lean.enterprise.middleware* Mobile: +94713448188 On Sun, Feb 22, 2015 at 10:43 PM, Isuru Udana <[email protected]> wrote: > Hi Manoj, > > Thanks for the response. > > Problem is > with org.wso2.carbon.deployment.synchronizer.util.ServiceReferenceHolder > [1]. > > > public static RegistryService getRegistryService() { > return registryService; > } > > Here registryService is not getting set from anywhere but it has a usage > in CarbonRepositoryUtils. > > > [1] > https://github.com/wso2/carbon-commons/blob/4.3.5/components/deployment-synchronizer/org.wso2.carbon.deployment.synchronizer/src/main/java/org/wso2/carbon/deployment/synchronizer/util/ServiceReferenceHolder.java > > On Sun, Feb 22, 2015 at 10:17 PM, Aruna Karunarathna <[email protected]> > wrote: > >> Hi Sameera, >> >> I think we need to release the svn-kit updated libs before the ESB final >> release, to support with svn newer server versions. >> >> Regards, >> Aruna >> >> On Sun, Feb 22, 2015 at 9:33 PM, Manoj Kumara <[email protected]> wrote: >> >>> Hi Isuru, >>> >>> This was found during testing and fixed with pull request [1]. Will try >>> to check this with ESB server tomorrow. >>> >>> [1] https://github.com/wso2/carbon-commons/pull/52 >>> >>> Regards, >>> Manoj >>> >>> >>> *Manoj Kumara* >>> Software Engineer >>> WSO2 Inc. http://wso2.com/ >>> *lean.enterprise.middleware* >>> Mobile: +94713448188 >>> >>> On Sun, Feb 22, 2015 at 4:36 PM, Isuru Udana <[email protected]> wrote: >>> >>>> Hi Kernel Team, >>>> >>>> Deployment synchronizer service component is not getting activated >>>> properly in latest ESB build with carbon-commons:4.3.5. >>>> Following is what we are getting on the osgi console. >>>> >>>> >>>> 29 Unsatisfied org.wso2.carbon.deployment.synchronizer.XXX >>>> org.wso2.carbon.deployment.synchronizer(bid=161) >>>> >>>> osgi> ls -c 161 >>>> Components in bundle org.wso2.carbon.deployment.synchronizer: >>>> ID Component details >>>> 29 Component[ >>>> name = org.wso2.carbon.deployment.synchronizer.XXX >>>> factory = null >>>> autoenable = true >>>> immediate = true >>>> implementation = >>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent >>>> state = Unsatisfied >>>> properties = {service.pid=org.wso2.carbon.deployment.synchronizer.XXX} >>>> serviceFactory = false >>>> serviceInterface = null >>>> references = { >>>> Reference[name = configuration.context.service, interface = >>>> org.wso2.carbon.utils.ConfigurationContextService, policy = dynamic, >>>> cardinality = 1..1, target = null, bind = setConfigurationContextService, >>>> unbind = unsetConfigurationContextService] >>>> Reference[name = repository.reference.service, interface = >>>> org.wso2.carbon.deployment.synchronizer.ArtifactRepository, policy = >>>> dynamic, cardinality = 0..n, target = null, bind = addArtifactRepository, >>>> unbind = removeArtifactRepository] >>>> } >>>> located in bundle = org.wso2.carbon.deployment.synchronizer_4.3.5 [161] >>>> ] >>>> Dynamic information : >>>> The component is satisfied >>>> All component references are satisfied >>>> Component configurations : >>>> Configuration properties: >>>> service.pid = org.wso2.carbon.deployment.synchronizer.XXX >>>> component.name = org.wso2.carbon.deployment.synchronizer.XXX >>>> component.id = 28 >>>> Instances: >>>> No instances were created because: Can not activate instance of >>>> component >>>> org.wso2.carbon.deployment.synchronizer.internal.DeploymentSynchronizerComponent. >>>> The activation throws: java.lang.NullPointerException >>>> >>>> >>>> I debug deployment synchronizer component and found out that from [1] >>>> registry service is removed and we haven't cleaned up the usages of >>>> registry service properly, hence we are getting a NPE upon activation. >>>> >>>> We need to get this fixed as soon as possible. >>>> >>>> >>>> [1] removing registry based DepSync components from carbon-commons >>>> >>>> https://github.com/wso2/carbon-commons/compare/7acb524b6389fabdf2264eb95c5b55b161546094...ffa87d07ad4d28247e4e4c8bdedc6a57874815f8 >>>> >>>> Thank you. >>>> >>>> >>>> -- >>>> *Isuru Udana* >>>> Senior >>>> *Software Engineer* >>>> WSO2 Inc.; http://wso2.com >>>> email: [email protected] cell: +94 77 3791887 >>>> blog: http://mytecheye.blogspot.com/ >>>> twitter: http://twitter.com/isudana >>>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> [email protected] >>> 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: [email protected] | Web: www.wso2.com >> >> > > > > -- > *Isuru Udana* > Senior > *Software Engineer* > WSO2 Inc.; http://wso2.com > email: [email protected] cell: +94 77 3791887 > blog: http://mytecheye.blogspot.com/ > twitter: http://twitter.com/isudana >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
