[jboss-jira] [JBoss JIRA] (WFLY-11819) max-allowed-connected-nodes element in jboss-ejb-client.xml not used

[Ilia Vassilev (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilia Vassilev updated WFLY-11819:
---------------------------------
    Labels: downstream_dependency  (was: )


> 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: Joerg Baesner
>            Assignee: Joerg Baesner
>            Priority: Major
>              Labels: downstream_dependency
>             Fix For: 17.0.0.Beta1
>
>
> 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)