[
https://issues.apache.org/jira/browse/KARAF-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964956#comment-16964956
]
Philip Brown commented on KARAF-6500:
-------------------------------------
Maybe you could help me with a suggest of who next to ping in the related issue.
(camel people, artemis people,or what)
I've been told that the file component defaults to stream, becuase it is
memory efficient and can segmen the data. Whereas when you convert to string,
it mandates a single contiguous chunk of memory.
For large messages, this is clearly bad.
So how come there isnt some "rewindable stream" type or something? maybe an
actual file type message, or equivalent. I dont know the most appropriate
naming, I'm new at this :)
So, what should I call it and who should I bug about it?
> 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)
