You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2007/09/20 11:07:31 UTC

[jira] Created: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Log the unsatisfied dependencies of a component which prevent activation of the component
-----------------------------------------------------------------------------------------

                 Key: FELIX-373
                 URL: https://issues.apache.org/jira/browse/FELIX-373
             Project: Felix
          Issue Type: Improvement
          Components: Declarative Services
            Reporter: Felix Meschberger
            Assignee: Felix Meschberger


A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.

It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Commented: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529094 ] 

Felix Meschberger commented on FELIX-373:
-----------------------------------------

Agreed, but let's keep this INFO logging for the moment that we do not have anything at all.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Commented: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529435 ] 

Felix Meschberger commented on FELIX-373:
-----------------------------------------

Deployed new snapshot containing this fix.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Updated: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger updated FELIX-373:
------------------------------------

    Fix Version/s: scr-1.0.0

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services (SCR)
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For: scr-1.0.0
>
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Commented: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Marcel Offermans (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529064 ] 

Marcel Offermans commented on FELIX-373:
----------------------------------------

I agree it's important to be able to get to this information, but I do think logging these kind of messages as LOG_DEBUG is the most appropriate (instead of INFO, WARN or ERROR) if anything is logged at all. I would like to see FELIX-284 implemented for all dependency management solutions we currently have. When we have that, I don't care too much about logging this at all.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Commented: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529060 ] 

Felix Meschberger commented on FELIX-373:
-----------------------------------------

Discussion on why to INFO and not to WARN or ERROR:

In an OSGi environment it is quite usual that service may be registered or not at some point in time. This may or may not constitute and actual problem. The SCR is not able to decide whether such a situation is actually a problem or not. Therefore only a LOG message is logged.

Understanding, that functionality is required to see, what components are active or not and why those components are in a certain state is not the task of logging but of some management support. Issue FELIX-284 is concerned to add such API.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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


[jira] Closed: (FELIX-373) Log the unsatisfied dependencies of a component which prevent activation of the component

Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Meschberger closed FELIX-373.
-----------------------------------

    Resolution: Fixed

Currently only the first unsatisified dependency of a component is logged at LOG_DEBUG level while the component is being activated. This behaviour is changed to log an LOG_INFO message for all unsatisfied references.

In addition a LOG_INFO message is logged when a service is registered which causes a component to be activated.

> Log the unsatisfied dependencies of a component which prevent activation of the component
> -----------------------------------------------------------------------------------------
>
>                 Key: FELIX-373
>                 URL: https://issues.apache.org/jira/browse/FELIX-373
>             Project: Felix
>          Issue Type: Improvement
>          Components: Declarative Services
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> A component may only be activated if all references may be satisifed. Otherwise the component stays unsatisfied.
> It would be a big releave if the unsatifsifed dependencies would be logged such that a system administrator may easily resolve why a certain component is not activated.

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