-
Bug
-
Resolution: Done
-
Major
-
7.1.0.DR7
-
None
Try deleting the definition of the ejb cache container from the default standalone.xml and running EAP, you will get
12:19:13,064 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 32) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]): java.lang.NullPointerException
at org.wildfly.clustering.server.dispatcher.LocalCommandDispatcherFactoryBuilder.build(LocalCommandDispatcherFactoryBuilder.java:69)
at org.jboss.as.ejb3.subsystem.EJB3RemoteServiceAdd.installRuntimeServices(EJB3RemoteServiceAdd.java:128)
at org.jboss.as.ejb3.subsystem.EJB3RemoteServiceAdd.performRuntime(EJB3RemoteServiceAdd.java:87)
at org.jboss.as.controller.AbstractAddStepHandler.performRuntime(AbstractAddStepHandler.java:337) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at org.jboss.as.controller.AbstractAddStepHandler$1.execute(AbstractAddStepHandler.java:151) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:940) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:683) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:382) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:368) [wildfly-controller-3.0.0.Alpha10-redhat-1.jar:3.0.0.Alpha10-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]
at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
This will fail even if you move the EJB passivation store to a different cache container (which exists). The dependency on "ejb" container seems to be hardcoded somewhere.
This is an issue for automated migration from EAP 6.4.0 because the standalone.xml config of 6.4.0 doesn't contain this cache container.
Seems to be related to changes in either JBEAP-6270 or JBEAP-6271