[
https://jira.jboss.org/jira/browse/EJBTHREE-1798?page=com.atlassian.jira....
]
jaikiran pai resolved EJBTHREE-1798.
------------------------------------
Fix Version/s: 1.1.4
Resolution: Done
The implementation of the JNDIKernelRegistryPlugin has been changed to return a
LazyJNDIKernelRegistryEntry - which does the JNDI lookup only when the
KernelRegistryEntry.getTarget() API is called.
JNDIKernelRegistryPlugin should not create proxies or sessions during
MC context state change
---------------------------------------------------------------------------------------------
Key: EJBTHREE-1798
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-1798
Project: EJB 3.0
Issue Type: Bug
Components: core
Affects Versions: 1.1.3
Reporter: jaikiran pai
Assignee: jaikiran pai
Fix For: 1.1.4
The JNDIKernelRegistryPlugin is to used for the jndi: dependencies (which is a MC
context) that are added to the EJB containers which are installed as MC beans. When MC
internally, changes the state of the contexts, there are multiple calls to the :
public KernelRegistryEntry getEntry(Object name)
API. The jndi: dependencies point to proxy factories bound to JNDI and when this API is
called it results in a JNDI lookup and a subsequent proxy/session creation. This needs to
be avoided
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira