[
https://issues.apache.org/jira/browse/KARAF-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964612#comment-16964612
]
Jean-Baptiste Onofré commented on KARAF-6500:
---------------------------------------------
IMHO, that's not a Karaf issue but more a Camel one. And actually, I don't
consider as a bug. By default, the {{file}} component populate the {{Exchange}}
{{body}} with the file {{InputStream}}. ActiveMQ or Artemis are able to deal
with stream but it's a special use case.
If you want to use a JMS {{TextMessage}} then you have to convert
({{TypeConverter}}) the exchange body as a String using {{convertBodyTo}}.
> adding logging zeros out message body
> -------------------------------------
>
> Key: KARAF-6500
> URL: https://issues.apache.org/jira/browse/KARAF-6500
> Project: Karaf
> Issue Type: Bug
> Components: karaf
> Affects Versions: 4.1.2, 4.2.7
> Environment: linux centos 8
> java -version
> openjdk version "1.8.0_222"
> OpenJDK Runtime Environment (build 1.8.0_222-b10)
> Reporter: Philip Brown
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Labels: artemis, camel, camel-jms, jms
> Attachments: queuetest.xml.log1.good
>
>
> Trying out basic karaf+camel+jms to artemis integration, and stumbled on this
> bug.
> Basic file polling of input directory.. pass file to artemis, then through a
> few queues, and back out.
> Actually works fine, until I add logging. Then, depending on where logline
> is, will ZERO OUT MESSAGE BODY.
> repeatable 100% of the time.
> retried it with both karaf 4.1.2 and 4.2.7 in fresh install directories.
> breaks in both.
> bug probably goes back further.
> I'm attaching the very simple deploy file.
> run it as-is to get it working.
> $ mkdir inqueue outqueue
> in top level and make a file in inqueue to see it get validly copied over to
> outqueue.
> Then uncomment one of the 2nd or 3rd loglines.
> Suddenly, the body gets zeroed.
> note#1: I write the body of the message to the log
> note #2: this works just fine for the first logline, but the exact same
> logline in 2nd route, zeros the body out
> note #3: this doesnt just log a blank message body. The ACTUAL message body
> is zeroed, as you can see by the resulting out file
> I believe the required features are:
> feature:install jms camel camel-jms camel-blueprint
> feature:install artemis-jms-client artemis-core-client
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
