[jboss-jira] [JBoss JIRA] (WFLY-2592) A server-to-server communication via outbound connection is not working

[Lin Gao (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12943798#comment-12943798 ] 

Lin Gao edited comment on WFLY-2592 at 2/12/14 5:46 AM:
--------------------------------------------------------

@ [~wdfink] , I tried your quickstarts following 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 at 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}

, and apply it to the 'server-client' server, the quickstarts works for me. (I tested against WildFly 8.0.0.CR1)

I changed the 'host' to the binding address of what the 'server-server' machine runs at.
And changed the protocol to 'http-remoting' explicitly, except you use the 'remote' protocol for ejb invocation for your 'server-server' server.

Would you please give another try to change the configureOutbound.cli for the 'server-client' server ? 
I think the host needs to be "192.168.27.38" in your case.
                
      was (Author: gaol):
    @ [~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 at 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.
                  
> A server-to-server communication via outbound connection is not working
> -----------------------------------------------------------------------
>
>                 Key: WFLY-2592
>                 URL: https://issues.jboss.org/browse/WFLY-2592
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: EJB, Remoting
>    Affects Versions: 8.0.0.Beta1
>            Reporter: Wolf-Dieter Fink
>            Assignee: David Lloyd
>            Priority: Critical
>              Labels: ejb, remoting
>         Attachments: networktraffic, server-client.log, server-server.log
>
>
> A ejb invocation from a SLSB is configured similar to AS7 (EAP6) to call a remote server fail in WildFly with the ERROR message " EJBCLIENT000025: No EJB receiver available for handling".
> The logfiles of client(server) and remote-server are attached, also a WireShark dump of the related network traffic.
> A standalone client at the same machine is able to call the remote application.

--
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