Cancel that!
Looks like Jetty spins a thread to complete it's startup - so in
framework terms it is started, but of course it's internal startup
hasn't completed.
We get a service registration race condition and deadlock due to this -
although we still use the old servicebinder code, so I doubt it affects
anyone else. Not sure yet if it's something fixable in servicebinder or
if we need to alter our startup dependencies.
If I find anything in servicebinder I'll raise a JIRA and fix it.
-- Rob
On 20/10/2011 9:45 AM, Rob Walker wrote:
Warning - despite working on OSGi and Felix for years, I may be about
to sound like total noob!
Updating to latest Felix and bundles, we hit an odd startup freeze
that we never had before. Still digging for the cause.
I'm about to start digging in Start Levels code - but maybe someone
knows the answer to 1 question that's coming to mind.
We seem to be getting a scenario where our HTTP Service (which is at a
start level of 1) is getting blocked by bundles at a higher start
level. It's still trying to register it's service but I can also see
bundles with higher start levels already running.
I did a double take when I saw this in the stack traces. I thought a
framework would only move to the next start level once all bundles in
the current start level had actually completed their startup. But
maybe that's a misconception on my part ? Perhaps the API contract is
only that start has been invoked on all bundles in a start level
before it advances
-- Rob
Ascert - Taking systems to the Edge
[email protected]
+44 (0)20 7488 3470
www.ascert.com
--
Ascert - Taking systems to the Edge
[email protected]
+44 (0)20 7488 3470
www.ascert.com
