Hi Paul, Am Donnerstag, den 19.06.2008, 15:49 +0200 schrieb Paul Neyens: > Hi Felix, > > Sorry for the late response, I haven't been accessing these mails for a > while.
No problem. > I've tried the current 1.0.2 version and it works fine! Thanks for the feedback. Glad to hear it works. Regards Felix > > Thanks, > > Paul > > -----Oorspronkelijk bericht----- > Van: Felix Meschberger [mailto:[EMAIL PROTECTED] > Verzonden: maandag 2 juni 2008 15:13 > Aan: [email protected] > Onderwerp: RE: SCR race condition > > Hi Paul, > > I just deployed a new SNAPSHOT build of the Declarative Services bundle > (1.0.1-SNAPSHOT), which contains a tentativ fix for this issue. Could > you please check, whether it still occurrs in your use case ? > > Thanks and Regards > Felix > > Am Donnerstag, den 08.05.2008, 17:20 +0200 schrieb Paul Neyens: > > Done: key = FELIX-550 > > > > As mentioned in the JIRA entry, I could not reproduce the error with > > logging turned on and set to debug level. > > > > Best regards, > > > > Paul > > > > > > -----Oorspronkelijk bericht----- > > > > Hi, > > > > Am Donnerstag, den 08.05.2008, 11:09 +0200 schrieb Paul Neyens: > > > What I am seeing, is that when starting the bundle (after stopping > it > > > first), the enable method (AbstractComponentManager) is called > > starting > > > an 'enableInternal' (including an activateInternal) on the component > > > actor thread. > > > Approximately at the same time, an update call is made from the > > > configuration manager (on some thread from the CM, through method > > > 'update' in ImmediateComponentManager's anonymous ManagedService > inner > > > class) resulting eventually in a call to 'reactivate' which first > > > deactivates (deactivateInternal) on the current thread (CM thread). > > > That's where things clash, I guess. > > > > If you could create JIRA with these findings, that would be great. > > Thanks a lot. > > > > > > > > I hope this explanation is helpfull, I haven't been able to extract > a > > > log (yet). > > > > Yes it is helpfull. If you come around to attaching any log output to > > the issue, it would even be better. > > > > Regards > > Felix > > > > > > --------------------------------------------------------------------- > > 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] > > > > > --------------------------------------------------------------------- > 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] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
