[jboss-jira] [JBoss JIRA] (WFLY-2592) A server-to-server communication via outbound connection is not working
David Lloyd (JIRA)
issues at jboss.org
Wed Feb 5 16:06:29 EST 2014
[ https://issues.jboss.org/browse/WFLY-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12941669#comment-12941669 ]
David Lloyd commented on WFLY-2592:
-----------------------------------
The only difference is that it's on a different port. Something like iptables can easily come into play, and it matches your symptoms pretty much exactly, so that would be the first thing to check - the TCP retransmits seem to indicate that the network layer isn't even getting the packets, long before WildFly or EAP would have a chance to touch the data.
> 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
More information about the jboss-jira
mailing list