[ https://issues.apache.org/jira/browse/FELIX-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683336#comment-13683336 ]
metatech commented on FELIX-1717: --------------------------------- I still have the problem with Karaf 2.2.4. The Spring status stays empty, until the first invocation of "osgi:list" in the Karaf shell, after which the listener gets registered, but the Spring status stays empty until the next bundle restart. A more reliable solution to this problem would be to register the listeners in a bundle activator in the Karaf Shell OSGi bundle, so that all events are listened from the early start of the server. > osgi:list column for spring is sometimes filled and sometimes not > ----------------------------------------------------------------- > > Key: FELIX-1717 > URL: https://issues.apache.org/jira/browse/FELIX-1717 > Project: Felix > Issue Type: Bug > Components: Karaf > Affects Versions: karaf-1.0.0 > Reporter: Lars Heinemann > Assignee: Guillaume Nodet > Fix For: karaf-1.2.0 > > > see IRC discussion: > [09:24] <lhein> gnodet: did you recognize that the osgi:list Spring column is > sometimes filled with lots of "started" and most times it's simply empty? > [09:25] <lhein> most is maybe not correct...it seems to be a random effect > [09:57] <gnodet> lhein: that's a problem with spring > [09:57] <gnodet> mostly when you add a spring listener, you don't know about > previous events > [09:58] <gnodet> so if the listener was registered too late, it will miss > some events > [09:58] <gnodet> but we only register the listener when using osgi:list > command, so you may want to raise a bug so that it's done earlier if possible -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira