[ https://issues.jboss.org/browse/AS7-5592?page=com.atlassian.jira.plugin.s... ] Adam Kovari commented on AS7-5592: ---------------------------------- I think reproducer for AS7-4274 can be used here too. I managed to get the same thread dumps in EAP 6.0.0. -- 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

[ https://issues.jboss.org/browse/AS7-5592?page=com.atlassian.jira.plugin.s... ] Adam Kovari edited comment on AS7-5592 at 9/21/12 9:24 AM: ----------------------------------------------------------- I think reproducer for AS7-4274 can be used here too. I managed to get the same thread dumps in EAP 6.0.0 and AS 7.2.0 Alpha 1. was (Author: adam.kovari): I think reproducer for AS7-4274 can be used here too. I managed to get the same thread dumps in EAP 6.0.0. -- 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

[ https://issues.jboss.org/browse/AS7-5592?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-5592: ----------------------------------- Those of you running into this issue against the latest community edition version of AS7, could you please follow these steps and see if it works for you: 1) Download the 3.2.10.GA version of jboss-remoting from here https://repository.jboss.org/nexus/content/groups/public/org/jboss/remoti... 2) Copy this jboss-remoting-3.2.10.GA.jar to JBOSS_AS7_HOME/modules/org/jboss/remoting3/main 3) Open the JBOSS_AS7_HOME/modules/org/jboss/remoting3/main/module.xml in a file editor and change the following line in it: {code} <resource-root path="jboss-remoting-3.2.8.SP1.jar"/> {code} to {code} <resource-root path="jboss-remoting-3.2.10.GA.jar"/> {code} 4) (Re)start the server. 5) If these steps were followed correctly, then you'll notice the console log to show the remoting version as follows: {quote} 15:05:56,945 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.10.GA {quote} Once that's verified, now you can test out the same application that you have been running into issues with. Let us know if it works fine and/or if you run into other issues. -- 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

[ https://issues.jboss.org/browse/AS7-5592?page=com.atlassian.jira.plugin.s... ] Bartosz Sabik edited comment on AS7-5592 at 9/28/12 8:03 AM: ------------------------------------------------------------- It's better but not quite good. When exception is thrown on client side during deserialization, remoting hangs until client's jvm is killed. Since client jvm is killed everthing is back to normal, client calls works smoothly again. Nothing never hangs with remoting-3.2.6.GA though any exceptions on client side during deserializations. It is better because with 3.2.8 or 3.2.3 it hangs indefinitely nevertheless client jvm kills. was (Author: bartosz.sabik): It's better but not quite good. When exception is thrown on client side during deserialization, remoting hangs until client's jvm is killed. Since client jvm is killed everthing is back to normal, client calls works smoothly again. Nothing never hangs with remoting-3.2.6.GA though any exceptions on client side during deserializations. It is better because with 3.2.6 or 3.2.3 it hangs indefinitely nevertheless client jvm kills. -- 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

[ https://issues.jboss.org/browse/AS7-5592?page=com.atlassian.jira.plugin.s... ] 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. -- 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