1 2 3 Previous Next 34 Replies Latest reply on Oct 17, 2012 10:13 AM by jaikiran pai

    7.1.2.Final Is there a timeout for inbound connnections?

    jkreska Newbie

      I have a remote ejbClient that is getting an InvocationTargetException with the cause exception

       

      Caused by: java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:testmodule, moduleName:xxi-framework-test-module-ejb, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@f0d9cd
              at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:583)
              at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:112)
              at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181)
              at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
              at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
              at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
      

       

      After a couple of minutes of inactivity

       

      The server log

       

      12:37:17,891 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "jb7-3" read-1) Channel Channel ID 47b0c640 (inbound) of Remoting connection 576d3e6a to /192.168.12.85:50891 closed.
      12:37:17,891 INFO  [org.jboss.as.naming] (Remoting "jb7-3" task-2) JBAS011806: Channel end notification received, closing channel Channel ID 47b0c640 (inbound) of Remoting connection 576d3e6a to /192.168.12.85:50891
      12:37:17,892 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "jb7-3" read-1) Channel Channel ID 048107bf (inbound) of Remoting connection 576d3e6a to /192.168.12.85:50891 closed
      12:37:17,919 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "jb7-3" task-1) Channel Opened - Channel ID 222dcad4 (inbound) of Remoting connection 23c85761 to /192.168.12.85:46427
      12:37:17,921 DEBUG [org.jboss.naming.remote.server.RemoteNamingService] (Remoting "jb7-3" task-2) Chosen version 0x01
      12:37:17,927 DEBUG [org.jboss.as.ejb3.remote.EJBRemoteConnectorService] (Remoting "jb7-3" task-1) Client with protocol version 1 and marshalling strategy river trying to communicate on Channel ID 6896b9b7 (inbound) of Remoting connection 23c85761 to /192.168.12.85:46427
      12:37:17,928 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "jb7-3" task-1) Sending initial module availability message, containing 4 module(s) to channel Channel ID 6896b9b7 (inbound) of Remoting connection 23c85761 to /192.168.12.85:46427
      12:37:17,928 DEBUG [org.jboss.as.ejb3.remote.protocol.versionone.VersionOneProtocolChannelReceiver] (Remoting "jb7-3" task-1) Writing out cluster formation message for 1 clusters, to channel Channel ID 6896b9b7 (inbound) of Remoting connection 23c85761 to /192.168.12.85:46427
      12:37:17,930 DEBUG [com.xxi.framework.moduleproxy.JBoss7SynchronousProxy] (EJB default - 6) Calling remote method public abstract com.xxi.framework.locationfindermodule.api.data.CityLocation com.xxi.framework.locationfindermodule.api.LocationModuleAPI.getCity(java.lang.String) Using args [DFW]
      12:37:17,931 INFO  [com.xxi.framework.jbossaux.cluster.RoundRobinClusterNodeSelector] (EJB default - 6) Calling RoundRobin with jboss7-test-server1-ejb ConnectedNodes: [jb7-2, jb7-1] AvailableNodes: [jb7-2, jb7-1]
      

       

      I can't tell what is triggering the disconnect.  It only seems to happen when I am running in a remote web container (resin), a standalone java app does not seem to reproduce the behavior.

       

      I am looking up the ejb in JNDI at servlet init and then using the ejb on each web request.  If a web request cauese the webapp to restart, deployment changed, then the disconnect happens as soon as the request makes the ejb call.  i.e.  the servlet init cached it fine and the first call fails.

        1 2 3 Previous Next