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...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER7
: EAP 6.2.0
Assignee: Stuart Douglas
QA Contact: Jan Martiska
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 1023602
TreeView+ depends on / blocked
 
Reported: 2013-10-16 15:09 UTC by Brad Maxwell
Modified: 2018-12-03 20:18 UTC (History)
2 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:20:07 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-2320 0 Major Resolved EJB should not be remotely accessible until all of its dependencies have been started 2016-12-08 09:04:20 UTC

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.


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