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

[Jason Greene (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619081#comment-13619081 ] 

Jason Greene commented on WFLY-10150:
-------------------------------------

We need to look at including this patch by David:

https://github.com/dmlloyd/jboss-remoting/commit/8ca5f1c1c03a7bd7f64010e9091ad04249ca6932

> 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
>              Labels: downstream_dependency
>
> 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)