[jboss-jira] [JBoss JIRA] (WFLY-5850) Can't deploy an EJB to a WildFly 10 server migrated from 6.4

Can't deploy an EJB to a WildFly 10 server migrated from 6.4 ------------------------------------------------------------ Key: WFLY-5850 URL: https://issues.jboss.org/browse/WFLY-5850 Project: WildFly Issue Type: Bug Components: EJB Reporter: Ladislav Thon Priority: Blocker I just tried to migrate a {{standalone.xml}} server from clean EAP 6.4.0 to 7.0.0.ER3 and then deploy the {{server-side}} part of the {{ejb-remote}} quickstart: {code} git clone git@github.com:jboss-developer/jboss-eap-quickstarts.git cd jboss-eap-quickstarts/ git checkout -b 6.4.x origin/6.4.x cd ejb-remote/server-side/ mvn clean package -s ../../settings.xml cd target unzip .../jboss-eap-6.4.0.zip unzip .../jboss-eap-7.0.0.ER3.zip cp jboss-eap-6.4/standalone/configuration/standalone.xml jboss-eap-7.0/standalone/configuration/test.xml ./jboss-eap-7.0/bin/standalone.sh -c test.xml --admin-only # on a separate console ./jboss-eap-7.0/bin/jboss-cli.sh -c --controller=localhost:9999 /subsystem=threads:remove /extension=org.jboss.as.threads:remove /subsystem=web:migrate shutdown # on the original console cp jboss-ejb-remote-server-side.jar jboss-eap-7.0/standalone/deployments/ ./jboss-eap-7.0/bin/standalone.sh -c test.xml {code} What I get is this horrible stack trace: {code} 15:22:24,909 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jboss-ejb-remote-server-side.jar".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."jboss-ejb-remote-server-side.jar".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "jboss-ejb-remote-server-side.jar" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) [wildfly-server-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.6.Final-redhat-1.jar:1.2.6.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_66] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_66] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_66] Caused by: javax.validation.ValidationException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath. at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:271) at org.hibernate.validator.internal.cdi.ValidationExtension.<init>(ValidationExtension.java:109) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.8.0_66] at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [rt.jar:1.8.0_66] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.8.0_66] at java.lang.reflect.Constructor.newInstance(Constructor.java:422) [rt.jar:1.8.0_66] at java.lang.Class.newInstance(Class.java:442) [rt.jar:1.8.0_66] at org.jboss.as.weld.deployment.WeldPortableExtensions.tryRegisterExtension(WeldPortableExtensions.java:53) at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.loadAttachments(WeldPortableExtensionProcessor.java:121) at org.jboss.as.weld.deployment.processors.WeldPortableExtensionProcessor.deploy(WeldPortableExtensionProcessor.java:81) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) [wildfly-server-2.0.4.Final-redhat-1.jar:2.0.4.Final-redhat-1] ... 5 more 15:22:24,918 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jboss-ejb-remote-server-side.jar")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"jboss-ejb-remote-server-side.jar\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jboss-ejb-remote-server-side.jar\".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment \"jboss-ejb-remote-server-side.jar\" Caused by: javax.validation.ValidationException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath."}} {code} When I deploy the same JAR to a clean install of EAP 7.0.0.ER3, it works just fine. This suggests that something (probably the EJB subsystem?) doesn't correctly parse/serialize the legacy configuration. Or something like that.