GitHub user gaohoward opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1332

    ARTEMIS-1227 Internal properties not removed from messages

    In a cluster if a node is shut down (or crashed) when a
    message is being routed to a remote binding, a internal
    property may be added to the message and persisted. The
    name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
    if the node starts back, it will load and reroute this message
    and if it goes to a local consumer, this property won't
    get removed and goes to the client.
    
    The fix is to remove this internal property before it
    is sent to any client.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gaohoward/activemq-artemis master_priv_header

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1332.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1332
    
----
commit 1c86472a99ae474aba7b07e6c03bbc970298c232
Author: Howard Gao <[email protected]>
Date:   2017-06-12T12:30:41Z

    ARTEMIS-1227 Internal properties not removed from messages
    
    In a cluster if a node is shut down (or crashed) when a
    message is being routed to a remote binding, a internal
    property may be added to the message and persisted. The
    name of the property is like _AMQ_ROUTE_TOsf.my-cluster*.
    if the node starts back, it will load and reroute this message
    and if it goes to a local consumer, this property won't
    get removed and goes to the client.
    
    The fix is to remove this internal property before it
    is sent to any client.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to