Bug 920316 - OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop
Summary: OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: DR1
: ---
Assignee: Jaikiran Pai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-11 19:26 UTC by Brad Maxwell
Modified: 2013-10-23 23:02 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EJBCLIENT-67 0 Blocker Resolved OOME (Threads) if scoped EJB context (EJBCLIENT-34) is used with lookups in a loop 2014-07-25 13:24:27 UTC

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
Note You need to log in before you can comment on or make changes to this bug.