[
https://issues.apache.org/jira/browse/AMQ-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056078#comment-16056078
]
Christopher L. Shannon edited comment on AMQ-6708 at 6/20/17 4:57 PM:
----------------------------------------------------------------------
One thing I noticed is that you have configured
{{concurrentStoreAndDispatchTopics}} set to true. Setting
{{concurrentStoreAndDispatchQueues}} to true (the default) is recommended but
for Topics it is not and might be the cause of the issue. You might want to
try disabling that first.
Other than that, to narrow down the issue, you'd probably need to start
removing variables. It's possible there could be something going on with
Camel, etc but it's hard to say.
was (Author: christopher.l.shannon):
One thing I noticed is that you have configured
concurrentStoreAndDispatchTopics set to true. Setting
concurrentStoreAndDispatchQueues to true (the default) is recommended but for
Topics it is not and might be the cause of the issue. You might want to try
disabling that first.
Other than that, to narrow down the issue, you'd probably need to start
removing variables. It's possible there could be something going on with
Camel, etc but it's hard to say.
> 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)
