I think that I figured it out. I think that it is a configuration issue in
the stock configuration of Karaf Container (apache-karaf-4.0.10.tar.gz).
etc/org.apache.karaf.features.cfg contains:
#configCfgStore=true
which I think means that the default setting is for the features service to
write
Hello,
I'm having trouble creating a self contained KAR file, which depends on
another KAR file (see below). KAR A specifies some core features such as
activemq and cxf. KAR B depends on KAR A.
What I am finding is when I drop KAR B into the deploy folder of karaf, it
is still going to the
Thank you very much for the prompt reply JB!
On Thu, 09 Nov 2017 16:41:00 +0100, Jean-Baptiste Onofré
wrote:
Hi Sergiy,
For the transaction PID, it's blacklisted because the location of the
journal files could be specific to a Karaf instance.
For the Cellar node and
Hello,
I've found that as part of the fix for
https://issues.apache.org/jira/browse/KARAF-4941 the configuration pids
for were added into inbound and outbound blacklists for configuration
synchronization
Yes, please !
Thanks,
Regards
JB
On 11/09/2017 04:12 PM, Tim Moloney wrote:
Should I create a new issue for this in JIRA?
On Wed, Nov 8, 2017 at 8:58 AM, Tim Moloney > wrote:
Yes, the config blocks start like
No, I don't
Should I create a new issue for this in JIRA?
On Wed, Nov 8, 2017 at 8:58 AM, Tim Moloney wrote:
> Yes, the config blocks start like
>
>
>
> No, I don't start with any custom service configuration files in etc.
> Only the ones that come with Karaf. After running,
By the way, I'm now able to reproduce the issue.
Workaround using either /bin/bash in karaf script, or aliasing sh with bash.
I'm fixing that.
Regards
JB
On 11/08/2017 09:03 PM, Francois Papon wrote:
Hi,
When I launch Karaf I've got this error :
./bin/karaf: 218: ./bin/karaf: Bad