- 
        1. Re: Could not register a EJB receiver for connection to remotejayasiv Jan 8, 2013 2:52 PM (in response to jayasiv)Happend couple of times in the last one week. I have a webservice application running too inside the same server and that works fine. Its the client sever communincation that fails. Any suggestions? 
- 
        2. Re: Could not register a EJB receiver for connection to remotewill.tatam Jan 23, 2013 7:07 PM (in response to jayasiv)I've just seen this for the first time too. App was working fine, then suddenly stopped with this error. Restart of AS fixed it Any ideas what triggers it or potential fixes Though I'm not seeing the error you mention in my server log though 
- 
        3. Re: Could not register a EJB receiver for connection to remotejaikiran Jan 23, 2013 11:28 PM (in response to will.tatam)If you are using 7.1.1.Final, then I would suggest that you try against the latest nightly build https://community.jboss.org/thread/167590 and see if it works there. There were some bugs fixed after 7.1.1.Final was released. With whatever little information is contained in this thread, I can't say if you are running into those bugs. 
- 
        4. Re: Could not register a EJB receiver for connection to remotewill.tatam Jan 24, 2013 5:33 AM (in response to jaikiran)The problem is so far we have seen this error only once in weeks of use, so we could try running a nightly for several days testing and never see the issue, but that would not prove that the fault is resolved 
- 
        5. Re: Could not register a EJB receiver for connection to remoteolli24 Oct 1, 2013 8:00 AM (in response to jayasiv)Hi jayasiv We faced a similiar problem: 2013-09-30 11:33:00.756 ERROR [Remoting "config-based-ejb-client-endpoint" read-1] org.jboss.remoting.remote.connection - JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host 2013-09-30 11:33:00.766 WARN [thread applet-WebTerminal.mtTerminalApplet-1] org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector - Could not register a EJB receiver for connection to remote://xxxx01:9000 java.lang.RuntimeException: java.io.IOException: An existing connection was forcibly closed by the remote host at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:91) at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.setupEJBReceivers(ConfigBasedEJBClientContextSelector.java:121) at org.jboss.ejb.client.remoting.ConfigBasedEJBClientContextSelector.<init>(ConfigBasedEJBClientContextSelector.java:78) at org.jboss.ejb.client.EJBClientContext.<clinit>(EJBClientContext.java:77) at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:120) at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) at $Proxy0.create(Unknown Source) see https://community.jboss.org/message/839562#839562 Did you find already the root cause? Thanks, Oliver 
- 
        6. Re: Could not register a EJB receiver for connection to remotejayasiv Dec 4, 2013 2:41 PM (in response to olli24)Still having the same problem but the frequency it occurs is reduced. We have two production servers and i configured the ejb client property file to use both the servers. I see the following error message in my log file at several different times. JBREM000200: Remote connection failed: java.io.IOException: An existing connection was forcibly closed by the remote host 
- 
        7. Re: Could not register a EJB receiver for connection to remoteolli24 Dec 9, 2013 2:39 AM (in response to jayasiv)We also still have the problem approx. once 1 month. We have migrated to EAP 6.1.0.Alpha1 (AS 7.2.0) to see if the problem still occurs. 
 
     
     
    