You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2020/10/09 04:05:00 UTC

[jira] [Deleted] (KARAF-2891) Display status and errors of components/services in Karaf container.

     [ https://issues.apache.org/jira/browse/KARAF-2891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré deleted KARAF-2891:
----------------------------------------


> Display status and errors of components/services in Karaf container.
> --------------------------------------------------------------------
>
>                 Key: KARAF-2891
>                 URL: https://issues.apache.org/jira/browse/KARAF-2891
>             Project: Karaf
>          Issue Type: Improvement
>         Environment: Karaf container
>            Reporter: Stefan Castman
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>
> Want to check the status of the components/services (and why they are NOT satisfied) in Karaf container (v 2.3.2/3.0.0), but the Equinox DS commands that worked fine in the OSGi container gives different output or don’t work at all in Karaf.
>  
> The commands that not work as before/at all in Karaf:
> karaf> *ls*                     (In Karaf, the service are listed in another format and the useful “State” column is missing in the output?)
> karaf> *ls -c <ID>*        (In Karaf, this command complains about “Error executing command osgi:ls undefined option -c" when trying to display information about NOT satisfied services in a bundle?) 
> karaf> *comp <ID>*       (In Karaf, this command complains about “Invalid component ID!” whatever ID I use to display information about a NOT satisfied service?)
> The *scr:list/details* feature in Karaf replaces the native *ls* command in some extent, but it {color:red}doesn't display the useful error details{color} that *ls -c <ID>* and *comp <ID>* does.
> Example of useful error details:
> -Exceptions: "No instances were created because: Can not activate instance of component <REF>. The activation throws: java.lang.IllegalArgumentException".
> -Dynamic information: "*The component is NOT satisfied, The following references are not satisfied: <REF>".
> -Indication of missing component/service configuration.
> For more detialed examples of "useful error details" generated by the Equinox DS commands in OSGi container, see Karaf forum post: http://karaf.922171.n3.nabble.com/How-see-status-of-services-and-why-they-are-NOT-satisfied-in-Karaf-container-tt4032359.html#a4032493
> Regards
> SteffeC



--
This message was sent by Atlassian Jira
(v8.3.4#803005)