felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Created: (FELIX-2062) Possible concurrency induced ERROR messages during startup
Date Tue, 09 Feb 2010 17:49:29 GMT
Possible concurrency induced ERROR messages during startup
----------------------------------------------------------

                 Key: FELIX-2062
                 URL: https://issues.apache.org/jira/browse/FELIX-2062
             Project: Felix
          Issue Type: Improvement
          Components: Declarative Services (SCR)
    Affects Versions:  scr-1.4.0
            Reporter: Felix Meschberger


During startup of a system containing lots of inter-component dependencies, error messages
like the following might be logged:

09.02.2010 12:51:02.907 *ERROR* [SCR Component Actor] org.apache.sling.commons.scheduler
                 [org.apache.sling.commons.scheduler.impl.QuartzScheduler] DependencyManager
: Immediate component not yet created,
                 bind method cannot be called

This message is written by the DependencyManager.invokeBindMethod method if the component
to bind a reference is not created.

I suspect this is caused by concurrency situations where one thread has deactivated a component
while another thread is assuming to be activating the component and thus tries to bind a reference.

Maybe this message could be logged at a different level and a different message if we can
find out why this situation occurrs; e.g. if the component actually has been deactivated and
thus the bind method cannot be called any longer.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message