[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:comment-tabpanel&focusedCommentId=13766312#comment-13766312 ] 

Lin Gao commented on WFLY-10150:
--------------------------------

I tried with WildFly master(commit id: 2a124aa4658b987b69b3c6ecb71996196b547bbf) in my local machine following the reproduce steps, the jmeter scripts executed for over 50 minutes without stuck anymore, so I think it is fixed already in WildFly.

XNIO version: 3.7.2.Final
jboss-remoting: 5.0.12.Final


> 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: Tomasz Adamski
>            Priority: Major
>              Labels: downstream_dependency
>         Attachments: domain-mode-hung-logs.zip
>
>
> 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.12.1#712002)