Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-14395

camel-jms - Add option to turn off Artemis optimization for bytes messages

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.2.0
    • Component/s: came-jms
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              davsclaus Claus Ibsen
              Reporter:
              davsclaus Claus Ibsen
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: