-
Bug
-
Resolution: Done
-
Major
-
4.0.37.Final
-
None
In the fix https://github.com/wildfly/jboss-ejb-client/pull/470 for JBEAP-18321 new EJB client timeout was introduced using the property `org.jboss.ejb.client.discovery.additional-node-timeout`. It defines how long to wait if at least one node has already been discovered. It seems this timeout works only for the first invocation and when the cluster is established the discovery is blocking again. This is consistent with the behavior of the 7.2.9 one-off, which should resolved the issues for the customer.
- is cloned by
-
JBEAP-20666 [GSS](7.3.z) EJBCLIENT-398 org.jboss.ejb.client.discovery.additional-node-timeout works only for the first invocation
- Closed
- is related to
-
EJBCLIENT-356 EJB client API blocks invocation until all configured connections are established/discovered
- Resolved