[
https://issues.apache.org/jira/browse/CAMEL-14395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-14395:
-----------------------------------
Assignee: Claus Ibsen
> camel-jms - Add option to turn off Artemis optimization for bytes messages
> --------------------------------------------------------------------------
>
> Key: CAMEL-14395
> URL: https://issues.apache.org/jira/browse/CAMEL-14395
> Project: Camel
> Issue Type: Improvement
> Components: came-jms
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 3.2.0
>
>
> Reported on user forum
> The byte[] vs Byte[] is likely more of a Artemis question how their
> JMS client handle this.
> For byte[] then Camel creates a javax.jms.BytesMessage and for the
> other it creates a javax.jmx.ObjectMessage.
> You can force what JMS message type Camel should use with the option
> (see its docs)
> You can also turn on TRACE logging and see if you see this logging message
> LOG.trace("Optimised for Artemis: Reading from BytesMessage in
> streaming mode directly into CachedOutputStream payload");
> It smells that this optimized mode (CAMEL-11931) somehow cause Artemis
> to close the stream. (smells like a bug in Artemis).
> We could maybe add an option to turn this optimized Artemis mode off.
> You can also turn off mapJmsMessage then Camel does not extract
> body/headers etc.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
