[jboss-jira] [JBoss JIRA] (WFLY-6104) Too many invocations to a remote EJB from multiple threads cause infinite wait

[Tomas Hofman (JIRA)]

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

Tomas Hofman moved JBEAP-3122 to WFLY-6104:
-------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-6104  (was: JBEAP-3122)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: Remoting
                           (was: Remoting)
       Target Release:   (was: 7.0.0.GA)
    Affects Version/s: 10.0.0.Final
                           (was: 7.0.0.ER4)


> Too many invocations to a remote EJB from multiple threads cause infinite wait
> ------------------------------------------------------------------------------
>
>                 Key: WFLY-6104
>                 URL: https://issues.jboss.org/browse/WFLY-6104
>             Project: WildFly
>          Issue Type: Bug
>          Components: Remoting
>    Affects Versions: 10.0.0.Final
>            Reporter: Tomas Hofman
>            Assignee: Tomas Hofman
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1302181
>   While a thread (1) of EJB client invokes a remote EJB which needs long
>   processing time and wait for the response, if the other threads complete
>   more than 65536 invocations to the remote EJB, EJBCLIENT000011 message like
>   below occurs in EJB client side and the waiting thread (1) falls into
>   infinite wait for the response.
>     INFO: EJBCLIENT000011: Discarding result for invocation id 0 since no
>     waiting context found
>   All invocations should successfully complete regardless of the number of
>   invocations.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)