[
https://issues.redhat.com/browse/WFLY-11808?page=com.atlassian.jira.plugi...
]
Cheng Fang commented on WFLY-11808:
-----------------------------------
name space context is more related to batch envrionment than to job operator. So I think
{{BatchEnvironmentService}} is probably a better place to handle name space context
selection. Maybe compare the current thread's name space context with the deployment
one, and switch if differ.
Unable to do jndi lookup when starting batch job from web console
-----------------------------------------------------------------
Key: WFLY-11808
URL:
https://issues.redhat.com/browse/WFLY-11808
Project: WildFly
Issue Type: Bug
Components: Batch
Affects Versions: 16.0.0.Final
Reporter: Cheng Fang
Assignee: Cheng Fang
Priority: Major
Attachments: Default Task Thread.png, External Management Request Thread.png,
Screen Shot 2019-03-04 at 10.38.47 PM.png
when starting a batch job from web console, jndi lookup inside the application's
batch artifacts failed with NameNotFoundException. When the same job is started by the
application, the lookups all go well. Need to check if the naming context is properly
propagated when starting job from the web console.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)