No response from remote for outbound association. Associate timed out after [15000 ms]

329 views Asked by At

Does anyone know why do we get association errors?

I have a server and client system where actors from the client-side send messages to the server actor through Akka remoting and both server and client are on the same local machine but using different ports.

Error on the server client side:

[ERROR][12/1/2020 3:59:28 AM][Thread 0021][akka.tcp://RemoteSystem@localhost:8876/system/transports/akkaprotocolmanager.tcp.0/akkaProtocol-tcp%3A%2F%2FRemoteSystem%40localhost%3A8080-1] No response from remote for outbound association. Associate timed out after [15000 ms].
[WARNING][12/1/2020 3:59:28 AM][Thread 0019][remoting (akka://RemoteSystem)] Tried to associate with unreachable remote address [akka.tcp://RemoteSystem@localhost:8080]. Address is now gated for 5000 ms, all messages to this address will be delivered to dead letters. Reason: [Association failed with akka.tcp://RemoteSystem@localhost:8080] Caused by: [System.TimeoutException: No response from remote for outbound association. Associate timed out after [15000 ms].   
   at Akka.Remote.Transport.AkkaProtocolTransport.Associate(Address remoteAddress, Nullable`1 refuseUid)
   at Akka.Remote.EndpointWriter.AssociateAsync()]

Error on server side:

[ERROR][12/1/2020 3:53:29 AM][Thread 0020][akka.tcp://RemoteSystem@localhost:8080/system/transports/akkaprotocolmanager.tcp.0/akkaProtocol-tcp%3A%2F%2FRemoteSystem%40%5B%3A%3Affff%3A127.0.0.1%5D%3A57235-1] No response from remote for 
inbound association. Handshake timed out after [15000] ms

My understanding is that handshake is not achieved from client to server.

When I work with 20 client actors sending messages to the server and waiting for the reply it works but with more than 25 it does not work.

Any help will be appreciated.

0

There are 0 answers