Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: 7.4.10.CR1, 7.4.10.GA
Affects Version/s: 7.4.8.GA
Component/s: EJB
Labels:
None

Blocked:
False
Blocked Reason:
None
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.4.z.GA
Git Pull Request:
https://github.com/wildfly/jboss-ejb-client/pull/599
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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

JBEAP-24818 [GSS](7.4.z) EJBCLIENT-493 - Verbose DISCOVERY_ADDITIONAL_TIMEOUT logging during EJB discovery

Closed

incorporates

EJBCLIENT-485 Set default value for discovery.additional-node-timeout

Resolved

is incorporated by

JBEAP-24395 [GSS](7.4.z) Upgrade jboss-ejb-client from 4.0.49.Final-redhat-00001 to 4.0.50.Final

Closed

is related to

EJBCLIENT-356 EJB client API blocks invocation until all configured connections are established/discovered

Resolved

Assignee:: Tomas Hofman

Reporter:: Brad Maxwell

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2022/12/20 4:11 PM

Updated:: 2024/08/19 1:58 PM

Resolved:: 2023/01/02 2:52 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates