[
https://issues.apache.org/jira/browse/ARTEMIS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932934#comment-16932934
]
ASF subversion and git services commented on ARTEMIS-2496:
----------------------------------------------------------
Commit 70c2200c54066eb6d9f1d0235aae5c3bbf5b7412 in activemq-artemis's branch
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=70c2200 ]
ARTEMIS-2496 Revert catch up with zero-copy, as it's causing issues into some
integration usage
Revert "ARTEMIS-2336 Use zero copy to replicate journal/page/large message file"
This reverts commit 85b93f0883bc06a2dfe2de9d560805a59d626d38.
> Use of Netty FileRegion on ReplicationCatch is breaking wildfly integration
> with artemis
> ----------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2496
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2496
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.10.0
> Reporter: clebert suconic
> Assignee: clebert suconic
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> This is of course an issue on Wildfly integration, but it seems something on
> our recent changes is breaking replication on Wildfly.
> My biggest concern is that it seems that paging catch up is silently failing
> in our testsuite and some other issues are currently hidden.
> Wildfly has an extra layer on top of Netty:
> https://github.com/xnio/netty-xnio-transport/tree/0.1
> But the main thing here, is that it seems that are other issues within
> Artemis.
> For now I'm reverting the change from ARTEMIS-2336
> And we need more investigation to bring it back
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
