Hi
Ahh you use hawtio. You can see that, when you install hawtio, you have a "mix"
of Pax Web 7.2.x and 7.3.x.
Karaf 4.3.x itself uses Pax Web 7.3, but hawtio seems to want Pax Web 7.2
(which is bad, it should not force Pax Web version).
Hawtio should be fixed, definitely (probably hawtio did
Thanks, JB,
I now installed every feature separately in a different order after
cleaning /data and removing a blacklist configuration from another :
feature:repo-add hawtio 2.13.0
feature:repo-add camel 3.7.2
feature:repo-add spring-legacy
feature:repo-add activemq 5.16.1 (5.15.14)
feature:i
You still have the same problem.
When you do feature:install camel-blueprint camel-jms camel-http, you can see
that jline bundles will be uninstalled, so the Karaf shell will be uninstall.
Can you please do:
Feature:install -v camel-blueprint
Feature:install -v camel-jms
Feature:install http
Fe
Same outcome with Camel 3.7.2 LTS and leaving out camel-stream as well
(after clearing /data):
karaf@root()> feature:install -v -t camel-blueprint camel-jms camel-http
Adding features:
camel-blueprint/[3.7.2,3.7.2],camel-http/[3.7.2,3.7.2],camel-jms/[3.7.2,3.7.2]
Changes to perform:
Region:
No constraint, I wanted to use the most recent versions but got stuck
there as well.
I then found examples using this version and just tried. I'm going to
use the most recent versions now and try with your tips to get it to work.
Thanks,
Michael
Am 09.03.21 um 20:58 schrieb Jean-Baptiste O
Actually, it’s not the whole Karaf runtime which stop or restart: it’s the
shell part.
The problem is that you install camel-stream not aligned in term of jline, and
so the karaf shell is refreshed due to jline.
Do you have a constraint to use a so old Camel version ??!!!
Regards
JB
> Le 9 ma
Ok, I think I will provide the first example for the difficulties I face.
I removed the /data folder and restarted Karaf, then:
karaf@root()> feature:install -v -t camel-blueprint camel-stream
camel-blueprint camel-jms camel-http camel-saxon
Adding features:
camel-http/[2.24.1,2.24.1],camel-jm
Hi,
Feature:install -v -t will directly output on the terminal (System.out).
When you do feature:install, the resolver output goes into data/karaf.log (by
default).
Regards
JB
> Le 9 mars 2021 à 18:22, Michael Brohl a écrit :
>
> Thank you JB,
>
> I was hoping there would be some general (a
Thank you JB,
I was hoping there would be some general (and releatively easy) approach
or strategy to detect the requirements each feature needs or maybe some
compatibility list to study.
I will try with your suggestions and come back with more data if this is
not successful.
The resolver
Hi JB,
Thank you for the info. It seems to be the order of doing installs. Let me try
to come up with a small generic example and send you the info.
Best,
Oleg
> On Mar 9, 2021, at 4:55 AM, Jean-Baptiste Onofre wrote:
>
> Hi Oleg,
>
> It seems you have the same as
> https://issues.apache.or
Hi Oleg,
It seems you have the same as https://issues.apache.org/jira/browse/KARAF-6916
So, I guess you also have a refresh, right ?
I never saw such issue, but if you can produce a test case to reproduce it, I
will investigate.
Thanks,
Regards
JB
> Le 9 mars 2021 à 10:49, Oleg Cohen a écrit
Greetings,
When installing a feature I am getting the following exception, which seems
pretty fundamental:
org.apache.felix.resolver.reason.ReasonException: Unable to resolve root:
missing requirement [root] osgi.identity; osgi.identity=bundle;
type=karaf.feature; version="[4.3.0,4.3.0]";
fil
Hi Michael,
It’s hard to say without the log messages. You can use feature:install -t -v to
"simulate" the installation and get some details (like refresh) before actually
installing a feature.
I bet you have a refresh on hawtio caused by ActiveMQ.
You can disable auto refresh to avoid such is
Hi,
I am struggling with a fresh setup on Karaf 4.3.0, trying to install
Apache Camel, ActiveMQ and Hawt.io in current versions.
Depending on the order of installation, I get different errors leaving
me clueless what to do with errors like
Singleton conflict. Unresolved requirements: []
14 matches
Mail list logo