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

Bug 1019894

Summary:	EJB should not be remotely accessible until all of its dependencies have been started
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	EJB	Assignee:	Stuart Douglas <sdouglas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jan Martiska <jmartisk>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.1.1	CC:	brian.stansberry, myarboro
Target Milestone:	ER7
Target Release:	EAP 6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	In some situations EJBs could be remotely invoked before they were fully started, resulting in an unresponsive EJB client. This occurred because remote interfaces were bound before any dependencies of the EJB were fully resolved. Thus a bean could be invoked before it was fully able to respond. This has been fixed and an EJB's remote interfaces are not available until all of its dependencies have been resolved.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-15 16:20:07 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:
Bug Blocks:	1023602

Description Brad Maxwell 2013-10-16 15:09:27 UTC

If an EJB injects or depends on a resource such as an @Singleton which has not been started, the EJB's remote interface java:jboss/exported/* is already bound and this allows remote EJB clients to try to invoke it. This causes the EJB clients to hang because the EJB will not be started until its dependencies have been started.

Comment 3 JBoss JIRA Server 2013-10-25 21:53:29 UTC

Stuart Douglas <stuart.w.douglas> updated the status of jira WFLY-2320 to Resolved

Comment 7 Jan Martiska 2013-11-05 12:55:59 UTC

Verified in 6.2.0.ER7.