Here is the result of the ls -c command.
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
According to the results of the above command, there is some NPE when
activating the service.
Thanks,
Chanaka
On Fri, Feb 27, 2015 at 6:10 PM, Chanaka Fernando <[email protected]> wrote:
> Hi All,
>
> I am getting the below unsatisfied osgi component error in the latest ESB
> 490 M7 pack. We have an integration test to check the unsatisfied osgi
> components list and that test is failing due to this behavior.
>
> 29 Unsatisfied org.wso2.carbon.deployment.synchronizer.XXX
> org.wso2.carbon.deployment.synchronizer(bid=161)
>
>
> when I run the diagnosis on this bundle, I am getting the following result
> osgi> diag 29
> reference:file:../plugins/commons-collections_3.2.0.wso2v1.jar [29]
> No unresolved constraints.
>
> What would be the reason for this behavior?
>
> Here is the location of the pack
>
> https://svn.wso2.org/repos/wso2/people/chanakaf/M7-packs/
>
>
> Thanks,
> Chanaka
>
>
> --
> --
> Chanaka Fernando
> Technical Lead
> WSO2, Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 773337238
> Blog : http://soatutorials.blogspot.com
> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
> Twitter:https://twitter.com/chanakaudaya
> Wordpress:http://chanakaudaya.wordpress.com
>
>
>
>
--
--
Chanaka Fernando
Technical Lead
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
mobile: +94 773337238
Blog : http://soatutorials.blogspot.com
LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0
Twitter:https://twitter.com/chanakaudaya
Wordpress:http://chanakaudaya.wordpress.com
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
