>>>>> Steinar Bang <[email protected]>:
> Maybe I can try a remote debug into karaf and figure out what is
> attempted loaded that way...?
I've done remote debugging of the second call to bundle:install.
One thing I see, is that in the call to Deployer.handlrePrerequisites()
on line 394 (in the karaf-4.3.x branch) of Deployer.java, the feature
I'm requesting seems to be part of the prerequisites:
{root=[feature:system/[4.3.7,4.3.7], feature:diagnostic/[4.3.7,4.3.7],
feature:kar/[4.3.7,4.3.7],
feature:oldalbum-with-derby/[1.8.0.SNAPSHOT,1.8.0.SNAPSHOT],
feature:service/[4.3.7,4.3.7], feature:jaas/[4.3.7,4.3.7],
feature:config/[4.3.7,4.3.7], feature:feature/[4.3.7,4.3.7],
feature:management/[4.3.7,4.3.7],
feature:sampleapp-with-derby/[1.0.0.SNAPSHOT,1.0.0.SNAPSHOT],
feature:wrap/[2.6.10,2.6.10], feature:log/[4.3.7,4.3.7],
feature:instance/[4.3.7,4.3.7], feature:bundle/[4.3.7,4.3.7],
feature:eventadmin/[4.3.7,4.3.7], feature:shell/[4.3.7,4.3.7],
feature:ssh/[4.3.7,4.3.7], feature:package/[4.3.7,4.3.7],
feature:deployer/[4.3.7,4.3.7], feature:framework/[4.3.7,4.3.7]]}
(in this case sampleapp-with-derby)
Presumably that's why it seems to go loopety-loop between
Deployer.deploy() and Deployer.handlePrerequisites() until the stack
overflows...?
But why this happens and also why this only happens only on the second
use of the bundle:install command, is still unclear...?
I see that sampleapp-with-derby (the feature currently being installed)
and the feature I installed with the first feature:install are the only
non-karaf features in the list.
Also: why is oldalbum-with-derby part of the prerquisites?
1. It's already installed
2. It is not a prerequisite listed by sampleapp-with-derby
The search continues.
