The only thing the start level guarantees is that the framework has called BundleActivator.start() on each bundle in a given start level and returned from it before advancing to the next start level. Felix doesn't use multiple threads within a start level, but I think the spec allows it. It is possible that the bundles themselves spawn off new threads in their activators to finish their initialization. If that is the case, there is nothing OSGi can do to help here.

-> richard

On 3/25/09 12:24 PM, Skinner Chad wrote:
Yes, The easybeans agent bundle in felix.auto.start.2 is responsible for starting the other bundles in the correct order. If I remove my bundles from the application and the restart felix the JNDI lookup errors go away. One question, is the startup performed on a single thread? Is it possible that all of these are started in multiple threads and the EZB bundles have not started completely before my bundles are started? If this is the case how to I prevent my bundles from starting before everything in the EZB bundle is started?




On Mar 25, 2009, at 1:29 PM, Karl Pauls wrote:

Are the easybeans bundles started at all? From the below properties
alone that isn't the case i think. So something else must be going on
as well.

regards,

Karl

On Wed, Mar 25, 2009 at 7:01 PM, Skinner Chad <[email protected]> wrote:
Sorry I messed up my description of how I have this configured. The correct
information is:

felix.auto.start.1 = <core osgi and felix bundles>
felix.auto.install.2 = <easybean bundles>
felix.auto.start.2 = <ow2 logging bundle> <easybeans agent bundle>
felix.auto.install.3 = <fileinstall bundle>


On Mar 25, 2009, at 9:51 AM, Skinner Chad wrote:

Can anyone tell me how the start levels affect the automatic start of
bundles?

I have the bundles setup as the following:

felix.auto.install.1 = <core osgi and felix bundles>
felix.auto.install.2 = <easybean bundles>
felix.auto.install.3 = <fileinstall bundle>
felix.startlevel.bundle = 4
org.osgi.framework.startlevel=4

The firsttime I start felix (clean cache) this appears to load in the
proper order and if I drop my custom bundles into the directory for file install they are loaded as well. Every subsequent time I start felix it
appears that my custom bundles in startlevel4 are being started before
easybeans and I get some JNDI errors.

Should the bundles not start in order (1, 2, 3, 4 ....)?

Thanks,
-- Chad
THIS EMAIL MESSAGE IS FROM THE TOPEKA PUBLIC SCHOOLS USD501 IN TOPEKA,
KANSAS AND IS INTENDED ONLY FOR THE ADDRESSEE. THE INFORMATION CONTAINED HEREIN MAY BE CONFIDENTIAL. IF THIS EMAIL HAS MISTAKENLY BEEN SENT TO YOU,
PLEASE DELETE IT AFTER NOTIFYING US OF THE ERROR BY REPLY EMAIL OR BY
CALLING 785-295-3000.  UNAUTHORIZED FORWARDING, PRINTING, COPYING,
DISTRIBUTING OR USING THE INFORMATION IN THIS EMAIL MESSAGE IS STRICTLY
PROHIBITED AND MAY BE UNLAWFUL.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


THIS EMAIL MESSAGE IS FROM THE TOPEKA PUBLIC SCHOOLS USD501 IN TOPEKA,
KANSAS AND IS INTENDED ONLY FOR THE ADDRESSEE. THE INFORMATION CONTAINED HEREIN MAY BE CONFIDENTIAL. IF THIS EMAIL HAS MISTAKENLY BEEN SENT TO YOU,
PLEASE DELETE IT AFTER NOTIFYING US OF THE ERROR BY REPLY EMAIL OR BY
CALLING 785-295-3000.  UNAUTHORIZED FORWARDING, PRINTING, COPYING,
DISTRIBUTING OR USING THE INFORMATION IN THIS EMAIL MESSAGE IS STRICTLY
PROHIBITED AND MAY BE UNLAWFUL.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





--
Karl Pauls
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


THIS EMAIL MESSAGE IS FROM THE TOPEKA PUBLIC SCHOOLS USD501 IN TOPEKA, KANSAS AND IS INTENDED ONLY FOR THE ADDRESSEE. THE INFORMATION CONTAINED HEREIN MAY BE CONFIDENTIAL. IF THIS EMAIL HAS MISTAKENLY BEEN SENT TO YOU, PLEASE DELETE IT AFTER NOTIFYING US OF THE ERROR BY REPLY EMAIL OR BY CALLING 785-295-3000. UNAUTHORIZED FORWARDING, PRINTING, COPYING, DISTRIBUTING OR USING THE INFORMATION IN THIS EMAIL MESSAGE IS STRICTLY PROHIBITED AND MAY BE UNLAWFUL.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to