[ https://issues.jboss.org/browse/WFLY-11808?page=com.atlassian.jira.plugin... ] Cheng Fang edited comment on WFLY-11808 at 3/20/19 7:45 PM: ------------------------------------------------------------ The batch subsystem chose the name context for the batch job execution as follows: {code:java} org.jboss.as.naming.context.NamespaceContextSelector.getCurrentSelector(); {code} So for a job execution request from the management console or CLI, the current thread is "External Management Threads - 1", and its associated name context is used for batch job execution, but this name context has no knowlege of the deployment that contains the batch job. Any lookup of application resources done from any batch artifacts during the batch job execution will simply fail. See attached screenshot of external management request thread vs default task thread. was (Author: cfang): The batch subsystem chose the name context for the batch job execution as follows: {code:java} org.jboss.as.naming.context.NamespaceContextSelector.getCurrentSelector(); {code} So for a job execution request from the management console or CLI, the current thread is "External Management Threads - 1", and its associated name context is used for batch job execution, but this name context has no knowlege of the deployment that contains the batch job. Any lookup of application resources done from any batch artifacts during the batch job execution will simply fail. -- This message was sent by Atlassian Jira (v7.12.1#712002)