activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jbertram <>
Subject [GitHub] activemq-artemis pull request #1291: Backwards compatibility + test fixes
Date Wed, 24 May 2017 22:54:58 GMT
GitHub user jbertram opened a pull request:

    Backwards compatibility + test fixes


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

    $ git pull master_work

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

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

    This closes #1291
commit de2228b0ab11821a726feeee813969ef4680f4e6
Author: Justin Bertram <>
Date:   2017-05-22T16:37:11Z

    ARTEMIS-1178 backwards compatibility issues
    This commit has 2 changes for backwards compatibility with older
    1) A "bindings query" will now detect if the client is both JMS and
    "old" (i.e. pre-2.0) and will prefix the returned queue names with the
    old prefix (i.e. "jms.queue."). This will allow the old client to
    properly detect whether or not a queue exists in its auto-creation
    2) When messages are dispatched to a consumer there is logic to detect
    if the consumer is both JMS and "old" and will prefix the "address"
    on the message with "jms.queue." or "jms.topic." as appropriate
    (if it's not already prefixed).

commit e0f03d654e7b47393ce18b90b7bc7f3549a09ceb
Author: Justin Bertram <>
Date:   2017-05-23T14:57:21Z

    Fixing failing tests after sync changes

commit 0c5fddde1acb9cd85d0631b7c079051b7f16ef87
Author: Justin Bertram <>
Date:   2017-05-24T22:50:45Z

    Revert "[ARTEMIS-1171] Improve log readability around clustering"
    This reverts commit 744221dcb5f250d724a72f0321144630ecb2eab7.
    Broke o.a.a.a.t.i.m.QueueControlUsingCoreTest.testListDeliveringMessages


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 or file a JIRA ticket
with INFRA.

View raw message