[
https://issues.apache.org/jira/browse/ARTEMIS-474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241988#comment-15241988
]
ASF GitHub Bot commented on ARTEMIS-474:
----------------------------------------
GitHub user clebertsuconic opened a pull request:
https://github.com/apache/activemq-artemis/pull/463
ARTEMIS-474 and ARTEMIS-484
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/clebertsuconic/activemq-artemis master-work
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/463.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 #463
----
commit 406ac233143099527993e189d7c0744005ee4dca
Author: Clebert Suconic <[email protected]>
Date: 2016-04-04T22:36:36Z
ARTEMIS-465 Changing Byteman race on test
commit e34a7cc8bb0dedfae62f74df1bce06ea7b838422
Author: Clebert Suconic <[email protected]>
Date: 2016-04-06T16:58:50Z
ARTEMIS-474 Avoiding one lock around the readyListener call tree and fixing
ReplicationManager / NettyConnection deadlock
commit 5b1f185a3e66160e0a4bef960a0e36378006988b
Author: Clebert Suconic <[email protected]>
Date: 2016-04-07T19:53:52Z
ARTEMIS-474 fixing page.close() deadlock with replica
commit ae6e5f3669b7e7a614853f3bf100e450162fc676
Author: Clebert Suconic <[email protected]>
Date: 2016-04-14T17:24:46Z
ARTEMIS-484 Large Message Loss on Initial replication
https://issues.apache.org/jira/browse/ARTEMIS-484
The File copy after the initial synchronization on large messages was
broken.
On this commit we fix how the buffer is cleaned up before each read since
a previously unfinished body read would make the buffer dirty.
I'm keeping also lots of Traces I have added to debug this issue, so they
will
be useful if anything like this happens again.
commit 10a35a084623eff9ef9c360c4be3d6120c19a1a1
Author: Clebert Suconic <[email protected]>
Date: 2016-04-14T21:51:18Z
ARTEMIS-474 Clustering fails on certain topologies
Communication between nodes will fail under certain topologies
JGroups has something called JForkChannel that could be used on container
systems.
And be injected into Artemis.
For some reason that channel cannot be reused for more than one channel per
VM.
And it cannot ever be closed.
I am keeping the trace logs I used to debug this issue in case anything
similar to this happens again.
----
> replication fails with colocated topologies
> -------------------------------------------
>
> Key: ARTEMIS-474
> URL: https://issues.apache.org/jira/browse/ARTEMIS-474
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Fix For: 1.3.0
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
