[jboss-jira] [JBoss JIRA] (AS7-3601) Component context not available on spawned threads
Johannes Odland (JIRA)
jira-events at lists.jboss.org
Fri Feb 3 08:37:48 EST 2012
Johannes Odland created AS7-3601:
------------------------------------
Summary: Component context not available on spawned threads
Key: AS7-3601
URL: https://issues.jboss.org/browse/AS7-3601
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.0.CR1b
Reporter: Johannes Odland
Assignee: John Bailey
When a request is processed, the JavaNamespaceSetup pushes an InjectedEENamespaceContextSelector onto a ThreadLocalStack, making the app and component contexts available for lookups through InitialContext().lookup().
As a result, the application and component contexts are only available on the same thread as the request, and not on threads spawned by the application itself.
Many applications, such as Solr, spawns its own threads for doing asynchronous processing. These are not able to access the JNDI component context (java:comp/env/).
Perhaps one should use InheritableThreadLocal to store the selector instead?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list