Open marteloudini opened 4 weeks ago
To help, we'd need more information like a stack trace for the error or the content of the console output or quarkus.log
.
Also, there's no need to create your own CamelContext
instance. One is created for you automatically, and you can customize it with configuration properties, CDI beans, observers etc.
To help, we'd need more information like a stack trace for the error or the content of the console output or
quarkus.log
.Also, there's no need to create your own
CamelContext
instance. One is created for you automatically, and you can customize it with configuration properties, CDI beans, observers etc.
ok thanks.
i dont know customize a Server TLS and Client TLS for do MutualTLS in the same route. What are the properties for do that ? i have a micro service Quarkus Camel this service is Server with Truststore, and Client with Keystroe to can call other micro service.
thank you
i dont know customize a Server TLS and Client TLS for do MutualTLS in the same route. What are the properties for do that ? i have a micro service Quarkus Camel this service is Server with Truststore, and Client with Keystrore to can call other micro service.
It depends which components you are using. For example, if you're using platform-http
as the HTTP server consumer, then you can secure it by following this guide:
https://quarkus.io/guides/http-reference#ssl
And if you're using camel-http as the HTTP producer, you can use the sslContextParameters
option to set up your truststore etc:
https://camel.apache.org/components/4.4.x/http-component.html#_component_option_sslContextParameters
Otherwise, check the component documentation and see what options they have for security.
Bug description
Hey,
we are developing quarkus camel services, we are currently under quarkus 3.8.4, and we are deploying on a linux server with openjdk 17 64bit. (not native mode)
when we add the quarkus-management dependency, or in the code we make a declaration "DefaultCamelContext context = new DefaultCamelContext()", the application starts normally in Local with the Quarkus:dev command, but as soon as we deploy the *-runner.jar on linux server, it doesn't start.
it just says ERROR start failed... when remove this dependency or DefaultCamelContext... the app start normaly....
Do you have an idea ? Thanks in advance