[
https://issues.apache.org/jira/browse/AMQ-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056333#comment-16056333
]
Christopher L. Shannon commented on AMQ-6708:
---------------------------------------------
What kind of messages are you sending? Does the issue still happen if you
change message type? (String, bytes message, etc, or persistent or
non-persistent)
The main thing is just trying to narrow down what the issue could be as right
now it will be hard to figure out as your setup is complex. For example, does
the issue happen if you only have 1 consumer instead of multiple? Does the
issue happen if you just use a standalone broker and no network of brokers?
Does the issue happen if Camel is not used? The simplest setup possible to
reproduce the issue the better. For example, If you are able to reproduce it
with a standalone broker without Camel it would be a lot easier to debug.
> When reading from a topic, messages will intermittently have empty body text
> ----------------------------------------------------------------------------
>
> Key: AMQ-6708
> URL: https://issues.apache.org/jira/browse/AMQ-6708
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.14.3
> Environment: CentOS 7
> Reporter: Peter Boekelheide
> Attachments: config.zip
>
>
> We've come across a problem with our brokers wherein messages consumed from a
> topic will intermittently have null/empty body text. This is regardless of
> the type of consumer we use, be it stomp or openwire. There doesn't seem to
> be any particular pattern to the null messages that we can see, and they may
> be null for one consumer but the same message would have a body for another
> consumer. While we can consistently reproduce it in the sense that we can
> connect a consumer and wait for a period of time (usually a couple of
> minutes) and the issue will occur, we can't seem to find the exact conditions
> under which the null message happens.
> I know this a relatively vague issue description, but I'm not sure what more
> you'd be looking for right now. Please comment and let me know if you'd like
> more information. This is currently a major problem for us, as it makes our
> topics unreliable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
