janwesterkamp opened a new issue, #8355:
URL: https://github.com/apache/camel-quarkus/issues/8355
### Bug description
Hello,
since migrating the quarkus version from 3.31.4 to 3.32.1 and with it to
camel-quarkus 3.32.0 or camel 4.18.0 it's not possible to write to the
configured object store via minio (client instance created by quarkus minio
client).
Here a test route, which gets called by REST DSL via PUT via JUnit(5) test
with the body value of "TESTPUT"
```
from(DIRECT_OBJECT_STORE_PUT_OBJECT)
.log(LoggingLevel.INFO, "Processing ${id}")
.log(LoggingLevel.INFO, "Headers (before): ${headers}")
.log(LoggingLevel.INFO, "Body (before): ${body}")
.setHeader(MinioConstants.OBJECT_NAME,
simple("${header.objectName}"))
//FIXME Workaround!?
//.setBody(simple("TESTPUT"))
.log(LoggingLevel.INFO, "Headers (in between): ${headers}")
.log(LoggingLevel.INFO, "Body (in between): ${body}")
.to("minio://test-ephemeral")
;
```
Calling this with camel-quarkus 3.32.0 fails with an HTTP Status Code 500
Internal Server Error (because of REST PUT call handles Exception).
Further investigations did not show significant changes on the camel-minio
and camel-quarkus-minio component between these versions.
However, setting the body in the route directly to the same value works
around the problem (see FIXME comment)! So the body object received from the
REST DSL might be related for issue.
In the original application there was also a strange log error message
before the exception, which I could not reproduce on the simple test route yet,
but may give a hint:
`simple{valid part size must be provided when object size is unknown}`
One difference is the use of OpenTelemetry observability in the original
application.
So may be this is a side effect related to the major simple language
improvements in the camel 4.18.0 release?
--
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 to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
