Bug 1067194 – [GSS] (6.3.1) EJB3 client code swallows exceptions making it difficult to track down issues in production.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1067194 - [GSS] (6.3.1) EJB3 client code swallows exceptions making it difficult to track down issues in production.

Summary:	[GSS] (6.3.1) EJB3 client code swallows exceptions making it difficult to tra...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	EJB (Show other bugs)
Sub Component:
Version:	6.1.0
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	CR1
Target Release:	EAP 6.3.1
Assigned To:	baranowb
QA Contact:	Jan Martiska
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:	Triaged

Depends On:	1118892
Blocks:	1127593 eap631-blockers/eap631-payload/eap63-cp01-blockers 1104255
	Show dependency tree / graph

Reported:	2014-02-19 17:48 EST by dstephan
Modified:	2014-10-13 14:38 EDT (History)
CC List:	7 users (show)

See Also:
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:
Clones:	1118892 (view as bug list)
Environment:
Last Closed:	2014-10-13 14:38:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	EJBCLIENT-106	Major	Resolved	EJB3 client code swallows exceptions making it difficult to track down issues	2016-10-12 10:34 EDT

Groups: None (edit)

Description dstephan 2014-02-19 17:48:01 EST

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):
jboss-ejb-clien-1.0.21

Comment 2 baranowb 2014-08-08 02:39:54 EDT

PR merged: https://issues.jboss.org/browse/EJBCLIENT-106

Shifting to 'MODIFIED'

Comment 4 Jan Martiska 2014-08-28 06:58:06 EDT

Verified in EAP 6.3.1.CR1 / ejb client 1.0.26.Final

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