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

[GSS](7.3.z) EJBCLIENT-356 - EJB client API blocks invocation until all configured connections are established/discovered

    XMLWordPrintable

Details

    • +
    • Hide 
      <configuration>
    <authentication-client xmlns="urn:elytron:1.0">
        ...
    </authentication-client>
    <jboss-ejb-client xmlns="urn:jboss:wildfly-client-ejb:3.2">
        <max-allowed-connected-nodes nodes="3" />
        <connections>
            <connection uri="remote+http://localhost:8080" />
            <connection uri="remote+http://localhost:8380" />
        </connections>
    </jboss-ejb-client>    

    <!-- default heartbeat-interval as below was introduced with JBoss EAP 7.2 CP3
     |
     |   see: https://access.redhat.com/solutions/4151781
     |
     |-->
    <endpoint xmlns="urn:jboss-remoting:5.1" read-timeout="2000" heartbeat-interval="1000">
        <connections>
            <connection destination="remote+http://localhost:8080" read-timeout="6000" write-timeout="6000" heartbeat-interval="3000" />
        </connections>
    </endpoint>
</configuration>
      Show
      <configuration> <authentication-client xmlns= "urn:elytron:1.0" > ... </authentication-client> <jboss-ejb-client xmlns= "urn:jboss:wildfly-client-ejb:3.2" > <max-allowed-connected-nodes nodes= "3" /> <connections> <connection uri= "remote+http: //localhost:8080" /> <connection uri= "remote+http: //localhost:8380" /> </connections> </jboss-ejb-client> <!-- default heartbeat-interval as below was introduced with JBoss EAP 7.2 CP3 | | see: https: //access.redhat.com/solutions/4151781 | |--> <endpoint xmlns= "urn:jboss-remoting:5.1" read-timeout= "2000" heartbeat-interval= "1000" > <connections> <connection destination= "remote+http: //localhost:8080" read-timeout= "6000" write-timeout= "6000" heartbeat-interval= "3000" /> </connections> </endpoint> </configuration>
    • Hide

      See README.md of the playground.zip of EJBCLIENT-356

      Show
      See README.md of the playground.zip of EJBCLIENT-356

    Description

      In case a standalone Java client is configured with a wildfly-config.xml that contain 2 connections like this:

      <configuration>
    ...
    <jboss-ejb-client xmlns="urn:jboss:wildfly-client-ejb:3.2">
        <max-allowed-connected-nodes nodes="3" />
        <connections>
            <connection uri="remote+http://localhost:8080" />
            <connection uri="remote+http://localhost:8380" />
        </connections>
    </jboss-ejb-client>
</configuration>

      And there's a cluster behind it with 3 nodes, the invocation to the first node is performed once all of these configured connections are established.

      If now establishing the connection to localhost:8080 takes 0.5 seconds and the establishing of the connection to localhost:8380 takes 10 seconds, the client block the invocation for 10 seconds.

      If the target nodes are running in a cluster and there's another 3rd node running (e. g. localhost:8680, then the 2nd invocation on the client is again blocked until the connection to localhost:8680 is established.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-17826 [GSS](7.2.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.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. 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.
          • Resolved
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-19790 [GSS](7.3.z) Upgrade jboss-ejb-client from 4.0.33.SP1-redhat-00001 to 4.0.37.Final-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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-20666 [GSS](7.3.z) 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.
          • Verified
          links to

          Web Link KCS

          Activity

            People

              istudens@redhat.com Ivo Studensky
              rhn-support-ivassile Ilia Vassilev
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: