1 Reply Latest reply on Jul 14, 2015 4:46 AM by k koushik

    Jboss AS 7.2 EJB client Error Operation Failed with status waiting

    k koushik Newbie

      Hi all,

      I have an application which runs of Jboss 7.2.  Ejb client for this application is failing with error

      java.lang.RuntimeException: Operation failed with status WAITING

      java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:dcnm, moduleName:all-app, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@78657ce

           

      After  further debugging with enabling the TRACE on Jboss remoting and xnio we could see that the application is taking around 20 seconds to set the channel listener. as in below logs

       

      2015-07-13  12:54:43,099 TRACE [org.xnio.listener] (Remoting "openglab-pc-linux2" read-1) Setting channel listener to Read listener for org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <393922b8>

      2015-07-13  12:54:43,099 TRACE [org.xnio.listener] (Remoting "openglab-pc-linux2" read-1) Setting channel listener to Write listener for org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <393922b8>

      2015-07-13  12:54:43,099 TRACE [org.xnio.listener] (Remoting "openglab-pc-linux2" read-1) Setting channel listener to Close listener for org.xnio.channels.FramedMessageChannel around TCP socket channel (NIO) <393922b8>

      2015-07-13  12:54:43,100 TRACE [org.xnio.channels.framed] (Remoting "openglab-pc-linux2" read-1) Created new framed message channel around TCP socket channel (NIO) <393922b8>, receive buffer Pooled wrapper around java.nio.HeapByteBuffer[pos=0 lim=8196 cap=8196], transmit buffer Pooled wrapper around java.nio.HeapByteBuffer[pos=0 lim=8196 cap=8196]

      2015-07-13  12:55:03,116 TRACE [org.xnio.listener] (Remoting "openglab-pc-linux2" read-1) Setting channel listener to org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener@9ea9a4d

       

      Can any body please help me in trouble shooting this? what could be the cause in so much of the delay?

      This behavior is observed in one of the production setup and is consistent.

       

      Any help is very much appreciated