[jboss-jira] [JBoss JIRA] (WFLY-10150) EJB race condition can cause client to be in awaitResponse while server is done

[Lin Gao (JIRA)]

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

Lin Gao moved JBEAP-14527 to WFLY-10150:
----------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-10150  (was: JBEAP-14527)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: EJB
                           (was: EJB)
    Affects Version/s:     (was: 7.1.1.GA)
        Fix Version/s:     (was: 7.1.3.GA)


> EJB race condition can cause client to be in awaitResponse while server is done
> -------------------------------------------------------------------------------
>
>                 Key: WFLY-10150
>                 URL: https://issues.jboss.org/browse/WFLY-10150
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB
>            Reporter: Lin Gao
>            Assignee: JBoss SET
>
> With a client jboss server1 that has a client servlet that invokes a remote EJB on jboss server2 configured using server to server config in the standalone.xml/domain.xml outbound remoting connection, the client side can get stuck in awaitResponse while the server side has finished processing.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)