-
Enhancement
-
Resolution: Done
-
Major
-
4.0.48.Final, 5.0.1.Final
Currently discovery.timeout and discovery.additional-node-timeout have a default timeout of 0 , so they will not timeout.
We should consider setting a default value for these, definitely for discovery.additional-node-timeout , so that EJB invocations can start happening when a node is connected and not get stuck waiting until all clusters nodes are connected.
- causes
-
EJBCLIENT-493 Verbose DISCOVERY_ADDITIONAL_TIMEOUT logging during EJB discovery
- Resolved
- is incorporated by
-
JBEAP-24376 [GSS](7.4.z) EJBCLIENT-485 - Set default value for discovery.additional-node-timeout
- Closed
-
WFLY-17457 Upgrade jboss-ejb-client from 4.0.49.Final to 4.0.50.Final
- Closed