I have a working version of my stuff that entirely uses blueprint.
My assembly lists a set of boot features:
aries-blueprint
bundle
config
diagnostic
feature
jaas
shell
log
management
package
shell-compat
ssh
system
wrap
jolokia
war
Some more info:
Bottom stack trace.
"pool-2-thread-1@3587" prio=5 tid=0x1b nid=NA runnable
java.lang.Thread.State: RUNNABLE
at
org.apache.karaf.features.internal.service.FeaturesServiceImpl$3.filterMatches(FeaturesServiceImpl.java:1232)
at
org.apache.felix.framework.util.SecureAction.invoke
Hi Benson,
did you try to reproduce it on a vanilla Karaf with installing one feature
after the other.
Just to make sure which one is actually causing it?
Might be that some bundles are in conflict.
regards, Achim
2015-09-07 3:35 GMT+02:00 Benson Margulies :
> Some more info:
>
> Bottom stack t
One-by-one, I get three interesting things.
1: I need to install the first few features in an unexpected order due
to a mistake I'll correct.
2: Karaf 'reboots' after I install the DS feature, but that might be
because I didn't actually install scr.
3: As soon as I install the last feature, I get
That's not a reboot, it's just a restart of the shell, so one of your
bundles you installed does
trigger a restart of the shell bundle.
regards, Achim
2015-09-07 13:54 GMT+02:00 Benson Margulies :
> One-by-one, I get three interesting things.
>
> 1: I need to install the first few features in a
So I fixed my dependency order on bundles, and pretty much reproduced
the same set of stuff.
I have one more thing to try, which is to put the cfg files for my
services into place.
karaf@root()> feature:repo-add
file:/Users/benson/.m2/repository/org/apache/cxf/karaf/apache-cxf/3.1.2/apache-cxf-3.
Ok, so let's try to narrow this down a bit.
At least concerning the SCR feature I'd say it's most likely due to an
dependency on the eventadmin feature, which is know to cause a "refresh" on
the shell features.
Therefore maybe an early eventadmin feature install could make this one
disappear.
For
On Mon, Sep 7, 2015 at 8:14 AM, Achim Nierbeck wrote:
> Ok, so let's try to narrow this down a bit.
> At least concerning the SCR feature I'd say it's most likely due to an
> dependency on the eventadmin feature, which is know to cause a "refresh" on
> the shell features.
> Therefore maybe an earl
frontloading eventadmin did not stop the shell from restarting or all
the backtraces about, apparently, missing pieces of blueprint.
In an effort to narrow this down, I installed only the features needed
to get to the last two (the DS feature and the 'null pointer feature')
-- that eliminated thre
If installing the scr feature triggers to refresh the cxf feature, it must
be one of the scr bundles contained.
Most likely a might be able to sole that
for the scr feature.
regards, Achim
2015-09-07 14:41 GMT+02:00 Benson Margulies :
> frontloading eventadmin did not stop the shell from
On Mon, Sep 7, 2015 at 8:48 AM, Achim Nierbeck wrote:
> If installing the scr feature triggers to refresh the cxf feature, it must
> be one of the scr bundles contained.
> Most likely a might be able to sole that for
> the scr feature.
Achim, did you mean my feature that uses DS or the stoc
As I already said in the other thread,
make sure you don't provide the compendium jar it'll colide with a bunch of
other jars already providing the
needed packages ...
regards, Achim
2015-09-07 15:09 GMT+02:00 Benson Margulies :
> On Mon, Sep 7, 2015 at 8:48 AM, Achim Nierbeck
> wrote:
> > If
Oh ... and use the scr feature it's known to work with Karaf.
regards, Achim
2015-09-07 15:26 GMT+02:00 Achim Nierbeck :
> As I already said in the other thread,
> make sure you don't provide the compendium jar it'll colide with a bunch
> of other jars already providing the
> needed packages ...
13 matches
Mail list logo