You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/14 23:01:20 UTC
[jira] [Commented] (ARTEMIS-734) Message expired while being moved
on the cluster bridge does not follow the address setting configuration
[ https://issues.apache.org/jira/browse/ARTEMIS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15491688#comment-15491688 ]
ASF GitHub Bot commented on ARTEMIS-734:
----------------------------------------
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 <cl...@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 <vp...@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 <cl...@apache.org>
Date: 2016-09-14T22:51:13Z
ARTEMIS-734 small improvement: use ActiveMQScheduledComponent
----
> Message expired while being moved on the cluster bridge does not follow the address setting configuration
> ---------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-734
> URL: https://issues.apache.org/jira/browse/ARTEMIS-734
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: clebert suconic
> Fix For: 1.5.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)