You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (Jira)" <ji...@apache.org> on 2019/09/23 18:58:01 UTC

[jira] [Closed] (ARTEMIS-2496) Use of Netty FileRegion on ReplicationCatch is breaking wildfly integration with artemis

     [ https://issues.apache.org/jira/browse/ARTEMIS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-2496.
------------------------------------
    Resolution: Fixed

> 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 20m
>  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)