Bug 1019894 – EJB should not be remotely accessible until all of its dependencies have been started

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

Bug 1019894 - EJB should not be remotely accessible until all of its dependencies have been started

Summary:	EJB should not be remotely accessible until all of its dependencies have been...

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	unspecified Severity unspecified
Target Milestone:	ER7
Target Release:	EAP 6.2.0
Assigned To:	Stuart Douglas
QA Contact:	Jan Martiska
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1023602
	Show dependency tree / graph

Reported:	2013-10-16 11:09 EDT by Brad Maxwell
Modified:	2014-05-26 21:27 EDT (History)
CC List:	2 users (show)

See Also:
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 11:20:07 EST
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	WFLY-2320	Major	Resolved	EJB should not be remotely accessible until all of its dependencies have been started	2016-12-08 04:04 EST

Groups: None (edit)

Description Brad Maxwell 2013-10-16 11:09:27 EDT

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 17:53:29 EDT

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

Comment 7 Jan Martiska 2013-11-05 07:55:59 EST

Verified in 6.2.0.ER7.

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