You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@celix.apache.org by Woojoong Kim <wo...@gmail.com> on 2019/12/09 21:45:18 UTC
Error when stopping resolved bundle
Hi guys,
I am trying to use Celix.
Just I want to know how to fix an unexpected error when stopping resolved bundles.
Normally, we will not push the command stop a resolved bundle but sometimes we type wrong command…
I think it is important for exception handling.
Is this error can be resolved or do you have any idea to solve it?
=== test result ===
-> lb
ID State Name
0 Active framework
1 Active apache_celix_shell
2 Active apache_celix_shell_tui
3 Active apache_celix_dm_shell
4 Active apache_celix_remote_shell
5 Active apache_celix_log_service
6 Active GWCore
7 Resolved SBBundle
-> stop 7
-> lb
ID State Name
0 Active framework
1 Active apache_celix_shell
2 Active apache_celix_shell_tui
3 Active apache_celix_dm_shell
4 Active apache_celix_remote_shell
5 Active apache_celix_log_service
6 Active GWCore
7 Stopping SBBundle
-> start 7
ERROR: Illegal state [70006]: "Failed to get bundle lock”
at framework_acquireBundleLock(/mnt/extra/workspace/xranc/common/celix/framework/private/src/framework.c:2001)
ERROR: Illegal state [70006]: Could not start bundle: SBBundle [7]
at fw_startBundle(/mnt/extra/workspace/xranc/common/celix/framework/private/src/framework.c:766)
ERROR: Illegal state [70006]: "Failed to start bundle”
at bundle_startWithOptions(/mnt/extra/workspace/xranc/common/celix/framework/private/src/bundle.c:285)
Thanks,
Woojoong Kim.
Re: Error when stopping resolved bundle
Posted by Pepijn Noltes <pe...@gmail.com>.
Hi,
This should not happen and is a bug.
I created an issue for this:
https://github.com/apache/celix/issues/129
Greetings,
Pepijn
On Mon, Dec 9, 2019 at 10:45 PM Woojoong Kim <wo...@gmail.com> wrote:
>
> Hi guys,
>
> I am trying to use Celix.
>
> Just I want to know how to fix an unexpected error when stopping resolved bundles.
>
> Normally, we will not push the command stop a resolved bundle but sometimes we type wrong command…
>
> I think it is important for exception handling.
>
> Is this error can be resolved or do you have any idea to solve it?
>
> === test result ===
>
> -> lb
> ID State Name
> 0 Active framework
> 1 Active apache_celix_shell
> 2 Active apache_celix_shell_tui
> 3 Active apache_celix_dm_shell
> 4 Active apache_celix_remote_shell
> 5 Active apache_celix_log_service
> 6 Active GWCore
> 7 Resolved SBBundle
> -> stop 7
> -> lb
> ID State Name
> 0 Active framework
> 1 Active apache_celix_shell
> 2 Active apache_celix_shell_tui
> 3 Active apache_celix_dm_shell
> 4 Active apache_celix_remote_shell
> 5 Active apache_celix_log_service
> 6 Active GWCore
> 7 Stopping SBBundle
> -> start 7
> ERROR: Illegal state [70006]: "Failed to get bundle lock”
> at framework_acquireBundleLock(/mnt/extra/workspace/xranc/common/celix/framework/private/src/framework.c:2001)
> ERROR: Illegal state [70006]: Could not start bundle: SBBundle [7]
> at fw_startBundle(/mnt/extra/workspace/xranc/common/celix/framework/private/src/framework.c:766)
> ERROR: Illegal state [70006]: "Failed to start bundle”
> at bundle_startWithOptions(/mnt/extra/workspace/xranc/common/celix/framework/private/src/bundle.c:285)
>
> Thanks,
> Woojoong Kim.