]
Jarosław Przygódzki updated WFLY-14196:
---------------------------------------
Attachment: WFLY-14196-stacktrace.txt
Some remote EJB invocations are slower when one of the initial
cluster nodes is down
------------------------------------------------------------------------------------
Key: WFLY-14196
URL:
https://issues.redhat.com/browse/WFLY-14196
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 21.0.1.Final
Reporter: Jarosław Przygódzki
Assignee: Paul Ferraro
Priority: Major
Attachments: WFLY-14196-stacktrace.txt
When one of the initial cluster nodes becomes unavailable, every 5 seconds one of the
remote invocations takes few seconds longer.
It seems that the delay is introduced by _DiscoveryEJBClientInterceptor_ that tries to
connect to node that's not available and blocks until connection attempt fails.
From what I've gathered, it looks like an unintended consequence of EJBCLIENT-309,
because the slower call happens exactly when failed destination in
RemotingEJBDiscoveryProvider expires, and increasing
_org.jboss.ejb.client.destination-recheck-interval_ makes slower invocations to happen
less frequently, matching _destination-recheck-interval_ value.