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

[Cheng Fang (Jira)]

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

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

Starting a batch job operation from web console follows a different path than starting a batch job by application.  The following is the stack trace for management-initiated batch job execution:

{code}
"External Management Request Threads -- 1 at 16187" prio=5 tid=0xa0 nid=NA runnable
  java.lang.Thread.State: RUNNABLE
	  at org.wildfly.extension.batch.jberet.deployment.JobOperatorService.start(JobOperatorService.java:219)
	  at org.wildfly.extension.batch.jberet.deployment.BatchDeploymentResourceDefinition$1.execute(BatchDeploymentResourceDefinition.java:105)
	  at org.wildfly.extension.batch.jberet.deployment.JobOperationStepHandler.executeRuntime(JobOperationStepHandler.java:75)
	  at org.wildfly.extension.batch.jberet.deployment.JobOperationStepHandler$$Lambda$979.35215319.execute(Unknown Source:-1)
	  at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
	  at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
	  at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
	  at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412)
	  at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423)
	  at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243)
	  at org.jboss.as.controller.ModelControllerImpl$$Lambda$631.1055034970.run(Unknown Source:-1)
	  at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$632.1532149905.run(Unknown Source:-1)
	  at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289)
	  at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255)
	  at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243)
	  at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212)
	  at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72)
	  at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93)
	  at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62)
	  at org.jboss.as.domain.http.server.security.ElytronIdentityHandler$$Lambda$977.1385167113.run(Unknown Source:-1)
	  at org.wildfly.security.auth.server.SecurityIdentity$$Lambda$978.2116813432.run(Unknown Source:-1)
	  at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313)
	  at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270)
	  at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254)
	  at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225)
	  at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61)
	  at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56)
	  at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364)
	  at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)
	  at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	  at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
	  at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
	  at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
	  at java.lang.Thread.run(Thread.java:834)
	  at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}

> Unable to do jndi lookup when starting batch job from web console
> -----------------------------------------------------------------
>
>                 Key: WFLY-11808
>                 URL: https://issues.jboss.org/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: 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.12.1#712002)