[jboss-jira] [JBoss JIRA] (WFLY-11808) Unable to do jndi lookup when starting batch job from web console

Cheng Fang (Jira) issues at jboss.org
Mon Aug 10 00:16:00 EDT 2020


    [ https://issues.redhat.com/browse/WFLY-11808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14374620#comment-14374620 ] 

Cheng Fang commented on WFLY-11808:
-----------------------------------

We could pass {{EEModuleDescription}} to {{BatchEnvironmentService}} instead of {{JobOperatorService}}. In {{BatchEnvironmentService}} when we create {{NamespaceContextHandle}}, we can just use the selector from {{EEModuleDescription}}, by changing {{NamespaceContextHandle}} constructor to take the deployment's namespace selector, without using the one from the thread. This should work for job executions started from either application, or from management.

> 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