[
https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin....
]
Wolf-Dieter Fink commented on WFLY-2592:
----------------------------------------
What you mean by remoting (native) is there a difference for the configuration of the
outbound-connection (I did not found any hint in the docs).
Not 100% sure, but there should be no firewall in between and I've used
ejb-multi-server example before which include outbound-connection and scoped-context for
the same ejb-ejb invocation.
The scoped context works fine with the same ports.
Maybe I need to enlarge my example a bit and use scoped-context as well, but again is
there a difference regarding (native) remoting?
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