Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-11819

max-allowed-connected-nodes element in jboss-ejb-client.xml not used

    XMLWordPrintable

Details

    Description

      An application uses remote-outbound-connections for remote EJB invocations and the jboss-ejb-client.xml contains a clusters definition containing the max-allowed-connected-nodes, like below:

      <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2">
        ...
        <clusters>
            <cluster name="ejb" ... max-allowed-connected-nodes="20">
            </cluster>
        </clusters>
    </client-context>
</jboss-ejb-client>

      In the actually used EJBClientContext this value doesn't get assigned and the hard coded default value of 10 is being used.

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16543 [GSS](7.2.z) WFLY-11819 - max-allowed-connected-nodes element in jboss-ejb-client.xml not used

          • 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.
          • Verified
          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-305 Unable to configure 'maximumConnectedClusterNodes'

          • 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 incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-16513 [GSS](7.2.z) WFLY-11819 - max-allowed-connected-nodes element in jboss-ejb-client.xml not used

          • 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

              rhn-support-jbaesner Joerg Baesner
              rhn-support-jbaesner Joerg Baesner
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: