Pasquale Congiusti

Yes, I think that the behavior should be to provide any matching catalog if exists, otherwise to fail (with a clear failing message) expecting the user to provide a fixed...

I've managed to run an Integration enabling jolokia and it seems on Kubernetes side it is running as expected (`java -javaagent:dependencies/lib/main/org.jolokia.jolokia-jvm-1.7.2.jar=discoveryEnabled=false,host=*,port=8778`). If I understand correctly, the error you're getting is...

Thanks @tadayosi for such detailed reproducer. We can have a look and see what could be the root cause. However, it seems something related to the runtime. Is this something...

I re-read some of the comments above and it seems the reporter manages to run it properly in Camel Quarkus regular app. We'll have a look asap.

> the issue is the fact that camel-k operator does not add any xml related dependency if not needed by the routes whereas the example by @tadayosi does https://github.com/hawtio/hawtio-online-examples/blob/main/camel-quarkus/pom.xml#L110-L116 >...

That does not seems to be the problem. There was a minor change required in the runtime catalog as the JAXB dependency was still pointing to Camel and not to...

> maybe there are some spurious dependencies making thing failing, has the new kit be created from scratch ? Yes. What I am looking now is the jolokia version. As...

I tried the Camel Quarkus examples with jolokia 1.7.2 and it seems it works correctly. I've also used the same set of dependencies for Camel 4. I wonder if this...

Thanks @claudio4j for looking at it. If it is solved with the new released runtime, I guess we can close this issue. @hdwivedi-ra cold you please check on your side...

> @squakez I have kamel v2.1 how can I install camel-k runtime version 3.2.3? I want to install it in a new K8s namespace. You need to specify the Camel...