JBeret WildFly extension cannot handle runtime-name
cornhoolio22 Nov 14, 2016 5:47 AMHello,
I experienced a NullPointerException, when I use a runtime-name for a batch job. I tried it with the nightly build from Friday the 11th of November.
Steps to reproduce the error:
I used the javaee7-samples
git clone git clone https://github.com/javaee-samples/javaee7-samples.git cd javaee7-samples/util && mvn clean install cd ../test-utils && mvn clean install cd .. && mvn clean install --projects . cd batch/chunk-csv-database/ && mvn clean package -DskipTests=true
Then I deployed with
deploy javaee7-samples/batch/chunk-csv-database/target/batch-chunk-csv-database.war --runtime-name=some-other-name.war
The CLI command causing the error:
/deployment=batch-chunk-csv-database.war/subsystem=batch-jberet/job=myJob:read-resource(include-runtime=true)
The stacktrace
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 13) WFLYCTL0013: Operation ("read-attribute") failed - address: ([ ("deployment" => "batch-chunk-csv-database.war"), ("subsystem" => "batch-jberet"), ("job" => "myJob") ]): java.lang.NullPointerException at org.wildfly.extension.batch.jberet.deployment.JobOperationStepHandler.execute(JobOperationStepHandler.java:68) at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecuteInternal(ReadAttributeHandler.java:174) at org.jboss.as.controller.operations.global.ReadAttributeHandler.doExecute(ReadAttributeHandler.java:137) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:230) at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AvailableResponseWrapper.execute(GlobalOperationHandlers.java:988) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:921) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:664) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:383) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1364) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:416) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:237) at org.wildfly.security.auth.client.PeerIdentity.runAsAll(PeerIdentity.java:431) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:206) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:237) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:217) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$400(ModelControllerClientOperationHandler.java:137) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:161) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) at org.wildfly.security.auth.client.PeerIdentity.runAsAll(PeerIdentity.java:464) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:225) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:185) at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:157) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at org.jboss.threads.JBossThread.run(JBossThread.java:320)
The problem here is also reproduceable when opening the deployments in the HTTP-Management Interface. So it is not possible anymore to open http://localhost:9990/console/App.html#standalone-deployments .
Hi hope I got the correct forum here for my post.
So my questions here are: Are runtime-names for deployments containing batch jobs supported? And is there a workaround to use them anyway?
Thx in advance for any helpful hint.
Best Regards,
Markus