[
https://issues.apache.org/jira/browse/ARTEMIS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933370#comment-16933370
]
Francesco Nigro commented on ARTEMIS-2496:
------------------------------------------
Here some instructions to help reproducing the issue:
* clone https://github.com/ehsavoie/wildfly/tree/WFLY-12304
* change on pom.xml
<version.org.apache.activemq.artemis>2.11.0-SNAPSHOT</version.org.apache.activemq.artemis>
or whatever version of artemis we want to test
* be sure that the artemis broker referenced above is isntalled in the mvn repo
ie run on it $ mvn -Pdev -DskipTest clean install
* run on widfly $ mvn -DskipTest clean install
* run the attached script on wildfly ./runTillFails.sh
> 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
>
> Attachments: runTillFails.sh
>
> Time Spent: 2h
> 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)
