directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ivo Leitão (JIRA) <j...@apache.org>
Subject [jira] [Commented] (DIRAPI-273) api-ldap-net-mina bundle remains in STARTING mode
Date Mon, 07 Mar 2016 23:10:40 GMT

    [ https://issues.apache.org/jira/browse/DIRAPI-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183956#comment-15183956
] 

Ivo Leitão commented on DIRAPI-273:
-----------------------------------

I find this quite puzzling also. I lingered with this problem at least one day before finding
a post somewhere in the net saying that removing the Lazy directive could solve the problem
and fortunately it did (it was related with other bundle). I even change the loading order
of the bundles a couple of times before giving up and tried to find alternate solutions. Unfortunately
with that directive it doesn't work in felix at least, i don't know about other osgi frameworks


> api-ldap-net-mina bundle remains in STARTING mode
> -------------------------------------------------
>
>                 Key: DIRAPI-273
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-273
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0.0-M33
>         Environment: Linux; Felix
>            Reporter: Ivo Leitão
>              Labels: Felix, OSGI
>
> After deploying the api-ldap-net-mina bundle in an OSGI environment (in my case the Felix
container) the bundle remains in STARTING mode til an explicit stop and start via a gogo shell
command or via Felix webconsole. I've found that removing Bundle-ActivationPolicy: lazy in
the MANIFEST.MF resolves this issues. From what I've investigated is not a good pratice to
use Bundle-ActivationPolicy at least in a Felix environment (I know that is more common in
Equinox). It's possibile to remove this without affecting other OSGI platforms.
> What I can say is that it does not work OOB with this directive.



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

Mime
View raw message