karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kerry Billingham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-4081) Karaf-Command 'diag' does not provide full information for Spring-DM bundles
Date Tue, 27 Oct 2015 12:54:27 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976322#comment-14976322
] 

Kerry Billingham commented on KARAF-4081:
-----------------------------------------

Sorry, should have been more specific. It's service dependencies. I've attached a simple bundle
to this issue to demonstrate the problem if it's dropped into a Karaf 4.0.1 instance. With
Spring-DM feature installed, you'll see this bundle goes into the waiting state and diag <bundle
number>' just simply states it's waiting. When it finally times-out diag simply reports
the exception but it would be useful to see what the missing service dependency is. In either
case, the service dependency can be discovered by grepping/inspecting the logs.

> Karaf-Command 'diag' does not provide full information for Spring-DM bundles
> ----------------------------------------------------------------------------
>
>                 Key: KARAF-4081
>                 URL: https://issues.apache.org/jira/browse/KARAF-4081
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-shell
>    Affects Versions: 4.0.1
>         Environment: Linux (Mint 17.2)
>            Reporter: Kerry Billingham
>            Assignee: Christian Schneider
>            Priority: Minor
>         Attachments: springdmtest-1.0-SNAPSHOT.jar
>
>
> When using the Karaf commandline command 'diag' to diagnose a Spring-DM bundle, not all
diagnostic information is provided.
> For example, I have several Spring-DM enabled bundles which I wish to deploy in Karaf
however often I do not have their Spring-dependencies available. This means the bundles go
to the waiting state as can be seen with the 'list' command. As I am not the author of these
bundles I need to discovery easily exactly what dependencies are currently unavailable.
> Using the 'diag' command on the Spring-DM enabled bundles initially only states the bundle
is 'waiting' but it does not state what dependency it is waiting for. I understand that this
is a bug with Karaf 'diag' command, see link below.
> Currently the only way to resolve the issue is to either inspect the Karaf logs for bundle
startup or failure messages (which can be inconvenient if the logs are constantly updating
as in my case) or inspect the bundle itself.
> I can confirm I have the org.apache.karaf.bundle.springstate bundle installed. This issue
was raised following this Stack Overflow post:
> http://stackoverflow.com/questions/32936160/interrogate-osgi-spring-dm-framework-for-a-bundles-dependencies
> The issue can be re-created by deploying a Spring-DM enabled bundle into Karaf which
has a dependency on another Spring-DM enabled bundle but which is NOT made available.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message