[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-12-11 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: (was: 4.0.8)
   4.0.9

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.9, 4.0.9
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-09-18 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: (was: 4.0.7)
   4.0.8

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.9, 4.0.8
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-08-23 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: (was: 4.0.6)
   4.0.7

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.9, 4.0.7
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-08-07 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: (was: 3.0.8)
   3.0.9

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6, 3.0.9
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-06-06 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: (was: 3.0.7)
   3.0.8

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 4.0.6, 3.0.8
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-03-31 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Component/s: karaf-shell

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
>Assignee: Jean-Baptiste Onofré
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (KARAF-4283) List command reporting incorrect bundle state after service recovery

2016-03-31 Thread JIRA

 [ 
https://issues.apache.org/jira/browse/KARAF-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-4283:

Fix Version/s: 4.0.6
   3.0.7
   4.1.0

> List command reporting incorrect bundle state after service recovery
> 
>
> Key: KARAF-4283
> URL: https://issues.apache.org/jira/browse/KARAF-4283
> Project: Karaf
>  Issue Type: Bug
>  Components: karaf-shell
>Affects Versions: 2.4.3, 3.0.5, 4.0.4
> Environment: Oracle Java 1.7.0_79
> Camel 2.16.1
>Reporter: Quinn Stevenson
> Fix For: 4.1.0, 3.0.7, 4.0.6
>
>
> When an OSGi service used by a Camel route disappears, the list command 
> report bundle containing the Camel route is in the "Waiting" state, which is 
> expected.
> However, when the required OSGi service is restored, the list command 
> continues to report the bundle containing the Camel route is in the "Waiting" 
> state, even though the Camel route recovers and is processing exchanges.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)