GitHub user jkorab opened a pull request:
https://github.com/apache/activemq/pull/36
Fix for AMQ-5249
Approach to the change is described in
http://issues.apache.org/jira/browse/AMQ-5294?focusedCommentId=14077910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14077910
For some reason there is also a commit in this pull request that was
already merged (Added close destroy-method...), apologies something messed up
in the workflow.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jkorab/activemq trunk
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/36.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 #36
----
commit a92027691a8de2482e43ab33ed4e9dd0f7a24377
Author: Jakub Korab <[email protected]>
Date: 2014-04-03T10:36:24Z
Added close destroy-method to Postgres data source. Example crashed and
burned on master-slave failover when master lost network connectivity - took
down VM.
commit 039750805eec66fad2c273e7db5c15912acb272c
Author: jkorab <[email protected]>
Date: 2014-07-25T11:23:11Z
Merge branch 'trunk' of https://github.com/apache/activemq into trunk
commit ecedea34faee1e8c56daa4a7a9c40261cdba91fe
Author: jkorab <[email protected]>
Date: 2014-07-29T16:25:09Z
Fix for AMQ-5294. Refactored tool to unify timing of the samplers and
client (producer/consumer), in such a way that the performance test no longer
sits waiting for sampler to complete, even though the run terminated much
earlier. Full description of approach in
http://issues.apache.org/jira/browse/AMQ-5294?focusedCommentId=14077910&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14077910
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
