Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-307

Only able to configure a custom ClusterNodeSelector using legacy 'jboss-ejb-client.properties'

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • None
    • 4.0.11.Final
    • None

    Description

      A custom ClusterNodeSelector can only be configured using jboss-ejb-client.properties as below:

      remote.clusters=ejb
      remote.cluster.ejb.clusternode.selector=org.jboss.playground.PlaygroundClusterNodeSelector

      Due to that this legacy file is required even when using only jndi.properties or InitialContext programmatically.

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-315 Allow to configure DeploymentNodeSelector and ClusterNodeSelector in 'wildfly-config.xml'

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-15465 [GSS](7.2.z) Only able to configure a custom DeploymentNodeSelector / ClusterNodeSelector using legacy 'jboss-ejb-client.properties'

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is incorporated by

          Feature Request - Feature requests from customers and/or users JBEAP-15408 [GSS](7.1.z) Only able to configure a custom DeploymentNodeSelector / ClusterNodeSelector using legacy 'jboss-ejb-client.properties'

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: