Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.3.6.CR1, 7.3.6.GA
Affects Version/s: 7.3.3.GA
Component/s: EJB
Labels:
- test_included

Blocked:
False
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Release Note Text:
Undefined
Target Release:

7.3.z.GA
Git Pull Request:
https://github.com/wildfly/jboss-ejb-client/pull/497, https://gitlab.cee.redhat.com/ejb/jboss-ejb-client/-/merge_requests/473
Steps to Reproduce:

Hide

Follow the reproducer for ~~EJBCLIENT-356~~.

Show
Follow the reproducer for EJBCLIENT-356 .
Market:

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

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.

clones

EJBCLIENT-398 org.jboss.ejb.client.discovery.additional-node-timeout works only for the first invocation

Resolved

is incorporated by

JBEAP-20762 [GSS](7.3.z) Upgrade jboss-ejb-client from 4.0.37.Final-redhat-00001 to 4.0.39.SP1-redhat-00001

Closed

relates to

JBEAP-18321 [GSS](7.3.z) EJBCLIENT-356 - EJB client API blocks invocation until all configured connections are established/discovered

Verified

Assignee:: Tomas Hofman

Reporter:: Daniel Cihak

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2020/12/07 6:27 AM

Updated:: 2022/09/09 7:13 AM

Resolved:: 2021/01/29 2:44 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates

Hide