claudio4j closed issue #4990: Route diagram not visible in hawtio console: JMX
connector not running
URL: https://github.com/apache/camel-k/issues/4990
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go t
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1874206073
> It is failing because the operator cannot download from maven some
dependency and times out after 5 minutes:
>
> ```
>
{"level":"info","ts":"2024-01-02T14:03:23Z","lo
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1874084169
It is failing because the operator cannot download from maven some
dependency and times out after 5 minutes:
```
{"level":"info","ts":"2024-01-02T14:03:23Z","logger":"camel-k.m
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1874078122
> kubectl logs -f $(kubectl get pod -l app=camel-k -oname)
https://github.com/apache/camel-k/assets/133973883/dbacbe1c-ecfd-4b6e-9272-5ca4f0e8c79d";>
Operator logs
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1874030708
Thanks, it seems the build is failing when it tries to create the new
CamelCatalog. Could you please check the result of `kubectl get camelcatalog`?
also, you should be able to see t
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1874005061
> Okey, thanks. Could you please run the following `kubectl get it hello -o
yaml`? so we can check why the integration is on error. In general, you can
have a look at the [troubl
claudio4j commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873817827
> It is showing error in logs
You can also look at the camel-k-operator logs: `kubectl logs -f $(kubectl
get pod -l app=camel-k -oname)`
--
This is an automated messa
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873800546
Okey, thanks. Could you please run the following `kubectl get it hello -o
yaml`? so we can check why the integration is on error. In general, you can
have a look at the [troubleshoot
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873779384
It is showing error in logs
https://github.com/apache/camel-k/assets/133973883/6b83dbe5-abf5-4327-bbc2-16cb4462ae19";>
--
This is an automated message from the Apache Git
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873768176
It sounds weird. The Integration and related Deployment/Pod should be
created and the runtime used should be the new one you specified. Mind that it
would probably run a new build to
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873763168
@claudio4j
`./kamel run hello.java -t jolokia.protocol=https -t jolokia.host=* -t
jolokia.port=8778 -t jolokia.use-ssl-client-authentication=false -t
jolokia.enabled=true --n
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873752317
> @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 runtime property trait:
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873749573
@squakez I have kamel v2.1 how can I install camel-k runtime version 3.2.3?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log o
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1873737280
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 and confirm if th
claudio4j commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1869509394
It worked with camel-k-runtime 3.2.3 by using the camel trait `-t
camel.runtime-version=3.2.3`
Camel K 2.2 (main branch, unreleased) also works, so the original errors
seems to
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1866086100
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 may be some classpath
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865990855
> 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 we are using
lburgazzoli commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865989432
maybe there are some spurious dependencies making thing failing, has the new
kit be created from scratch ?
--
This is an automated message from the Apache Git Service.
To resp
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865970931
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 Quarkus (I think it was
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865903734
> 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/hawt
lburgazzoli commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865896860
the issue is the fact that camle k does not add any xml related bit if not
needed by the routes whereas the example by @tadayosi does
https://github.com/hawtio/hawtio-online-exam
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865881302
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 reproduc
tadayosi commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1865871468
Hi Camel K team @squakez,
It's really not an issue specific to Hawtio, but you can reproduce it only
with Camel K.
For instance, you can use this example
https://githu
tadayosi commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1864112721
@hdwivedi-ra OK, thanks. It looks like I can reproduce the issue at hand.
I'll look into it further and get back to you.
--
This is an automated message from the Apache Git Servic
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1862263160
@tadayosi
The behavior is same with the native build also
**kamel run hello.java --name hawtio-online-example-camel-k --dev -t
jolokia.protocol=https -t jolokia.host=*
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1862257171
@tadayosi
Belo is the sample route which I am running
```
import org.apache.camel.builder.RouteBuilder;
public class hello extends RouteBuilder {
@Overr
tadayosi commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1862233071
@hdwivedi-ra If you're not, it might be related to the content of the
integration you're running. Sharing the integration code that reproduces the
issue could help.
--
This is an
tadayosi commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1859990224
Just to be sure, are you not using native build for the Camel K integration?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1859964118
camel:jaxb is already added
[1] 2023-12-18 09:47:58,616 INFO [io.quarkus] (main) Installed features:
[camel-bean, camel-core, camel-java-joor-dsl, camel-jaxb, camel-k-core
hdwivedi-ra commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1859942196
The route diagram is correctly visible if I run camel route in Quarkus
application using the same versions. The issue is JMX service is not started in
the camel-k integration.
squakez commented on issue #4990:
URL: https://github.com/apache/camel-k/issues/4990#issuecomment-1859913503
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.ja
hdwivedi-ra opened a new issue, #4990:
URL: https://github.com/apache/camel-k/issues/4990
### What happened?
Hi,
I am using kamel version 2.1 and want to enable hawtio monitoring with
jolokia traits. There is an exception when viewing the route diagram.
jakarta.xml.bind.JAXBExce
32 matches
Mail list logo
