Connection reset by peer during EJB invocations

[raphy78626]

Hi All,

We have built an application which has components deployed across two wildfly instances (Main & Slave) on different physical servers. These two components talk to each other using EJB.

#1 - The Main server enlists all registered slaves from a database and connects to each using Scoped EJB context periodically and executes some EJB methods. This runs in a managed scheduled executor at a specified interval.

#2 - Each slave needs to communicate to the Main server to fulfill requests. As part of the above request the slave invokes different EJB on the Main server to fetch some data. This is done using the approach mentioned here - EJB invocations from a remote server instance - WildFly 8 - Project Documentation Editor.

Now in one of our slaves (running on a Mac) the above sequence fails. Below are trace logs from Main Server and Slave server. We also see "Connection reset by peer" logs on the Slave server in jboss console.

Appreciate if someone could help us on this. We have been trying to figure the cause since 3 days almost.

Thanks in advance,

Syed Md Rafi

Message was edited by: rafi syed Please find the slave logs

[croco]

Your slave server log is empty. Do you have a firewall between this machines?

[raphy78626]

1. Please find attached slave logs.

2. We dont have any firewall inbetween its an open network.

[croco]

Your logs don't match. One is from 11. feb the other is from 14. feb.

Try this example if it works for you: jboss-eap-quickstarts/MainAppSContextBean.java at 6.4.x-develop · jboss-developer/jboss-eap-quickstarts · GitHub

Set up a scoped ejb connection manually instead configuring it inside standalone.xml. I have more or less the same situation as you do and I've done it on AS7 using manual scoped connection (as described in the upper example) and it works correctly.

You should also check this example app: https://github.com/wildfly/quickstart/tree/master/ejb-multi-server

Hope it helps.

[raphy78626]

Thanks Matija Vizintin for your kind reply, we will try it.