[jboss-jira] [JBoss JIRA] (WFLY-8652) TCPPING initial_hosts not configurable

[Paul Ferraro (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro moved JBEAP-10575 to WFLY-8652:
--------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8652  (was: JBEAP-10575)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Clustering
                       JMS
                           (was: Clustering)
                           (was: JMS)
    Affects Version/s: 11.0.0.Alpha1
                           (was: 7.1.0.DR16)
      Affects Testing:   (was: Regression)


> TCPPING initial_hosts not configurable
> --------------------------------------
>
>                 Key: WFLY-8652
>                 URL: https://issues.jboss.org/browse/WFLY-8652
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering, JMS
>    Affects Versions: 11.0.0.Alpha1
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>            Priority: Blocker
>
> *Scenario:*
> * There are two servers called "JMS servers"
> * There are two servers called "MDB servers"
> * JMS servers are configured to be in cluster. They have destinations and hold all messages.
> * MDB servers have MDB applications which connect remotely via resource adapter to JMS servers.
> * Resource adapter on MDB servers is configured to use Jgroups TCP ping discovery protocol to find JMS servers.
> *Expectation:* MDB applications on MDB servers are able to receive and sent messages from InQueue to OutQueue which are deployed on JMS servers.
> *Reality:* MDB applications don't receive any message.
> *Customer impact:* Customers which use aforementioned scenario with Jgroups TCP ping are affected. Their applications stop working after migration to EAP 7.1.
> This is regression against EAP 7.1.0.DR15. I tried to use both Artemis jars and messaging integration jars from DR15 but it didn't help. I saw the same issue. I compared JGroups versions between DR15 and DR16 but they are the same.
> There was also update of XNIO from 3.5.0.Beta2 to 3.5.0.Beta4 but I wasn't able to run the DR16 with 3.5.0.Beta2 because there was change in API.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)