-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jolokia is failing (again) #5855
Comments
Could it relate to the recent Jolokia 2.1.x updates? |
Thanks @tadayosi I think it does as it happened last time. However it's kind of weird, in the sense that we should be using the previous dependency released which is 2.0.2. The container spec is in fact:
so, I'd expect this to work. Or is there any reason why an older dependency won't work when a new version is over? |
The agent is not started with this warning:
|
@grgrzybek does the above problem ring any bell to you? |
Hmm, I'm pretty sure that if you use |
Yeah, but for some reason it was required when a few months ago it suddenly started to fail. It was some workaround we had to apply, see #5668 However, the weird thing is that these failures are happening suddenly. This very same configuration (with the very same dependency) was working correctly until at least September 18th (see https://github.com/apache/camel-k/actions/runs/10916172666/job/30298712407#step:5:1145). I will try removing the classpath later in the day and let you know, but I have the feeling there is some hidden thing that is making the dependency unstable. |
Getting full stack trace would be nice too - whether this exception happens in agent's |
That's the full stack indeed :) It's happening in the agents call, even before the Camel application starts. Here the entire stack with the rest of the application. Mind that the application starts correctly. What it happens is that the agent does not start, so, it won't expose the port as expected.
full dump is available in https://github.com/apache/camel-k/actions/runs/10942519804/job/30379734409#step:5:2401 if it may helps getting more info. |
Can we reproduce outside of GH actions and outside of OpenShift? |
I'll have a look and try to come out with a reproducer. |
I'm not very experienced with camel-k, so thanks - it'd be very helpful! |
No problem. No, that's the weirdness. It started with no changes in our code yesterday night at 2:31 AM (see https://github.com/apache/camel-k/actions/runs/10932241111). And for the records, it happened a few months back as well (see #5666). Also in that occasion was a sudden break with no changes on our code. |
I see: - args:
- -javaagent:dependencies/lib/main/org.jolokia.jolokia-agent-jvm-2.0.2-javaagent.jar=discoveryEnabled=false,host=*,port=8778,protocol=http,useSslClientAuthentication=false
- -cp
- dependencies/lib/main/org.jolokia.jolokia-agent-jvm-2.0.2-javaagent.jar
- -Xmx268M
- -cp
- ./resources:/etc/camel/application.properties:/etc/camel/resources:/etc/camel/resources.d/_configmaps:/etc/camel/resources.d/_secrets:/etc/camel/sources/Java.java:dependencies/*:dependencies/app/*:dependencies/lib/boot/*:dependencies/lib/main/*:dependencies/lib/main/org.jolokia.jolokia-agent-jvm-2.0.2-javaagent.jar:dependencies/quarkus/*
- io.quarkus.bootstrap.runner.QuarkusEntryPoint so Jolokia agent is actually added 3 times... However locally I had no problems when Jolokia was duplicated... |
It seems this is resolved with the new runtime. We'll keep it open until the new runtime is released. |
The text was updated successfully, but these errors were encountered: