[jboss-jira] [JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console
Michal Petrov (Jira)
issues at jboss.org
Fri Aug 7 15:52:00 EDT 2020
[ https://issues.redhat.com/browse/WFLY-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368688#comment-14368688 ]
Michal Petrov commented on WFLY-11808:
--------------------------------------
I'm afraid I don't see how. We need to switch the context for the {{start-job}} operation but as far as I can see {{BatchEnvironmentService}} does not care about any operations being executed. Moreover the deployment also uses the default context, it's only getting switched during a server request from the app, since we're using CLI there is no such request. I'm basically trying to copy the context switching process that normally happens when you start the job from the app.
By the way what is the purpose of {{NamespaceContextHandle}}? I can see it is switching the context but for one it's doing it too late (i.e. after the lookups) and secondly it's simply reinserting the current context into the queue.
> 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: Michal Petrov
> 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)
More information about the jboss-jira
mailing list