Bug 920316

Summary:	OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	EJB	Assignee:	Jaikiran Pai <jpai>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	dimitris, jmartisk, rsvoboda, wfink
Target Milestone:	DR1
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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:

Description Brad Maxwell 2013-03-11 19:26:20 UTC

Using the scoped EJB context to tie the client context to the jndi context will cause out of memory is used for lookup in a loop.

 org.jboss.ejb.client.scoped.context : Boolean value (false). If set to true it will enable scoped EJB client context (introduced in AS7.2) which will be tied to the JNDI context, otherwise the EJB client context will use the global selector in the JVM to determine the properties to call the remote EJB and host. 

OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop 
https://issues.jboss.org/browse/EJBCLIENT-67

Allow Map based InitialContext configuration for ejb:
https://issues.jboss.org/browse/EJBCLIENT-34

Comment 1 Jan Martiska 2013-03-19 13:15:44 UTC

I hit the same issue with 6.1.0.ER2 too. Adding jboss-eap-6.1.0 flag.

Comment 2 Jan Martiska 2013-03-26 16:04:24 UTC

Verified in 6.1.0.ER3.

Comment 6 mark yarborough 2013-07-23 18:43:52 UTC

Details inside vpn: https://post-office.corp.redhat.com/mailman/private/eap-pm-list/2013-July/msg00105.html