Bug 1067194

Summary: [GSS] (6.3.1) EJB3 client code swallows exceptions making it difficult to track down issues in production.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: dstephan
Component: EJBAssignee: baranowb <bbaranow>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: high Docs Contact: Russell Dickenson <rdickens>
Priority: high    
Version: 6.1.0CC: bbaranow, bmaxwell, dstephan, jawilson, myarboro, smumford, wfink
Target Milestone: CR1Keywords: Triaged
Target Release: EAP 6.3.1   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Known Issue
Doc Text:
This release of JBoss EAP 6 carries a bug that causes EJB3 clients to swallow exceptions unless logging is set to DEBUG. This issue is expected to be resolved in a future release of the product.
Story Points: ---
Clone Of:
: 1118892 (view as bug list) Environment:
Last Closed: 2014-10-13 18:38:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1118892    
Bug Blocks: 1102082, 1104255, 1127593    

Description dstephan 2014-02-19 22:48:01 UTC
Description of problem:

Customer had great difficulty tracking down the root cause of the EJB client failure. It turned out to be a serialization exception.

The code in EJBInvocationHandler.sendRequestWithPossibleRetries swallows the exception in order to retry other nodes. However, with this serialization exception it was never going to work. 

The only way the customer could find the exception is to set DEBUG logging in production, which they find unacceptable.

Is it possible to return these exceptions up the stack to aid in troubleshooting?

Version-Release number of selected component (if applicable):

Comment 2 baranowb 2014-08-08 06:39:54 UTC
PR merged: https://issues.jboss.org/browse/EJBCLIENT-106

Shifting to 'MODIFIED'

Comment 4 Jan Martiska 2014-08-28 10:58:06 UTC
Verified in EAP 6.3.1.CR1 / ejb client 1.0.26.Final