GitHub user clebertsuconic opened a pull request:

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

    a few fixes

    

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

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

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

    https://github.com/apache/activemq-artemis/pull/1451.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 #1451
    
----
commit f293ff522961e3cf71600e79a89c8421db49d49b
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-09T00:30:39Z

    ARTEMIS-1308 Removing start/endcall around commit
    
    this issue many warning around the testsuite around MessageListeners
    it's valid to call the commit from a different thread on this case.

commit 4e6033ea21ea98aadacb9b7d241dc2c8af0a64a8
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-08T20:00:01Z

    ARTEMIS-1334 Scheduled component shouldn't be synchronized

commit af8246d739cd996e43a42dbfd3d3cdde89b1fa89
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-09T00:38:26Z

    NO-JIRA Adding large message failover test around duplicates

commit 8933b0060351ec00242920885f6b189ea96e4de7
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-09T02:39:20Z

    ARTEMIS-1333 SendACK listener message loss (adding test)
    
    next commit should have the fix.
    this is to make it easy to confirm the fix by people looking.

commit 9e1721e2a0b257af10047fca4b7915be74e664e0
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-09T02:48:25Z

    ARTEMIS-1333 SendACK listener fix

commit 75abedf928941b4a46ee986a12180d11d7ba8a8a
Author: Clebert Suconic <clebertsuco...@apache.org>
Date:   2017-08-09T02:55:11Z

    Revert "NO-JIRA Adding large message failover test around duplicates"
    
    This reverts commit af8246d739cd996e43a42dbfd3d3cdde89b1fa89.

----


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

Reply via email to