Re: [Dev] Unsatisfied osgi component in the ESB 490 M7 pack
Hi All,
Changes added to 'java8support' branch on Git. Should be able to resolve
this with latest packs once its merged. Didn't merged the first request
since both need to be merged on same time.
[1] https://github.com/wso2/carbon-commons/pull/61
[2] https://github.com/wso2/carbon-registry/pull/33
Regards,
Manoj
*Manoj Kumara*
Software Engineer
WSO2 Inc. http://wso2.com/
*lean.enterprise.middleware*
Mobile: +94713448188
On Fri, Feb 27, 2015 at 8:16 PM, Isuru Udana wrote:
> Hi Chanaka,
>
> Please refer to the mail thread
> "Deployment Synchronizer is not getting activated in ESB 4.9.0 pack" dev@.
>
> Thanks.
>
> On Fri, Feb 27, 2015 at 6:34 PM, Chanaka Fernando
> wrote:
>
>> Here is the result of the ls -c command.
>>
>> osgi> ls -c 161
>> Components in bundle org.wso2.carbon.deployment.synchronizer:
>> IDComponent details
>> 29Component[
>> 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
>> 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.
>>>
>>> 29Unsatisfiedorg.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
>>
>>
>>
>>
>
>
> --
> *Isuru Udana*
> Senior
> *Software Engineer*
> WSO2 Inc.; http://wso2.com
> email: isu...@wso2.com cell: +94 77 3791887
> blog: http://mytecheye.blogspot.com/
> twitter: http://twitter.com/isudana
>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unsatisfied osgi component in the ESB 490 M7 pack
Hi Chanaka,
Please refer to the mail thread
"Deployment Synchronizer is not getting activated in ESB 4.9.0 pack" dev@.
Thanks.
On Fri, Feb 27, 2015 at 6:34 PM, Chanaka Fernando wrote:
> Here is the result of the ls -c command.
>
> osgi> ls -c 161
> Components in bundle org.wso2.carbon.deployment.synchronizer:
> IDComponent details
> 29Component[
> 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
> 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.
>>
>> 29Unsatisfiedorg.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
>
>
>
>
--
*Isuru Udana*
Senior
*Software Engineer*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Unsatisfied osgi component in the ESB 490 M7 pack
Here is the result of the ls -c command.
osgi> ls -c 161
Components in bundle org.wso2.carbon.deployment.synchronizer:
IDComponent details
29Component[
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 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.
>
> 29Unsatisfiedorg.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
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Unsatisfied osgi component in the ESB 490 M7 pack
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. 29Unsatisfiedorg.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 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
