Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Patch Available
-
Unknown
Description
Due to lazy creation of Out message in DefaultExchange.getOut() implementation, HazelcastComponentHelper.copyHeaders() method inadvertently creates an Out message if one has not been set yet, which then creates problems in CamelInvocationHandler.getBody() which then returns null as a result.
There should be a check in copyHeaders() to see if Out exists, e.g.:
// set out headers if (ex.hasOut()) { ex.getOut().setHeaders(headers); }