[
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 with 3.2.10 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.8 or 3.2.3 it hangs indefinitely nevertheless client jvm
kills.
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&pa...).
--
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