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

[GSS](7.2.0) EJB client gets stuck in awaitResponse or AbstractHandleableCloseable when server is disconnected from network

    XMLWordPrintable

Details

    • Hide

      Set timeouts and heartbeat via wildfly-config.xml:

      <configuration>
    <endpoint xmlns="urn:jboss-remoting:5.0">
        <connections>
            <connection destination="remote+http://localhost:8080" read-timeout="11000" write-timeout="11000"
                        heartbeat-interval="1000"/>
        </connections>
    </endpoint>
</configuration>
      Show
      Set timeouts and heartbeat via wildfly-config.xml: <configuration> <endpoint xmlns= "urn:jboss-remoting:5.0" > <connections> <connection destination= "remote+http: //localhost:8080" read-timeout= "11000" write-timeout= "11000" heartbeat-interval= "1000" /> </connections> </endpoint> </configuration>
    • Hide

      use a standalone client to connect an EJB
      let the EJB take a bit time
      cut the network or power connection of this server

      Show
      use a standalone client to connect an EJB let the EJB take a bit time cut the network or power connection of this server

    Description

      1. A client will be blocked if a network connection to the server is broken or the server machine has power loss.
        The time until the client can continue seems the network timeout.

      org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:413)

      This is normally avoided by set
      connect.options.org.xnio.Options.READ_TIMEOUT
      connect.options.org.xnio.Options.KEEP_ALIVE"
      connect.options.org.jboss.remoting3.RemotingOptions.HEARTBEAT_INTERVAL

      But the properties don't make a difference for EAP7 client.

      if the property invocation.timeout is set the invocation failed and the client might continue if there are more servers or a cluster view.
      But it will stuck on exit if the connection should be closed at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:190)

      This is the same even if the server connector has changed from http-remoting to remoting.

      If the client use the EAP6.4.14 jboss-client.jar the properties take effect and the client will fail imediately - for sure the server use the old connector protocol -

      this will be a huge drawback in failover scenarios

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. XNIO-296 READ_TIMEOUT and WRITE_TIMEOUT options not set when opening new channel

          • 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-12670 [GSS](7.1.z) EJB client gets stuck in awaitResponse or AbstractHandleableCloseable when server is disconnected from network

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-11358 Upgrade XNIO to 3.5.0.Beta7

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

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-8577 [GSS](7.0.z) SSL EJB Client stuck in AbstractHandleableCloseable.close

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. JBEAP-13911 [EAT](7.1.z) Testcase for JBEAP-12670

          • 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

              dlloyd@redhat.com David Lloyd
              rhn-support-wfink Wolf Fink
              Richard Janik Richard Janik
              Richard Janik Richard Janik
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: