Skip to main content
These properties show up in nearly every connector’s application.properties. Real values come from the connector’s defaults; Kubernetes secrets and ConfigMaps inject deployment values at deploy time. For deploy-time configuration through Helm values.yaml and SOPS-encrypted secrets, see Configure the connector.

Quarkus and Camel plumbing

PropertyTypical valueWhat it controls
quarkus.native.resources.includes/**Includes XSLT/JSON resources in the native image
quarkus.camel.servlet.url-patterns/*URL pattern for the REST DSL servlet
template.version1.0.0Optional version label for the connector

HTTP client and CXF

PropertyTypical valueWhat it controls
http.client.connect.timeout5000Connection timeout (ms)
http.client.request.timeout10000Request timeout (ms)
http.client.socket.timeout5000Socket read timeout (ms)
http.client.connection.max.per.route200Max connections per route
http.client.connection.max.total200Max connections in the pool
http.client.proxy.activatetrueActivate proxy for outbound HTTP calls
cxf.client.connect.timeout5000(SOAP only) connection timeout
cxf.client.receive.timeout10000(SOAP only) receive timeout
cxf.loggingFeatureEnabledfalse(SOAP only) toggle CXF SOAP request and response logging
cxf.dataFormatRAW(SOAP only) keep the literal SOAP envelope produced by your XSLT

Retry and redelivery

PropertyTypical valueWhat it controls
retryFlagfalseMaster toggle for retries (referenced by kamelets)
retryStatuses429,500,502,503,504HTTP statuses that trigger a retry
gc-http-caller-handleExceptionsInConnectorfalseIf true, the connector handles HTTP errors itself instead of relying on the kamelet

Content types and headers

PropertyTypical valueWhat it controls
contentTypeapplication/jsonDefault Content-Type for outbound calls
acceptapplication/jsonDefault Accept for outbound calls
acceptedHeadersContent-TypeComma-separated list of headers retained by HeaderRemovalPolicy
resourcesBasePath(empty)Optional base path for classpath-loaded resources; if set, must end with /
HeaderRemovalPolicy strips every header except those listed in acceptedHeaders. Use exchange properties for any side-channel data that must survive across route steps.

Custom thread pool

Use these properties when you register a CustomThreadPoolProfile for parallel EIPs such as multicast().parallelProcessing() or split().parallelProcessing().
PropertyTypical valueWhat it controls
thread.profile.core.pool.size10Baseline number of threads the pool keeps created and available
thread.profile.max.pool.size20Upper limit on threads the pool creates to handle spikes

Next step

To apply deploy-time overrides on top of these values, see Configure the connector. To exercise the routes locally and on a cluster, see Test and validate.