[jboss-jira] [JBoss JIRA] (WFLY-7300) OperationHandlers that register DeploymentProcessor should do it only on boot

[Thomas Diesler (JIRA)]

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

Thomas Diesler edited comment on WFLY-7300 at 12/12/16 7:00 AM:
----------------------------------------------------------------

The commit associated with https://github.com/wildfly/wildfly/pull/9445 breaks wildfly-camel integration.

{code}
12:32:16,285 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit.arquillian-service.INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.arquillian-service.INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "arquillian-service"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
	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)
Caused by: java.lang.NullPointerException
	at org.wildfly.extension.batch.jberet.deployment.BatchDeploymentResourceProcessor.deploy(BatchDeploymentResourceProcessor.java:66)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
	... 5 more
{code}

It seems that arbitrary deployments can cause an NPE in BatchDeploymentResourceProcessor although they are not relevant to the batch subsystem.

CrossRef: https://github.com/wildfly-extras/wildfly-camel/issues/1531


was (Author: thomas.diesler):
The commit associated with https://github.com/wildfly/wildfly/pull/9445 breaks wildfly-camel integration.

{code}
12:32:16,285 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit.arquillian-service.INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit.arquillian-service.INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "arquillian-service"
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
	at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
	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)
Caused by: java.lang.NullPointerException
	at org.wildfly.extension.batch.jberet.deployment.BatchDeploymentResourceProcessor.deploy(BatchDeploymentResourceProcessor.java:66)
	at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
	... 5 more
{code}

It seems that arbitrary deployments can cause an NPE in BatchDeploymentResourceProcessor although they are not relevant to the batch subsystem

> OperationHandlers that register DeploymentProcessor should do it only on boot
> -----------------------------------------------------------------------------
>
>                 Key: WFLY-7300
>                 URL: https://issues.jboss.org/browse/WFLY-7300
>             Project: WildFly
>          Issue Type: Bug
>            Reporter: ehsavoie Hugonnet
>            Assignee: ehsavoie Hugonnet
>             Fix For: 11.0.0.Alpha1
>
>
> Registering a DeploymentProcessor is a boot only operation. Thus instead of extends AbstractAddStepHandler they should extend  AbstractBoottimeAddStepHandler



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)