camel-k: Error: io.quarkus.vertx.http.runtime.TrustedProxyCheckPartConverter not a subtype
What happened?
I have been randomly getting an error starting Integrations that use quartz and run on camel-k-runtime 3.2.3. The Integrations builds, but fails to start with:
Exception in thread "main" java.lang.reflect.InvocationTargetException
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:569)
at io.quarkus.bootstrap.runner.QuarkusEntryPoint.doRun(QuarkusEntryPoint.java:61)
at io.quarkus.bootstrap.runner.QuarkusEntryPoint.main(QuarkusEntryPoint.java:32)
Caused by: java.util.ServiceConfigurationError: org.eclipse.microprofile.config.spi.Converter: io.quarkus.vertx.http.runtime.TrustedProxyCheckPartConverter not a subtype
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:593)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
at io.smallrye.config.SmallRyeConfigBuilder.discoverConverters(SmallRyeConfigBuilder.java:135)
at io.smallrye.config.SmallRyeConfig.buildConverters(SmallRyeConfig.java:78)
at io.smallrye.config.SmallRyeConfig.<init>(SmallRyeConfig.java:70)
at io.smallrye.config.SmallRyeConfigBuilder.build(SmallRyeConfigBuilder.java:629)
at io.quarkus.runtime.generated.Config.<clinit>(Unknown Source)
at io.quarkus.runner.ApplicationImpl.<clinit>(Unknown Source)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:70)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:44)
at io.quarkus.runtime.Quarkus.run(Quarkus.java:124)
at io.quarkus.runner.GeneratedMain.main(Unknown Source)
... 6 more
- Changing the runtimeVersion to 3.8.1 does not reproduce the error;
- The error happens with the Cron trait fallback enabled or not.
- There’s no other information in the pod log besided the error
- Using Jib build strategy
Here is a sample Integration that eventually reproduces the error:
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: quartz-323
spec:
sources:
- name: main.yaml
content: |-
- from:
uri: quartz://ipaas/trigger?cron=0+*+*+?+*+*
steps:
- log:
message: "It worked"
traits:
camel:
runtimeVersion: 3.2.3
cron:
fallback: true
Steps to reproduce
No response
Relevant log output
No response
Camel K version
2.4.0
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (15 by maintainers)
Commits related to this issue
- bugfix(#5758): changing incremental image build to not allow extra dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not considering the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not consider the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing incremental image build to not allow extra dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not consider the application jar when matching dependencies — committed to lsergio/camel-k by lsergio 2 years ago
- bugfix(#5758): changing incremental image build to not allow extra dependencies — committed to apache/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to apache/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not consider the application jar when matching dependencies — committed to apache/camel-k by lsergio 2 years ago
- bugfix(#5758): changing incremental image build to not allow extra dependencies — committed to apache/camel-k by lsergio 2 years ago
- bugfix(#5758): changing dependencies build order strategy to be compatible with the incremental image build algorithm — committed to apache/camel-k by lsergio 2 years ago
- bugfix(#5758): incremental image build should not consider the application jar when matching dependencies — committed to apache/camel-k by lsergio 2 years ago
An alternative and even a possible final solution which we may use to keep the feature is to change instead the algorithm and make the incremental image kind of “additive” only. For instance, we can reuse only those base image that contains a subset of required dependencies but have no other “extra” dependency not required. If you think this is a good solution and you have time, you can have a look yourself as well.
ops, this was just to not duplicate the code here. The idea is to choose either one.