[
https://issues.apache.org/jira/browse/KARAF-4081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14976499#comment-14976499
]
Christian Schneider commented on KARAF-4081:
--------------------------------------------
Unfortunately it only writes
{noformat}Application context initialization for 'com.mycompany.springdmtest'
has timed out{noformat}
See:
org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor.fail(Throwable)
There it writes the missing dependencies into the log but only put the rather
unhelpfull message into the exception. So I think I can not easily solve this
but at least the log shows the detailed status.
> 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
> Fix For: 4.0.3
>
> 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)
