Jeremy Whiting created AS7-3928: ----------------------------------- Summary: Could not register a EJB receiver for connection. Key: AS7-3928 URL: https://issues.jboss.org/browse/AS7-3928 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.1.Final Environment: Linux running on a 64 bit system. OpenJDK 6. Reporter: Jeremy Whiting Assignee: jaikiran pai Priority: Critical When invoking an EJB from a remote client the call throws an error. The error reports a timeout when waiting for an EJB receiver to be setup. There are no exceptions on the EJB server. This is the error Message: Could not register a EJB receiver for connection to remote://burtha02-wireless:4447 Details: Host Sequence Date Millis f16lite 5 2012-02-24T17:24:59 1330104299204 Logger: org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector Thread Class Method 10 org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector setupEJBReceivers Exception: Message: java.lang.RuntimeException: Operation failed with status WAITING Stack Trace: Class Method Line org.jboss.ejb.client.remoting.IoFutureHelper get 93 org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector setupEJBReceivers 115 org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector <init> 77 org.jboss.ejb.client.EJBClientContext <clinit> 76 org.jboss.ejb.client.EJBInvocationHandler doInvoke 120 org.jboss.ejb.client.EJBInvocationHandler invoke 104 $Proxy29 setPropertyOnDB org.spec.jent.driver.MfgDriver initializeRunConfig 166 org.spec.jent.driver.MfgDriver initializeAndAudit 131 sun.reflect.NativeMethodAccessorImpl invoke0 sun.reflect.NativeMethodAccessorImpl invoke 57 sun.reflect.DelegatingMethodAccessorImpl invoke 43 java.lang.reflect.Method invoke 616 com.sun.faban.driver.engine.AgentThread invokePrePost 414 com.sun.faban.driver.engine.AgentThread preRun 347 com.sun.faban.driver.engine.TimeThread doRun 87 com.sun.faban.driver.engine.AgentThread run 202 This had been working on versions prior to 7.1.Final. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira