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

[GSS](7.3.z) EJBCLIENT-398 org.jboss.ejb.client.discovery.additional-node-timeout works only for the first invocation

    XMLWordPrintable

Details

    Description

      In the fix https://github.com/wildfly/jboss-ejb-client/pull/470 for JBEAP-18321 new EJB client timeout was introduced using the property `org.jboss.ejb.client.discovery.additional-node-timeout`. It defines how long to wait if at least one node has already been discovered. It seems this timeout works only for the first invocation and when the cluster is established the discovery is blocking again. This is consistent with the behavior of the 7.2.9 one-off, which should resolved the issues for the customer.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. EJBCLIENT-398 org.jboss.ejb.client.discovery.additional-node-timeout works only for the first invocation

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-20762 [GSS](7.3.z) Upgrade jboss-ejb-client from 4.0.37.Final-redhat-00001 to 4.0.39.SP1-redhat-00001

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-18321 [GSS](7.3.z) EJBCLIENT-356 - EJB client API blocks invocation until all configured connections are established/discovered

          • 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

          Activity

            People

              thofman Tomas Hofman
              dcihak@redhat.com Daniel Cihak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: