Client hangs on remote EJB calls during network / power outage in EAP 7 / 6

Solution Verified - Updated -

Issue

  • A client will be blocked if a network connection to the server is broken or the server machine has power loss. Client only continues after network timeout.
  • EJB client connections appear to be hanging in the event of a network/power outage.
    • Standalone client -> 2-Server Domain (SLSB)
    • vm1: server-1
    • vm2: server-2
    • vm3: standalone Java standalone client
    • The Java standalone client connected to the two servers as defined in jboss-ejb-client.properties and is load balancing between those two servers. When we execute a power-off on one of vms i.e. vm2 running server-2, the client continues to send requests only server-1 & server-2 (which was powered down). As a result the client gets totally blocked and receives an invocation timeout exception after 31s ("No invocation response received in 31000 milliseconds").
      After the restart of vm2, the client terminates without notice.
    • The same test worked well using a (clustered) stateful SessionBean (SFSB)

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 7.0 CP4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content