Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-12161

EJB client 4.x: failover is not working with the legacy configuration out of the box

    XMLWordPrintable

    Details

      Description

      New EJB 4.x client needs to work with jboss-ejb-client.properties EJB client configuration out of the box.

      At this moment, Clustered affinity needs to be set manually in order to make failover working.

      used jboss-ejb-client.properties:

      remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
      remote.connections=node1,node2
      #invocation.timeout=120000
      
      remote.connection.node1.host=${address.cluster1-node1}
      remote.connection.node1.port=8080
      remote.connection.node1.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
      remote.connection.node1.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=30000
      
      remote.connection.node2.host=${address.cluster1-node2}
      remote.connection.node2.port=8080
      remote.connection.node2.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
      remote.connection.node2.channel.options.org.jboss.remoting3.RemotingOptions.MAX_OUTBOUND_MESSAGES=30000
      
      remote.clusters=ejb
      
      remote.cluster.ejb.connect.options.org.xnio.Options.SASL_POLICY_NOANONYMOUS=false
      remote.cluster.ejb.connect.options.org.xnio.Options.SASL_POLICY_NOPLAINTEXT=false
      remote.cluster.ejb.connect.options.org.xnio.Options.WORKER_TASK_MAX_THREADS=4
      

      Link to test case:
      http://git.app.eng.bos.redhat.com/git/jbossqe/eap-tests-ejb.git/tree/ejb-multi-server-ts/src/test/java/org/jboss/qa/ejb/tests/failover/SimpleStatefulBeanFailoverLegacyConfigurationTestCase.java#n85

      Link to jenkins job results:
      https://eap-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/eap-7x-ejb-multi-server-testsuite/7/testReport/org.jboss.qa.ejb.tests.failover.beans/SimpleStatefulBeanFailoverLegacyConfigurationTestCase/testSimpleFailover_undeploy/

      Customer impact:
      Customers migrating from EAP 7.0 who are using legacy-style EJB client configuration in a clustered environment will have to either switch to the legacy client library (which we generally discourage) or apply a workaround requiring changes in the application code. These changes also mean bringing compile-time dependency on JBoss-specific classes which might be an issue for customers who can't or don't want to introduce this.

        Attachments

          Activity

            People

            Assignee:
            dlloyd@redhat.com David Lloyd
            Reporter:
            mvinkler1@redhat.com Michal Vinkler
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: