Bug 1359884

Summary:	[GSS](6.4.z) EJBs accessible too early (spec violation) - part 3 - (supplementation)
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	EJB	Assignee:	Fedor Gavrilov <fgavrilo>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.9	CC:	cdewolf, david.lloyd, fgavrilo, jbilek, jtruhlar, msochure, wfink
Target Milestone:	CR1
Target Release:	EAP 6.4.11
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 13:13:03 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:	1350355
Bug Blocks:	1361648, 1379471, 1389428

Description Brad Maxwell 2016-07-25 15:41:23 UTC

Follow up to: https://bugzilla.redhat.com/show_bug.cgi?id=1350355

Prior to changes, when a remote external EJB client tried to invoke an EJB such as a SLSB which was in an app with a Singleton which was not yet finished PostConstruct, the remote client would get an EJBCLIENT000025.  After the bug fixes it now is not getting the exception.  We need to keep it consistent since it was working that way for the previous 6.x releases:

java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:ejb-client, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@2473d930

Comment 1 Fedor Gavrilov 2016-08-23 14:36:57 UTC

https://github.com/jbossas/jboss-eap/pull/2829

Comment 9 Jiří Bílek 2016-10-04 15:31:57 UTC

Verified with EAP 6.4.11.CP.CR1

Comment 10 Petr Penicka 2017-01-17 13:13:03 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.