Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1131252

Summary:	[GSS] (6.3.1) EJB threads hang waiting to respond to client
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	EJB	Assignee:	Brad Maxwell <bmaxwell>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.3.0	CC:	bbaranow, jmartisk, myarboro, rdickens, schaudha
Target Milestone:	CR1	Keywords:	Triaged
Target Release:	EAP 6.3.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1131207	Environment:
Last Closed:	2014-10-13 18:38:05 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:
Embargoed:
Bug Depends On:	1131207
Bug Blocks:	1102082, 1104255, 1132696

Description Brad Maxwell 2014-08-18 19:21:40 UTC

+++ This bug was initially created as a clone of Bug #1131207 +++

When using a standalone client to make EJB calls to EAP it seems that those threads can get stuck in an indefinite wait state. This occurs when the client hits invocation.timeout. The server continues processes the request and that thread lingers waiting to return a respond to the client, which is no longer listening. This looks similar to EJBCLIENT-42, but not quite the same. I will attach a reproducer which was created from a quickstart. Note that when the client is killed, the server side throws various exceptions for all threads, including the writes closed exception.

Comment 3 Jan Martiska 2014-08-28 12:24:18 UTC

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