-
1. Re: EJB server-to-server handshake silence
jaikiran Jun 6, 2014 2:50 AM (in response to pbenedict)Which exact version of WildFly is this? Enable TRACE level logging of org.jboss.ejb.client on the server which is acting as the client (and maybe even on the other server) and see if it shows up something. There's usually a WARN logged when the connection fails.
-
2. Re: Re: EJB server-to-server handshake silence
pbenedict Jun 6, 2014 11:28 AM (in response to jaikiran)I am using 8.1.0.CR2 on both machines. I added this line to each server's standalone.xml:
<logger category="org.jboss.ejb.client"> <level name="TRACE"/> </logger>
Nothing logged on the client side. For the server, this was spit out. I don't know if it's related though:
DEBUG [org.jboss.ejb.client.txn] (Periodic Recovery) Send recover request for transaction origin node identifier 1 to EJB receiver with node name www
Does that help at all?
-
3. Re: EJB server-to-server handshake silence
wdfink Jun 6, 2014 1:32 PM (in response to pbenedict)Did you add a remoting connector for this protocol? The default is http-remoting
-
4. Re: EJB server-to-server handshake silence
pbenedict Jun 6, 2014 10:42 PM (in response to wdfink)Okay, I solved the issue but I can confirm what I originally thought: WildFly does not log anything when the handshake cannot be made. My problem was on the destination server side. That server's WildFly instance was bound to localhost (not the external IP) which prevented it from accepting incoming connections from the outside. Once I changed the bound address, I was able to make a handshake.
I am going to go ahead and create a new JIRA issue for this [1]. I think it's a defect -- not an enhancement -- because what should be a reported error must be swallowed somewhere. BTW, errors do get reported with things such as bad remoting messages or incorrect authentication, for example, but not if the handshake fails.
[1] [WFLY-3466] No error reported when remote handshake fails - JBoss Issue Tracker