Bug 922339 - Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler (client)
Summary: Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMess...
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: wfink
QA Contact:
Depends On:
Blocks: 922340
TreeView+ depends on / blocked
Reported: 2013-03-16 10:20 UTC by wfink
Modified: 2018-12-01 16:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 922340 (view as bug list)
Last Closed:
Type: Bug

Attachments (Terms of Use)
Maven project to reproduce the issue (18.06 KB, application/zip)
2013-03-16 10:20 UTC, wfink
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6086 0 Major Resolved Deadlock in org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler 2015-09-16 02:09:18 UTC

Description wfink 2013-03-16 10:20:01 UTC
Created attachment 711015 [details]
Maven project to reproduce the issue

Description of problem:

The MethodInvocationMessageHandler doesn't catch java.lang.IllegalArgumentException.
This causes the server hangs.

How reproducible:
A simple reproducer based on the ejb-remote quickstart is attached

Steps to Reproduce:
1. compile and deploy the project (mvn clean install jboss-as:deploy)
2. run the client 
   java -cp target/classes:../server-side/target/jboss-as-ejb-remote-app-client.jar:../../jboss/bin/client/jboss-client.jar org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient

Actual results:
Client hung

Expected results:
Exception at client side that the marshalling failed

Comment 1 wfink 2013-03-16 10:23:55 UTC
Problem is solved in EAP6.1.Alpha

Comment 2 Jan Martiska 2013-03-26 14:30:31 UTC
The fix is present in 6.1.0.ER3. This bug is not marked as ON_QA, but I will close it anyway; if there are concerns, please add comments.

Note You need to log in before you can comment on or make changes to this bug.