[
https://issues.jboss.org/browse/WFLY-11819?page=com.atlassian.jira.plugin...
]
Jörg Bäsner updated WFLY-11819:
-------------------------------
Environment: (was: In a cluster with used {{remote-outbound-connections}} for
remote EJB invocations and a {{clusters}} definition containing the
{{max-allowed-connected-nodes}}, like:
{code}
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2">
...
<clusters>
<cluster name="ejb" ...
max-allowed-connected-nodes="1">
</cluster>
</clusters>
</client-context>
</jboss-ejb-client>
{code})
max-allowed-connected-nodes element in jboss-ejb-client.xml not used
--------------------------------------------------------------------
Key: WFLY-11819
URL:
https://issues.jboss.org/browse/WFLY-11819
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 16.0.0.Final
Reporter: Jörg Bäsner
Assignee: Jörg Bäsner
Priority: Major
An application uses {{remote-outbound-connections}} for remote EJB invocations and the
{{jboss-ejb-client.xml}} contains a {{clusters}} definition containing the
{{max-allowed-connected-nodes}}, like below:
{code}
<jboss-ejb-client xmlns="urn:jboss:ejb-client:1.2">
...
<clusters>
<cluster name="ejb" ...
max-allowed-connected-nodes="20">
</cluster>
</clusters>
</client-context>
</jboss-ejb-client>
{code}
In the actually used {{EJBClientContext}} this value doesn't get assigned and the
hard coded default value of _10_ is being used.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)