[
https://issues.apache.org/jira/browse/ARIES-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359006#comment-14359006
]
Adam Pilkington commented on ARIES-1245:
----------------------------------------
I've also encountered this error, and although the improved logging tells me
which bundle(s) are not in the resolved state, it doesn't shed
any light on why this might be. I've attached a patch for some more detailed
logging where the state of all bundles in the system are logged in an attempt
to solve this.
Below is an example of what the log output would look like :-
Unable to resolve bundles for subsystem/version/id testSubsystem1/1.0.0/2:
150 : STATE RESOLVED : esa.test.Bundle1 : 1.0.0 :
com.app.sample_0_0!/bundle1.jar
> SubsystemException: Framework could not resolve the bundles
> -----------------------------------------------------------
>
> Key: ARIES-1245
> URL: https://issues.apache.org/jira/browse/ARIES-1245
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Environment: Windows
> Reporter: Tom Evans
> Assignee: Mark Nuttall
> Priority: Minor
> Attachments: StartActionPatch.txt
>
>
> During testing on Windows we have seen an intermittent problem which causes
> an application not to be resolved correctly. The only evidence in our logs is
> the following stack... (The message is not very helpful as it gives no
> indication of which bundles could not be resolved).
> org.osgi.service.subsystem.SubsystemException: Framework could not resolve
> the bundles
> at
> org.apache.aries.subsystem.core.internal.StartAction.resolve(StartAction.java:170)
> at
> org.apache.aries.subsystem.core.internal.StartAction.run(StartAction.java:104)
> at
> java.security.AccessController.doPrivileged(AccessController.java:274)
> at
> org.apache.aries.subsystem.core.internal.BasicSubsystem.start(BasicSubsystem.java:287)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
