Loading...

XML

Word

Printable

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

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Target Release:

7.2.z.GA
Git Pull Request:
https://github.com/wildfly/jboss-ejb-client/pull/407, https://github.com/wildfly/jboss-ejb-client/pull/408

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

The EJB client is eagerly creating connections to available cluster nodes up to a maximum value defined in EJBClientContext which is hardcoded to a maximum value of '10'.

It is not possible to overwrite this value. Even the legacy configuration remote.cluster.ejb.max-allowed-connected-nodes does not work.

clones

EJBCLIENT-305 Unable to configure 'maximumConnectedClusterNodes'

Resolved

is cloned by

JBEAP-15407 [GSS](7.1.z) Unable to configure 'maximumConnectedClusterNodes'

Closed

is incorporated by

JBEAP-17073 [GSS](7.2.z) Upgrade jboss-ejb-client from 4.0.20 to 4.0.23

Closed

is related to

JBEAP-16543 [GSS](7.2.z) WFLY-11819 - max-allowed-connected-nodes element in jboss-ejb-client.xml not used

Closed

Assignee:: Tomas Hofman

Reporter:: Ilia Vassilev

Votes:: 0 Vote for this issue

Watchers:: 9 Start watching this issue

Created:: 2018/09/14 7:59 AM

Updated:: 2024/09/02 3:23 PM

Resolved:: 2019/08/06 1:19 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates