Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 4.0.3.Final
    • Labels:
      None

      Description

      If a client use the legacy jboss-ejb-client.properties and configure Deployment and ClusterNodeSelector neither of it is invoked.

      jboss-ejb-client.xml is like this:
      remote.connectionprovider.create.options.org.xnio.Options.SSL_ENABLED=false
      deployment.node.selector=org.jboss.wfink.eap71.playground.client.legacy.TestNodeSelector
      remote.connections=one

      remote.connection.one.host=localhost
      remote.connection.one.port = 8080
      remote.connection.one.username = user1
      remote.connection.one.password = user1+

      remote.clusters=ejb
      remote.cluster.ejb.clusternode.selector=org.jboss.wfink.eap71.playground.client.legacy.TestNodeSelector
      remote.cluster.ejb.username = user1
      remote.cluster.ejb.password = user1+

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jason.greene Jason Greene
                Reporter:
                wdfink Wolf-Dieter Fink
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: