[jboss-jira] [JBoss JIRA] (AS7-5592) Regression: EJB remote invocations hang indefinitely due to possible remoting issues

[Wolf-Dieter Fink (JIRA)]

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

Wolf-Dieter Fink commented on AS7-5592:
---------------------------------------

I use the ejb-deadlock example of AS7-4274 to reproduce it.
I copy the project and add a 30sec delay after the Exception in the client class CustomerBeanClient.

If I replace the remoting with 3.2.10.GA I can start the first exec and after I see the Exception at server side the client sleep in the code.
If I start the second client this call produce the same error.
So for me it looks like working nevertheless whether the client is still alive.
                
> Regression: EJB remote invocations hang indefinitely due to possible remoting issues
> ------------------------------------------------------------------------------------
>
>                 Key: AS7-5592
>                 URL: https://issues.jboss.org/browse/AS7-5592
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB, Remoting
>    Affects Versions: 7.1.2.Final (EAP), 7.2.0.Alpha1
>         Environment: AS7 upstream master
>            Reporter: jaikiran pai
>            Assignee: jaikiran pai
>            Priority: Critical
>         Attachments: td.txt
>
>
> Apparently the issue(s) reported in https://issues.jboss.org/browse/AS7-3975 (and https://issues.jboss.org/browse/AS7-4274) are back in AS7 upstream as well as 7.1.2 tag. The user who's running into this issue reports that it works fine with jboss-remoting 3.2.6.GA version but hangs in a later 3.2.8.SP1 version which is used in AS7 upstream master as well as 7.1.2 tag (https://issues.jboss.org/browse/AS7-3975?focusedCommentId=12720551&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12720551).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira