[GitHub] activemq pull request #197: https://issues.apache.org/jira/browse/AMQ-6391

[pdudits <gi...@git.apache.org>]

GitHub user pdudits opened a pull request:

    https://github.com/apache/activemq/pull/197

    https://issues.apache.org/jira/browse/AMQ-6391

    Test case for multiple connections participating in one phase commit,
    causing leak in ConnectionStateTracker.
    
    Keep all the connections participating in an transaction in a static multimap
    similar to the one in TransactionContext.
    
    Even though Garry  says that static fields may cause issues in OSGi, I am offering this as a solution. This static map has same lifecycle, classloading and  source bundle as the one already present in TransactionContext, therefore I assume it cannot really make things worse.

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

    $ git pull https://github.com/pdudits/activemq amq-6391

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

    https://github.com/apache/activemq/pull/197.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 #197
    
----
commit 1c36bac35f7ad9ccb4b7dd9f981dc915e78947ea
Author: Patrik Dudits <pa...@dudits.net>
Date:   2016-08-09T14:41:46Z

    https://issues.apache.org/jira/browse/AMQ-6391
    
    Test case for multiple connections participating in one phase commit,
    causing leak in ConnectionStateTracker.
    
    Keep all the connections participating in an transaction in a static multimap
    similar to the one in TransactionContext.

----


---
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.
---