SIgh. I can't repro the problem that's interesting to you, and the
more CXF-ish problem needs to be chased at CXF.
On Wed, Jul 6, 2016 at 12:29 PM, Benson Margulies wrote:
> If I can repro it, I'll endeavor to produce.
>
>
> On Wed, Jul 6, 2016 at 12:25 PM, David Jencks
If I can repro it, I'll endeavor to produce.
On Wed, Jul 6, 2016 at 12:25 PM, David Jencks wrote:
> I’m wondering what the DS implementation bundle is getting it’s Config Admin
> packages from in each case.
>
> thanks
> david jencks
>
>> On Jul 6, 2016, at 9:20 AM,
It's the same karaf. I fear that in Karaf 4.0.4 there is a coin being
flipped to decide which set of gogo commands to use. I do not know how
to get Karaf to use the real SCR command and not its own by changing
what I type, maybe there's a way. It's another bundle start order
business.
On Wed,
I’m wondering what the DS implementation bundle is getting it’s Config Admin
packages from in each case.
thanks
david jencks
> On Jul 6, 2016, at 9:20 AM, Benson Margulies wrote:
>
> I can dump a bunch of wiring. But I'd have to repro the problem.
> which, after being
Is that the same karaf? The first scr:list looks like the new format and the
second like the really old format. There have been some shenanigans where
karaf thought they knew better than DS how to write a gogo command, so maybe
only the command is the wrong one rather than the DS
I can dump a bunch of wiring. But I'd have to repro the problem.
which, after being quite reproducible for some time, has gone into
hiding to be replaced by a different problem. Just what bundle's
wiring are you interested in?
On Wed, Jul 6, 2016 at 12:18 PM, David Jencks
Here's how I got into this.
I have this Karaf assembly. If I start if just after it is built, it
works fine. If I stop and restart it, it fails, because the CXF HTTP
transport does not start in time.
So, I added @References to ensure that the transport starts first.
Then, I hit the problem
There has been another report of a similar problem that I haven’t been able to
reproduce (outside karaf). Does Karaf provide any way of looking at the bundle
wiring? I’d like to see how the DS bundle is wired in the working and non
working cases. I’m wondering if in the non working case DS
com.basistech.worker.service.cfg exists.
And when I stopped and started karaf, the component got itself activated.
On Wed, Jul 6, 2016 at 12:01 PM, David Jencks wrote:
> You have configuration policy require and there is no component configuration
> shown, so the
You have configuration policy require and there is no component configuration
shown, so the configuration is missing.
If at least one matching configuration were available to DS you’d see one
component configuration for each configuration, and then you could tell if the
references were
Hi Benson,
Could it be that the configuration with pid com.basistech.worker.service is
missing? Or otherwise one of the services that it depends on isn't there
(or isn't visible)?
Cheers,
David
Folks, I have a service that isn't starting, and I cannot see why. Any clues?
karaf@root>scr:details com.basistech.ws.worker.service.WorkerService
Component Details
Name: com.basistech.ws.worker.service.WorkerService
State : UNSATISFIED
Properties :
12 matches
Mail list logo