You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Freeman Fang (JIRA)" <ji...@apache.org> on 2011/06/20 05:03:47 UTC
[jira] [Created] (CAMEL-4119) specify start-level as 50 for camel
features which ensure camel related bundle can get started before customer
bundles when restart OSGi container
specify start-level as 50 for camel features which ensure camel related bundle can get started before customer bundles when restart OSGi container
--------------------------------------------------------------------------------------------------------------------------------------------------
Key: CAMEL-4119
URL: https://issues.apache.org/jira/browse/CAMEL-4119
Project: Camel
Issue Type: Improvement
Reporter: Freeman Fang
the default start-level for customer bundles is 60, so if we specify start-level as 50 for camel features, we can ensure camel bundles always get started before customer bundles, this can avoid some race condition issues which is caused by customer router started but the necessary camel component not available yet.
More details is from SMX4-744[1]
[1]https://issues.apache.org/jira/browse/SMX4-744
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4119) specify start-level as 50 for camel
features which ensure camel related bundle can get started before customer
bundles when restart OSGi container
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang resolved CAMEL-4119.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.8.0
Applied patch into trunk with thanks to Freeman.
> specify start-level as 50 for camel features which ensure camel related bundle can get started before customer bundles when restart OSGi container
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4119
> URL: https://issues.apache.org/jira/browse/CAMEL-4119
> Project: Camel
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Willem Jiang
> Fix For: 2.8.0
>
> Attachments: CAMEL-4119.patch
>
>
> the default start-level for customer bundles is 60, so if we specify start-level as 50 for camel features, we can ensure camel bundles always get started before customer bundles, this can avoid some race condition issues which is caused by customer router started but the necessary camel component not available yet.
> More details is from SMX4-744[1]
> [1]https://issues.apache.org/jira/browse/SMX4-744
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4119) specify start-level as 50 for camel
features which ensure camel related bundle can get started before customer
bundles when restart OSGi container
Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Willem Jiang reassigned CAMEL-4119:
-----------------------------------
Assignee: Willem Jiang
> specify start-level as 50 for camel features which ensure camel related bundle can get started before customer bundles when restart OSGi container
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4119
> URL: https://issues.apache.org/jira/browse/CAMEL-4119
> Project: Camel
> Issue Type: Improvement
> Reporter: Freeman Fang
> Assignee: Willem Jiang
> Attachments: CAMEL-4119.patch
>
>
> the default start-level for customer bundles is 60, so if we specify start-level as 50 for camel features, we can ensure camel bundles always get started before customer bundles, this can avoid some race condition issues which is caused by customer router started but the necessary camel component not available yet.
> More details is from SMX4-744[1]
> [1]https://issues.apache.org/jira/browse/SMX4-744
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CAMEL-4119) specify start-level as 50 for camel
features which ensure camel related bundle can get started before customer
bundles when restart OSGi container
Posted by "Freeman Fang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CAMEL-4119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang updated CAMEL-4119:
--------------------------------
Attachment: CAMEL-4119.patch
> specify start-level as 50 for camel features which ensure camel related bundle can get started before customer bundles when restart OSGi container
> --------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4119
> URL: https://issues.apache.org/jira/browse/CAMEL-4119
> Project: Camel
> Issue Type: Improvement
> Reporter: Freeman Fang
> Attachments: CAMEL-4119.patch
>
>
> the default start-level for customer bundles is 60, so if we specify start-level as 50 for camel features, we can ensure camel bundles always get started before customer bundles, this can avoid some race condition issues which is caused by customer router started but the necessary camel component not available yet.
> More details is from SMX4-744[1]
> [1]https://issues.apache.org/jira/browse/SMX4-744
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira