Uploaded image for project: 'EJB Client Library (AS7+)'
  1. EJB Client Library (AS7+)
  2. EJBCLIENT-33

Implement a timeout on EJB client invocations

XMLWordPrintable

      IMHO a client must support a timeout. Very often when things go wrong the clients get stuck indefinitely.

      Maybe this problem go even deeper, something on the server failed but didnt reply to the client. This is often encoutered during failover undeploy test (50 of 200 clients got stuck ).

      "Runner - 16" daemon prio=10 tid=0x00007fb7a0025000 nid=0x4d7a in Object.wait() [0x00007fb78b3f2000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:485)
        at org.jboss.ejb.client.EJBClientInvocationContext.awaitResponse(EJBClientInvocationContext.java:330)
        - locked <0x00000006c013ae50> (a java.lang.Object)
        at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:140)
        at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
        at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
        at $Proxy0.getSerialAndIncrement(Unknown Source)
        at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
        at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
        at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
        at java.lang.Thread.run(Thread.java:662)

              jaikiran Jaikiran Pai (Inactive)
              rhn-engineering-rhusar Radoslav Husar
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: