简体繁体 English

部署后无法在Wildfly 11中启用kie-drools-wb-7.10.0.war

[英]Can't enable kie-drools-wb-7.10.0.war in wildfly 11 after deployment

原文 2018-10-12 14:32:50 9 1 optaplanner/ wildfly-11/ kie-wb

I went through the installation guide on https://docs.optaplanner.org/7.10.0.Final/optaplanner-wb-es-docs/html_single/#_planner.quickstart and on https://docs.optaplanner.org/latest/optaplanner-wb-es-docs/html_single/#_wildfly_11_x and did the steps desciped there but I can't enable the kie-wb deployment. 我在https://docs.optaplanner.org/7.10.0.Final/optaplanner-wb-es-docs/html_single/#_planner.quickstart和https://docs.optaplanner.org/latest上阅读了安装指南。 / optaplanner-wb-es-docs / html_single /＃_ wildfly_11_x ，并按照此处描述的步骤进行操作，但是我无法启用kie-wb部署。 I tried to install the kie-wb by copying it in the /standalone/deployments and by adding the kie-wb.war from the wildfly deployments GUI. 我试图通过在/ standalone / deployments中复制kie-wb并通过wildfly部署GUI添加kie-wb.war来安装它。

I start wildfly with 我从开始野蝇

./bin/standalone.sh --server-config=standalone-full.xml -Dorg.kie.server.user=planner -Dorg.kie.server.pwd=Planner123_ -Dorg.kie.server.controller.user=planner -Dorg.kie.server.controller.pwd=Planner123_ -Dorg.kie.server.id=wildfly-kieserver -Dorg.kie.server.location= http://localhost:8080/kie-server/services/rest/server -Dorg.kie.server.controller= http://localhost:8080/kie-wb/rest/controller ./bin/standalone.sh --server-config = standalone-full.xml -Dorg.kie.server.user = planner -Dorg.kie.server.pwd = Planner123_ -Dorg.kie.server.controller.user = planner -Dorg.kie.server.controller.pwd = Planner123_ -Dorg.kie.server.id = wildfly-kieserver -Dorg.kie.server.location = http：// localhost：8080 / kie-server / services / rest / server -Dorg.kie.server.controller = http：// localhost：8080 / kie-wb / rest / controller

In the second case I get this errors: 在第二种情况下，我得到以下错误：

15:38:35,251 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Found kmodule: vfs:/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,273 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Error when reading virtual file from vfs:/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml: java.lang.IllegalArgumentException: object is not an instance of declaring class at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.getPathForVFS(ClasspathKieProject.java:423) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fi 15：38：35,251 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）找到了kmodule：vfs：/content/kie-wb.war/WEB-INF/lib/kie -wb-common-services-backend-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,273错误[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1 -4）从vfs中读取虚拟文件时出错：/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule。 xml：java.lang.IllegalArgumentException：对象不是在sun.reflect.NativeMethodAccessorImpl.invoke0（本机方法）处在sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）处声明类的实例。 org上org.drools.compiler.kie.builder.impl.ClasspathKieProject.getPathForVFS（ClasspathKieProject.java:423）上java.lang.reflect.Method.invoke（Method.java:498）上的invoke（DelegatingMethodAccessorImpl.java:43） .drools.compiler.kie.builder.impl.ClasspathKieProject.fi xURLFromKProjectPath(ClasspathKieProject.java:368) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fetchKModule(ClasspathKieProject.java:141) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.discoverKieModules(ClasspathKieProject.java:112) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.init(ClasspathKieProject.java:84) at org.drools.compiler.kie.builder.impl.KieContainerImpl.(KieContainerImpl.java:131) at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer(KieServicesImpl.java:131) at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer(KieServicesImpl.java:118) at org.drools.cdi.KieCDIExtension.init(KieCDIExtension.java:94) at org.drools.cdi.KieCDIExtension.processInjectionTarget(KieCDIExtension.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(De 位于org.drools.compiler.kie.builder.impl.ClasspathKieProject.fetchKModule（ClasspathKieProject.java:141）的xURLFromKProjectPath（ClasspathKieProject.java:368）位于org.drools.compiler.kie.builder.impl.ClasspathKieProject.discoverKieModules（ClasspathKieProject.java:141） java：112）位于org.drools.compiler.kie.builder.impl.ClasspathKieProject.init（ClasspathKieProject.java:84）位于org.drools.compiler.kie.builder.impl.KieContainerImpl。（KieContainerImpl.java:131） org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer（Kiedros.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer（KieServicesImpl.java:131）上的org.drools.compiler.kie.builder.impl.java:118 org.drools.cdi.KieCDIExtension.processInjectionTarget（KieCDIExtension.java:100）处的cdi.KieCDIExtension.init（KieCDIExtension.java:94）位于sun.reflect.NativeMethodAccessorImpl.invoke0（Native Method）处的sun.reflect.NativeMethodAccessor（Impl.in）位于sun.reflect.DelegatingMethodAccessorImpl.invoke（De的NativeMethodAccessorImpl.java:62） legatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85) at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330) at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) at org.jboss.weld.util.Observers.notify(Observers.java:166) at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285) at org.jboss.weld.eve legatingMethodAccessorImpl.java:43），位于org.jboss.weld.injection.StaticMethodInjectionPoint.invoke（StaticMethodInjectionPoint.java:95），位于org.jboss.weld.injection的java.lang.reflect.Method.invoke（Method.java:498） org.jboss.weld.injection.MethodInvocationStrategy $ SimpleMethodInvocationStrategy.invoke（MethodInvocationStrategy.java:129）处的.StaticMethodInjectionPoint.invoke（StaticMethodInjectionPoint.java:85）在org.jboss.weld.event.ObserverMethodImpl.sendEvent ）的org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent（ExtensionObserverMethodImpl.java:123）的org.jboss.weld.event.ObserverMethodImpl.sendEvent（ObserverMethodImpl.java:308）的org.jboss.weld.event.ObserverMethod org.jboss.weld.util.Observers.notify（Observers.java:166）上的javax.enterprise.inject.spi.ObserverMethod.notify（ObserverMethod.java:124）上的notify（ObserverMethodImpl.java:286） org.jboss.weld.eve的.weld.event.ObserverNotifier.notifySyncObservers（ObserverNotifier.java:285） nt.ObserverNotifier.notify(ObserverNotifier.java:273) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents.java:269) at org.jboss.weld.bootstrap.AbstractBeanDeployer.processInjectionTargetEvents(AbstractBeanDeployer.java:140) at org.jboss.weld.bootstrap.BeanDeployer.processBeans(BeanDeployer.java:262) at org.jboss.weld.bootstrap.BeanDeployer.processClassBeanAttributes(BeanDeployer.java:244) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:4 org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:177）上的nt.ObserverNotifier.notify（ObserverNotifier.java:273），org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:171）在org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire（AbstractContainerEvent.java:53）处在org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire（AbstractDefinitionContainerEvent.java:44）在org.jboss.weld.bootstrap org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget（ContainerLifecycleEvents.java:269）处的.events.AbstractProcessInjectionTarget.fire（AbstractProcessInjectionTarget.java:33）在org.jboss.weld.bootstrap.AbstractBeanDeployer.java ：140）位于org.jboss.weld.bootstrap.BeanDeployer.processBeans（BeanDeployer.java:262）位于org.jboss.weld.bootstrap.BeanDeployer.processClassBeanAttributes（BeanDeployer.java:244）位于org.jboss.weld.bootstrap。 WeldStartup.deployBeans（WeldStartup.java:4 36) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) 36）在org.jboss.msd.weld.bootstrap.WeldBootstrap.deployBeans（WeldBootstrap.java:86）在org.jboss.weld.WeldStartService.start（WeldStartService.java:97）在org.jboss.msc.service.ServiceControllerImpl org.jboss.msc.service.ServiceControllerImpl $ ControllerTask.run（Service.org.jboss.msc.service.ServiceControllerImpl $ StartTask.execute（ServiceControllerImpl.java:1698）处的$ StartTask.startService（ServiceControllerImpl.java:1736）：1556），位于org.jboss.threads.ContextClassLoaderSavingRunnable.run（ContextClassLoaderSavingRunnable.java：35），位于org.jboss.threads.EnhancedQueueExecutor.safeRun（EnhancedQueueExecutor.java:1985），位于org.jboss.threads.EnhancedQueueExecutor $ org.jboss.threads.EnhancedQueueExecutor $ ThreadBody.run（EnhancedQueueExecutor.java:1378）上的EnhancedQueueExecutor.java:1487）java.lang.Thread.run（Thread.java:748）上的
15:38:35,884 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,885 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war 15:38:35,885 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) As folder project tried to fall back to pom.xml, but could not find one 15:38:35,886 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to load pom.properties from/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,886 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Cannot find maven pom properties for this project. 15：38：35,884警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法在/content/kie-wb.war/WEB-INF/lib中找到pom.properties /kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15：38：35,885警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法在/content/kie-wb.war 15：38：35,885 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject]中找到pom.properties（MSC服务线程1-4）为文件夹项目尝试回退到pom.xml，但找不到一个15：38：35,886 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法加载pom。来自/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15：38：35,886 WARN的属性[.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）找不到该项目的maven pom属性。 Using the container's default ReleaseId 15:38:35,898 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to build index of kmodule.xml url=vfs:/content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml Unable to get all ZipFile entries: /content/kie-wb.war/WEB-INF/lib/kie-wb-common-services-backend-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,898 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Found kmodule: vfs:/content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,899 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Error when reading virtual file from vfs:/content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/kmodule.xml: java.lang.IllegalArgumentException: object is not an instance of declaring class at sun.reflect.NativeMethodAccessorImpl.invoke0(Na 使用容器的默认ReleaseId 15：38：35,898错误[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法建立kmodule.xml的索引url = vfs：/ content / kie -wb.war / WEB-INF / lib / kie-wb-common-services-backend-7.11.0.Final.jar / META-INF / kmodule.xml无法获取所有ZipFile条目：/ content / kie-wb。 war / WEB-INF / lib / kie-wb-common-services-backend-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,898 INFO [org.drools.compiler.kie.builder。 impl.ClasspathKieProject]（MSC服务线程1-4）找到kmodule：vfs：/content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/ kmodule.xml 15：38：35,899错误[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）从vfs读取虚拟文件时出错：/content/kie-wb.war/WEB -INF / lib / kie-dmn-validation-7.11.0.Final.jar / META-INF / kmodule.xml：java.lang.IllegalArgumentException：对象不是在sun.reflect.NativeMethodAccessorImpl.invoke0（娜 tive Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.getPathForVFS(ClasspathKieProject.java:423) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fixURLFromKProjectPath(ClasspathKieProject.java:368) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fetchKModule(ClasspathKieProject.java:141) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.discoverKieModules(ClasspathKieProject.java:112) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.init(ClasspathKieProject.java:84) at org.drools.compiler.kie.builder.impl.KieContainerImpl.(KieContainerImpl.java:131) at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer(KieServicesImpl.java:131) at org.drools.compiler.kie.builder.impl.KieService tive方法），位于sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62），位于java.lang.reflect.Method.invoke（Method.java:498）处，sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）在org.drools.compiler.kie.builder.impl.ClasspathKieProject.fixURLFromKProjectPath（ClasspathKieProject.java:368）的org.drools.compiler.kie.builder.impl.ClasspathKieProject.fixURLFromKProjectPath（ClasspathKieProject.java:368）处org.drools.compiler.kie.builder.impl.ClasspathKieProject.discoverKieModules（ClasspathKieProject.java:112）上的.compiler.kie.builder.impl.ClasspathKieProject.java：141（org.drools.compiler.kie） org.drools.compiler.kie.builder.impl.KieContainerImpl。（KieContainerImpl.java:131）上的.builder.impl.ClasspathKieProject.init（ClasspathKieProject.java:84），位于org.drools.compiler.kie.builder.impl。 org.drools.compiler.kie.builder.impl.KieService上的KieServicesImpl.newKieClasspathContainer（KieServicesImpl.java:131） sImpl.newKieClasspathContainer(KieServicesImpl.java:118) at org.drools.cdi.KieCDIExtension.init(KieCDIExtension.java:94) at org.drools.cdi.KieCDIExtension.processInjectionTarget(KieCDIExtension.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85) at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330) at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123) at org. sImpl.newKieClasspathContainer（KieServicesImpl.java:118）在org.drools.cdi.KieCDIExtension.init（KieCDIExtension.java:94）在org.drools.cdi.KieCDIExtension.processInjectionTarget（KieCDIExtension.java:100）在sun.Accesslect。在sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）的.invoke0（本机方法）在java.lang.reflect.Method.invoke（Method.java）处的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）的invoke（NativeMethodAccessorImpl.java:43）：498）在org.jboss.weldin的org.jboss.weld.injection.StaticMethodInjectionPoint.invoke（StaticMethodInjectionPoint.java:85）在org.jboss.weld.injection.StaticMethodInjectionPoint.invoke（StaticMethodInjectionPoint.java:95） org.jboss.weld.event.ObserverMethodImpl.sendEvent（ObserverMethodImpl.java:330）处的MethodInvocationStrategy $ SimpleMethodInvocationStrategy.invoke（MethodInvocationStrategy.java:129）在org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent（Extension）在组织。 jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) at org.jboss.weld.util.Observers.notify(Observers.java:166) at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285) at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProc org.jboss.weld.event.ObserverMethodImpl.notify（ObserverMethodImpl.java:286）上的jboss.weld.event.ObserverMethodImpl.sendEvent（ObserverMethodImpl.java:308），javax.enterprise.inject.spi.ObserverMethod.notify（ObserverMethod。 java：124）位于org.jboss.weld.util.Observers.notify（Observers.java:166）位于org.jboss.weld.event.ObserverNotifier.notifySyncObservers（ObserverNotifier.java:285）位于org.jboss.weld.event org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:171）的org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:177）的.ObserverNotifier.notify（ObserverNotifier.java:273） org.jboss.weld.bootstrap上的org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire（AbstractContainerEvent.java:53）在org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire（AbstractDefinitionContainerEvent.java:44）。 events.AbstractProcessInjectionTarget.fire（AbstractProcessInjectionTarget.java:33）在org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProc essInjectionTarget(ContainerLifecycleEvents.java:269) at org.jboss.weld.bootstrap.AbstractBeanDeployer.processInjectionTargetEvents(AbstractBeanDeployer.java:140) at org.jboss.weld.bootstrap.BeanDeployer.processBeans(BeanDeployer.java:262) at org.jboss.weld.bootstrap.BeanDeployer.processClassBeanAttributes(BeanDeployer.java:244) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:436) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeR org.jboss.weld.bootstrap.BeanDeployer.processBeans（BeanDeployer.java:262）上的org.jboss.weld.bootstrap.AbstractBeanDeployer.processInjectionTargetEvents（AbstractBeanDeployer.java:140）上的essInjectionTarget（ContainerLifecycleEvents.java:269） org.jboss.weld.bootstrap.WeldStartup.deployBeans（WeldStartup.java:436）上的.weld.bootstrap.BeanDeployer.processClassBeanAttributes（BeanDeployer.java:244）在org.jboss.weld.bootstrap.WeldBootstrap.deployBeans（WeldBootstrap.java ：86），位于org.jboss.msc.service.ServiceControllerImpl $ StartTask.startService（ServiceControllerImpl.java:1736），位于org.jboss.msc.service.ServiceControllerImpl $ StartTask.startService（ServiceControllerImpl.java:1736）。 org.jboss.msc.service.ServiceControllerImpl $ ControllerTask.run（ServiceControllerImpl.java:1556）上的service.ServiceControllerImpl $ StartTask.execute（ServiceControllerImpl.java:1698）org.jboss.threads.ContextClassLoaderSavingRunnable.run（ContextClassLoaderSavingRunnable.java： 35）在org.jboss.threads.EnhancedQueueExecutor.safeR un(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) 15:38:35,927 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,928 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war 15:38:35,928 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) As folder project tried to fall back to pom.xml, but could not find one 15:38:35,928 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to load pom.properties from/content/kie-wb.war/WEB-INF/lib/kie-dmn-valida org.jboss.threads.EnhancedQueueExecutor $ ThreadBody.run（EnhancedQueueExecutor.java:1378）上的org.jboss.threads.EnhancedQueueExecutor $ ThreadBody.doRunTask（EnhancedQueueExecutor.java:1487）上的Un（EnhancedQueueExecutor.java:1985）。 .Thread.run（Thread.java:748）15：38：35,927警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法在/ content /中找到pom.properties kie-wb.war / WEB-INF / lib / kie-dmn-validation-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,928警告[org.drools.compiler.kie.builder。 impl.ClasspathKieProject]（MSC服务线程1-4）在/content/kie-wb.war 15：38：35,928中找不到pom.properties警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）由于文件夹项目试图回退到pom.xml，但找不到一个15：38：35,928 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1- 4）无法从/content/kie-wb.war/WEB-INF/lib/kie-dmn-valida加载pom.properties tion-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,929 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Cannot find maven pom properties for this project. tion-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,929警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）找不到maven pom该项目的属性。 Using the container's default ReleaseId 15:38:35,930 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to build index of kmodule.xml url=vfs:/content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/kmodule.xml Unable to get all ZipFile entries: /content/kie-wb.war/WEB-INF/lib/kie-dmn-validation-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,930 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Found kmodule: vfs:/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,931 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Error when reading virtual file from vfs:/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml: java.lang.IllegalArgumentException: object is not an instance of declaring class at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAcce 使用容器的默认ReleaseId 15：38：35,930错误[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法建立kmodule.xml的索引url = vfs：/ content / kie -wb.war / WEB-INF / lib / kie-dmn-validation-7.11.0.Final.jar / META-INF / kmodule.xml无法获取所有ZipFile条目：/content/kie-wb.war/WEB- INF / lib / kie-dmn-validation-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,930 INFO [org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）找到kmodule：vfs：/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15：38：35,931错误[ org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）从vfs读取虚拟文件时出错：/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11 .0.Final.jar / META-INF / kmodule.xml：java.lang.IllegalArgumentException：对象不是在sun.reflect.NativeMethodAccessorImpl.invoke0（本机方法）处声明类的实例，在sun.reflect.NativeMethodAcce ssorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.getPathForVFS(ClasspathKieProject.java:423) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fixURLFromKProjectPath(ClasspathKieProject.java:368) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.fetchKModule(ClasspathKieProject.java:141) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.discoverKieModules(ClasspathKieProject.java:112) at org.drools.compiler.kie.builder.impl.ClasspathKieProject.init(ClasspathKieProject.java:84) at org.drools.compiler.kie.builder.impl.KieContainerImpl.(KieContainerImpl.java:131) at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer(KieServicesImpl.java:131) at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer(KieServicesIm org.drools.compiler.kie上java.lang.reflect.Method.invoke（Method.java:498）上的sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）上的ssorImpl.invoke（NativeMethodAccessorImpl.java:62） org.drools.compiler.kie.builder.impl.ClasspathKieProject.fixURLFromKProjectPath（ClasspathKieProject.java:368）上的.builder.impl.ClasspathKieProject.getPathForVFS（ClasspathKieProject.java:423）org.drools.compiler.kie.builder.impl org.drools.compiler.kie.builder.impl.ClasspathKieProject.fetchKModule（ClasspathKieProject.java:141）在org.drools.compiler.kie.builder.impl.ClasspathKieProject.init处的ClasspathKieProject.discoverKieModules（ClasspathKieProject.java:112）（ClasspathKieProject.java:84）在org.drools.compiler.kie.builder.impl.KieContainerImpl。（KieContainerImpl.java:131）在org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer（KieServicesImpl。 131），网址为org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieClasspathContainer（KieServicesIm pl.java:118) at org.drools.cdi.KieCDIExtension.init(KieCDIExtension.java:94) at org.drools.cdi.KieCDIExtension.processInjectionTarget(KieCDIExtension.java:100) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:85) at org.jboss.weld.injection.MethodInvocationStrategy$SimpleMethodInvocationStrategy.invoke(MethodInvocationStrategy.java:129) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330) at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123) at org.jboss.weld.event.ObserverMethodImpl.sendEven pl.java:118）位于org.drools.cdi.KieCDIExtension.init（KieCDIExtension.java:94）位于org.drools.cdi.KieCDIExtension.processInjectionTarget（KieCDIExtension.java:100）位于sun.reflect.NativeMethodAccessorImpl.invoke0（本机） Method）位于sun.reflect.NativeMethodAccessorImpl.invoke（NativeMethodAccessorImpl.java:62）位于sun.reflect.DelegatingMethodAccessorImpl.invoke（DelegatingMethodAccessorImpl.java:43）位于java.lang.reflect.Method.invoke（Method.java:498）在org.jboss.weld.Injection.MethodSimple.Injection.MethodSimple.Inject.MethodInjection.Method.Inject.Method.Inject.Method.Injection.Invoke（StaticMethodInjectionPoint.java:85）上的org.jboss.weld.StaticMethodInjectionPoint.invoke（StaticMethodInjectionPoint.java:95） org.jboss.weld.event.ObserverMethodImpl.sendEvent（ObserverMethodImpl.java:330）的org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent（ExtensionObserverMethodImpl.java:123）的invoke（MethodInvocationStrategy.java:129） .weld.event.ObserverMethodImpl.sendEven t(ObserverMethodImpl.java:308) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) at org.jboss.weld.util.Observers.notify(Observers.java:166) at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285) at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171) at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53) at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:44) at org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire(AbstractProcessInjectionTarget.java:33) at org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget(ContainerLifecycleEvents. org.jboss.weld.event的t（ObserverMethodImpl.java:308）.org.jboss的javax.enterprise.inject.spi.ObserverMethod.notify（ObserverMethod.java:124）上的org.jboss.weld.event.ObserverMethodImpl.notify（ObserverMethodImpl.java:286） org.jboss.weld.event.ObserverNotifier.notifySyncObservers（ObserverNotifier.java:285）上的.weld.util.Observers.notify（Observers.java:166）org.jboss.weld.event.ObserverNotifier.notify（ObserverNotifier.notify（ObserverNotifier.java ：273），位于org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:177），位于org.jboss.weld.event.ObserverNotifier.fireEvent（ObserverNotifier.java:171），位于org.jboss.weld.bootstrap。 org.jboss.weld.bootstrap.events.AbstractProcessInjectionTarget.fire（AbstractProcessInjectionTarget.fire（org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire（AbstractDefinitionContainerEvent.java:44）处的events.AbstractContainerEvent.fire（AbstractContainerEvent.java:53）。 java：33），位于org.jboss.weld.bootstrap.events.ContainerLifecycleEvents.fireProcessInjectionTarget（ContainerLifecycleEvents。 java:269) at org.jboss.weld.bootstrap.AbstractBeanDeployer.processInjectionTargetEvents(AbstractBeanDeployer.java:140) at org.jboss.weld.bootstrap.BeanDeployer.processBeans(BeanDeployer.java:262) at org.jboss.weld.bootstrap.BeanDeployer.processClassBeanAttributes(BeanDeployer.java:244) at org.jboss.weld.bootstrap.WeldStartup.deployBeans(WeldStartup.java:436) at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:86) at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:97) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.j java：269）位于org.jboss.weld.bootstrap.AbstractBeanDeployer.processInjectionTargetEvents（AbstractBeanDeployer.java:140）位于org.jboss.weld.bootstrap.BeanDeployer.processBeans（BeanDeployer.java:262）位于org.jboss.weld.bootstrap org.jboss.weld.bootstrap.WeldBootstrap.deployBeans（WeldBootstrap.java:86）上的org.jboss.weld.bootstrap.WeldStartup.deployBeans（WeldStartup.java:436）上的.BeanDeployer.processClassBeanAttributes（BeanDeployer.java:244）位于org.jboss.msc.service.ServiceControllerImpl $ StartTask.startService（ServiceControllerImpl.java:1736）的org.jboss.msc.service.ServiceControllerImpl $的org.jboss.as.weld.WeldStartService.start（WeldStartService.java:97） org.jboss.threads.ContextClassLoaderSavingRunnable.run（ContextClassLoaderSavingRunnable.java:35）的org.jboss.msc.service.ServiceControllerImpl $ ControllerTask.run（ServiceControllerImpl.java:1556）的org.jboss.threads.ContextClassLoaderSavingRunnable.run（ContextClassLoaderSavingRunnable.java:35）的StartTask.execute（ServiceControllerImpl.java:1698） org.j的.jboss.threads.EnhancedQueueExecutor.safeRun（EnhancedQueueExecutor.java:1985） boss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) 15:38:35,995 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,998 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to find pom.properties in /content/kie-wb.war 15:38:35,999 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) As folder project tried to fall back to pom.xml, but could not find one 15:38:35,999 WARN [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to load pom.properties from/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:35,999 WARN [or 位于org.jboss.threads.EnhancedQueueExecutor $ ThreadBody.run（EnhancedQueueExecutor.java:1378）的boss.threads.EnhancedQueueExecutor $ ThreadBody.doRunTask（EnhancedQueueExecutor.java:1487）（java.lang.Thread.run（Thread.java:748） 15：38：35,995警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法在/content/kie-wb.war/WEB-INF/lib中找到pom.properties /kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15：38：35,998警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法在/content/kie-wb.war 15：38：35,999中找到pom.properties警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）当文件夹项目试图回退时到pom.xml，但找不到一个15：38：35,999警告[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法从/ content / kie加载pom.properties -wb.war / WEB-INF / lib / kie-pmml-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：35,999 WARN [或 g.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Cannot find maven pom properties for this project. g.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）找不到此项目的maven pom属性。 Using the container's default ReleaseId 15:38:36,000 ERROR [org.drools.compiler.kie.builder.impl.ClasspathKieProject] (MSC service thread 1-4) Unable to build index of kmodule.xml url=vfs:/content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml Unable to get all ZipFile entries: /content/kie-wb.war/WEB-INF/lib/kie-pmml-7.11.0.Final.jar/META-INF/kmodule.xml 15:38:37,640 INFO [org.jboss.errai.common.metadata.MetaDataScanner] (Thread-112) added class scanning extensions: org.jboss.errai.common.metadata.JbossVFsTypeHandler 15:38:37,641 INFO [org.jboss.errai.common.metadata.MetaDataScanner] (Thread-112) added class scanning extensions: org.jboss.errai.common.metadata.JbossVFsTypeHandler 15:40:11,831 INFO [org.jboss.errai.reflections.Reflections] (Thread-112) Reflections took 94179 ms to scan 152 urls, producing 4832 keys and 32877 values [using 2 cores] 15:40:12,062 WARN [org.jboss.errai.config.rebind.EnvUtil] (MSC service thread 1-4) The property errai.security.user_o 使用容器的默认ReleaseId 15：38：36,000错误[org.drools.compiler.kie.builder.impl.ClasspathKieProject]（MSC服务线程1-4）无法建立kmodule.xml的索引url = vfs：/ content / kie -wb.war / WEB-INF / lib / kie-pmml-7.11.0.Final.jar / META-INF / kmodule.xml无法获取所有ZipFile条目：/content/kie-wb.war/WEB-INF/ lib / kie-pmml-7.11.0.Final.jar / META-INF / kmodule.xml 15：38：37,640 INFO [org.jboss.errai.common.metadata.MetaDataScanner]（Thread-112）添加了类扫描扩展： org.jboss.errai.common.metadata.JbossVFsTypeHandler 15：38：37,641 INFO [org.jboss.errai.common.metadata.MetaDataScanner]（Thread-112）添加了类扫描扩展：org.jboss.errai.common.metadata。 JbossVFsTypeHandler 15：40：11,831信息[org.jboss.errai.reflections.Reflections]（Thread-112）反射花了94179 ms来扫描152个URL，产生了4832个键和32877个值[使用2个内核] 15：40：12,062 WARN [ org.jboss.errai.config.rebind.EnvUtil]（MSC服务线程1-4）属性errai.security.user_o n_hostpage_enabled has been set multiple times. n_hostpage_enabled已设置多次。 15:40:12,084 WARN [org.jboss.errai.config.rebind.EnvUtil] (MSC service thread 1-4) The property errai.class_scanning_extension has been set multiple times. 15：40：12,084 WARN [org.jboss.errai.config.rebind.EnvUtil]（MSC服务线程1-4）已多次设置属性errai.class_scanning_extension。 15:40:32,658 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.kie.workbench.common.forms.data.modeller.service.DataObjectFinderService 15:40:32,660 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.uberfire.preferences.shared.PreferenceStorage 15:40:32,664 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.guvnor.common.services.project.service.ModuleService 15:40:32,675 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.guvnor.common.services.project.service.ModuleRepositoriesService 15:40:32,687 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.guvnor.common.services.shared.metadata.MetadataService 15:40:32,708 WARN [org.jboss.errai.cdi.serv 15：40：32,658警告[org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.kie.workbench.common.forms.data.modeller.service.DataObjectFinderService的@Service实现15：40：32,660 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.uberfire.preferences.shared.PreferenceStorage的@Service实现15：40：32,664 WARN [org .jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.guvnor.common.services.project.service.ModuleService的@Service实现15：40：32,675 WARN [org.jboss.errai .cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.guvnor.common.services.project.service.ModuleRepositoriesService 15：40：32,687 WARN的@Service实现[org.jboss.errai.cdi.server .CDIExtensionPoints]（MSC服务线程1-4）找不到org.guvnor.common.services.shared.metadata.MetadataService的@Service实现15：40：32,708警告[org.jboss.errai.cdi.serv er.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.kie.workbench.common.forms.data.modeller.service.DataObjectFormModelCreationService 15:40:32,740 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.kie.workbench.common.stunner.core.service.DiagramLookupService 15:40:32,742 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.optaplanner.workbench.screens.guidedrule.service.ScoreHolderService 15:40:32,749 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.drools.workbench.screens.guided.dtable.service.GuidedDecisionTableGraphSaveAndRenameService 15:40:32,777 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.guvnor.common.services.project.service.WorkspaceProjectService 15:40:32 er.CDIExtensionPoints]（MSC服务线程1-4）未找到org.kie.workbench.common.forms.data.modeller.service.DataObjectFormModelCreationService 15：40：32,740 WARN [org.jboss.errai.cdi]的@Service实现。 server.CDIExtensionPoints]（MSC服务线程1-4）未找到org.kie.workbench.common.stunner.core.service.DiagramLookupService 15：40：32,742 WARN [org.jboss.errai.cdi.server]的@Service实现。 CDIExtensionPoints]（MSC服务线程1-4）找不到org.optaplanner.workbench.screens.guidedrule.service.ScoreHolderService @：Service的@Service实现15：40：32,749 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）未找到org.drools.workbench.screens.guided.dtable.service.GuidedDecisionTableGraphSaveAndRenameService的@Service实现15：40：32,777 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.guvnor.common.services.project.service.WorkspaceProjectService 15:40:32的@Service实现 ,799 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.kie.workbench.common.forms.editor.service.FormCreatorService 15:40:32,800 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints] (MSC service thread 1-4) No @Service implementations found for org.uberfire.ext.editor.commons.service.htmleditor.HtmlEditorService 15:42:13,483 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. ，799 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.kie.workbench.common.forms.editor.service.FormCreatorService的@Service实现15：40：32,800 WARN [org.jboss.errai.cdi.server.CDIExtensionPoints]（MSC服务线程1-4）找不到org.uberfire.ext.editor.commons.service.htmleditor.HtmlEditorService 15：42：13,483的@Service实现错误[ org.jboss.as.controller.management-operation]（外部管理请求线程-1）WFLYCTL0348：等待[300]秒后等待服务容器稳定的超时。 Operation will roll back. 操作将回滚。 Step that first updated the service container was 'deploy' at address '[("deployment" => "kie-wb.war")]' 15:42:35,526 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "kie-wb.war" was rolled back with the following failure message: "WFLYCTL0344: Operation timed out awaiting service container stability" 15:42:47,036 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$1@1dae869d for operation deploy at address [("deployment" => "kie-wb.war")] failed handling operation rollback -- java.util.concurrent.TimeoutException: java.util.concurrent.TimeoutException at org.jboss.as.controller.OperationContextImpl.waitForRemovals(OperationContextImpl.java:521) at org.jboss.as.controller.AbstractOperationContext$Step.handleResult(AbstractOperationContext.java:1518) at org.jboss.as.controller.AbstractOperationContext$Step.fin 15：42：35,526错误[org.jboss.as.server]（外部管理请求）首先更新服务容器的步骤是在地址'[（“ deployment” =>“ kie-wb.war”）]''deploy'线程-1）WFLYSRV0021：部署“ kie-wb.war”的部署已回滚，并显示以下失败消息：“ WFLYCTL0344：操作超时，等待服务容器的稳定性” 15：42：47,036错误[org.jboss.as。 controller.management-operation]（外部管理请求线程-1）WFLYCTL0190：步骤处理程序org.jboss.as.server.deployment.DeploymentHandlerUtil$1@1dae869d用于操作部署在地址[[“ deployment” =>“ kie-wb。 war“）]处理操作回滚失败-org.jboss.as.controller.OperationContextImpl.waitForRemovals（OperationContextImpl.java:521）处的org.jboss.as.controller.OperationContextImpl.java.util.concurrent.TimeoutException org.jboss.as.controller.AbstractOperationContext $ Step.fin处的.controller.AbstractOperationContext $ Step.handleResult（AbstractOperationContext.java:1518） alizeInternal(AbstractOperationContext.java:1472) at org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1445) at org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1319) at org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:876) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1411) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:265) at org.wildfly.security.auth.server.SecurityIdentity org.jboss.as.controller.AbstractOperationContext $ Step.finalizeStep（AbstractOperationContext.java:1445）处的alizeInternal（AbstractOperationContext.java:1472）org.jboss.as.controller.AbstractOperationContext $ Step.access $ 400（AbstractOperationContext.java:1319））在org.jboss.as.controller.AbstractOperationContext上的org.jboss.as.controller.AbstractOperationContext.processStages（AbstractOperationContext.java:726）上的org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase（AbstractOperationContext.java:876） org.jboss.as.controller.executeOperation（AbstractOperationContext.java:467）org.jboss.as.controller.OperationContextImpl.executeOperation（OperationContextImpl.java:1411）org.jboss.as.controller.ModelControllerImpl.internalExecute（ModelControllerImpl.java:423） org.wildfly.security.auth.server的.as.controller.ModelControllerImpl.lambda $ execute $ 1（ModelControllerImpl.java:243）org.wildfly.security.auth.server的SecurityIdentity.runAs（SecurityIdentity.java:265）。的SecurityIdentity .runAs(SecurityIdentity.java:231) 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.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:246) 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.ha org.jboss.as.controller.ModelControllerImpl.execute（ModelControllerImpl.java:243）的.runAs（SecurityIdentity.java:231）org.jboss.as.domain.http.server.DomainApiHandler.handleRequest（DomainApiHandler.java:212 ），位于org.jboss的org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest（DomainApiCheckHandler.java:93）的io.undertow.server.handlers.encoding.EncodingHandler.handleRequest（EncodingHandler.java:72）处。 as.domain.http.server.security.ElytronIdentityHandler.lambda $ handleRequest $ 0（ElytronIdentityHandler.java:62）在org.wildfly.security.auth.server.SecurityIdentity.runAs（SecurityIdentity.java:289）在org.wildfly.security org.jboss.as.controller.AccessAuditContext.doAs（AccessAuditContext.java:254）上的.auth.server.SecurityIdentity.runAs（SecurityIdentity.java:246）在org.jboss.as.controller.AccessAuditContext.doAs（AccessAuditContext.java）：225），位于io.undertow.server.ha的org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest（ElytronIdentityHandler.java:61） ndlers.BlockingHandler.handleRequest(BlockingHandler.java:56) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360) 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:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) 15:43:06,915 ERROR [org.jboss.as.controller.client] (External Management Request Threads -- 1) WFLYCTL0190: Step handler org.jboss.as.server.deployment.DeploymentHandlerUtil$1@1dae869d for operation deploy at address [("deployment" => "kie-wb.war")] failed handling operation rollback -- java.util.concurrent.TimeoutE org上io.undertow.server.Connectors.executeRootHandler（Connectors.java:360）上io.undertow.server.HttpServerExchange $ 1.run（HttpServerExchange.java:830）上的ndlers.BlockingHandler.handleRequest（BlockingHandler.java:56）。 org.jboss.threads.EnhancedQueueExecutor.safeRun（EnhancedQueueExecutor.java:1985）处的org.jboss.threads.EnhancedQueueExecutor $ EnhancedQueueExecutor.safeRun（ContextClassLoaderSavingRunnable.java:35）在org.jboss.threads.EnhancedQueueExecutor $ EnhancedQueueExecutor $ ThreadBody.doRunTask（在org.jboss.threads.JBossThread.run（JBossThread.java:485）在org.jboss.threads.EnhancedQueueExecutor $ ThreadBody.run（EnhancedQueueExecutor.java:1378）在java.lang.Thread.run（Thread.java:748））15：43：06,915错误[org.jboss.as.controller.client]（外部管理请求线程-1）WFLYCTL0190：步骤处理程序org.jboss.as.server.deployment.DeploymentHandlerUtil$1@1dae869d用于地址部署[（“ deployment” =>“ kie-wb.war”）]处理操作回滚失败-java.util.concurrent.TimeoutE xception 15:43:38,794 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0349: Timeout after [5] seconds waiting for service container stability while finalizing an operation. xception 15：43：38,794错误[org.jboss.as.controller.management-operation]（外部管理请求线程-1）WFLYCTL0349：[5]秒后超时，在完成操作时等待服务容器的稳定性。 Process must be restarted. 进程必须重新启动。 Step that first updated the service container was 'deploy' at address '[("deployment" => "kie-wb.war")]' 首先更新服务容器的步骤是在地址'[（“ deployment” =>“ kie-wb.war”）]''deploy'

How to solve the problem? 如何解决问题？

1 个解决方案

The kie-wb doesn't work with Oracle Java. kie-wb不适用于Oracle Java。 I could deploy kie-wb in wildfly after I removed Oracle Java and installed openJDK. 删除Oracle Java并安装openJDK之后，可以在wildfly中部署kie-wb。