[ https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin.... ] Lin Gao commented on WFLY-2592: ------------------------------- @ [~wdfink] , I tried your quickstarts as what you described in the reproduce steps. and if I made the changes to the configureOutbound.cli in the ejb-remote-server module, like: {code:} [lgao@dhcp-192-139 ejb-remote-server]$ git diff diff --git a/ejb-remote-server/configureOutbound.cli b/ejb-remote-server/configureOutbound.cli index dfc4d25..6f58d81 100644 --- a/ejb-remote-server/configureOutbound.cli +++ b/ejb-remote-server/configureOutbound.cli @@ -9,10 +9,10 @@ batch # Configure the connection from this server to the standard one # # add the socket binding to the full-sockets, used by the app-main server -/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-ejb:add(host=localhost, port=8080) +/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=remote-ejb:add(host=192.168.100.173, port=8080) # add the outbound connections to the remoting subsystem of the full-profile used by app-main server -/subsystem=remoting/remote-outbound-connection=remote-ejb-connection:add(outbound-socket-binding-ref=remote-ejb, security-realm=ejb-security-realm, username=quickuser1) +/subsystem=remoting/remote-outbound-connection=remote-ejb-connection:add(outbound-socket-binding-ref=remote-ejb, security-realm=ejb-security-realm, username=quickuser1, protocol=http-remoting) /subsystem=remoting/remote-outbound-connection=remote-ejb-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false) /subsystem=remoting/remote-outbound-connection=remote-ejb-connection/property=SSL_ENABLED:add(value=false) {code} , the quickstarts works for me. (I tested against WildFly 8.0.0.CR1) Because for WildFly 8.0.0.CR1, I think the ejb will use the http-remoting by default. For EAP6, the remoting socket-binding (port 4447) will be used by default. Would you please give another try to change the configureOutbound.cli for the second server ? I think the host needs to be "192.168.27.38" in your case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira