[
https://issues.apache.org/jira/browse/AMQ-6708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16055998#comment-16055998
]
Peter Boekelheide commented on AMQ-6708:
----------------------------------------
So our topology is pretty complicated, but I'll give you a couple of nodes to
show the basic idea. The four configuration files in question are included in
the [^config.zip] attached to this ticket.
We've got one broker, here mqbe03, with the configuration be03_activemq.xml and
be03_camel.xml. That broker is networked to another broker, 04, which I'm not
showing here. They have rebalance and their clients all do failover.
Then there's a third broker, npqueue01, which has the configuration
npqueue_activemq.xml and npqueue_camel.xml. This broker is standalone, and uses
its camel routing to pull from mqbe03 (or, if it's rebalanced of fails over,
mqbe04).
Let me know if this isn't clear enough or you need more information.
> 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
>
> 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)
