[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[equinox-dev] [DS] Unexplained Component Deactivation
- From: Andrew Teirney <andrew@xxxxxxxxxxx>
- Date: Thu, 4 Jun 2009 23:03:36 +1200
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type:content-transfer-encoding; b=ScHp6SZwcK5ECiiBsHcBwPaTLkzV+9jGZxfEVUBY4zUkmxjkj0iO1rDXdQ5nCQYQiL iq4eHs/q6fe0TpEUkU2gQPtsZpBL6WS6blbbPGk36/f681b2+AgVtm8ycq6CGR2+WP6f YSGXO4pf02VLdyrpJ6uqbt9YsB9ee4No+ZBq8=
After seeing a bug report recently regarding unnecessary deactivation
of components I decided to delve further into an issue I have had for
sometime. The problem being that sometimes for no apparent reason
(well that i could figure out at the time) during programmatic service
registrations some DS components would be deactivated during what
would i would consider a normal osgi framework startup.
The results of my findings are located on the bug ticket
If anyone else has the time it would be appreciated if you can
replicate the deactivation issue pointed to in the sample i have
provided (you may need to start up the osgi framework multiple times
to see it appear), i have reproduced it on several machines many
times, but since they are effectively the same hardware/os it doesn't
I also have a experimental patch that i believe catches all the cases
I have come across.
Any thoughts, feedback would be appreciated.