activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From clebertsuconic <...@git.apache.org>
Subject [GitHub] activemq-artemis pull request #777: ARTEMIS-734
Date Wed, 14 Sep 2016 23:00:37 GMT
GitHub user clebertsuconic opened a pull request:

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

    ARTEMIS-734

    

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

    $ git pull https://github.com/clebertsuconic/activemq-artemis expiry

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

    https://github.com/apache/activemq-artemis/pull/777.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 #777
    
----
commit 10afb539a2d5f0d8abdb6342ca5efb31bc2865b1
Author: Clebert Suconic <clebertsuconic@apache.org>
Date:   2016-09-14T22:34:50Z

    ARTEMIS-734 adding tests showing the issue on expiring while inside the cluster bridge

commit bb7c09de2b2177c11414381669baa252ccec3711
Author: Vlado Pakan <vpakan@redhat.com>
Date:   2016-09-14T22:43:34Z

    ARTEMIS-734 Message expired while being moved on the cluster bridge does not follow the
address setting configuration.

commit f65111128a89a1f7878a6d6c8d5aa63d9a3eb47b
Author: Clebert Suconic <clebertsuconic@apache.org>
Date:   2016-09-14T22:51:13Z

    ARTEMIS-734 small improvement: use ActiveMQScheduledComponent

----


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

Mime
View raw message