Error on drools 7 installation
938 views
Skip to first unread message
Jainath Gupta
Jul 17, 2017, 8:35:31 AM7/17/17
to Drools Setup
Hi,
I am using wildfly 11 for kie-server and kie-workbench 7.0-final
kie-server-7.0.0.Final-ee7.war
kie-drools-wb-7.0.0.Final-wildfly10.war
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\bin>standalone.bat
Calling "D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\bin\standalone.conf.bat"
Setting JAVA property to "D:\Project Software\jdk1.8.0_45\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1"
JAVA: "D:\Project Software\jdk1.8.0_45\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms512M -Xmx2048M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dor
g.kie.demo=false -Dorg.kie.example=false -Dorg.kie.server.user=jainath -Dorg.kie.server.pwd=jainath1! -Dorg.kie.server.id=jai-kie-server -Dorg.kie.server.location=htt
p://172.19.65.41:8083/kie-server/services/rest/server -Dorg.kie.server.controller=http://172.19.65.41:8083/kie-wb/rest/controller -Dorg.kie.server.controller.user=kie
server -Dorg.kie.server.controller.pwd=kieserver1! -Dorg.kie.server.persistence.dialect=org.hibernate.dialect.OracleDialect -Dorg.kie.server.persistence.ds=java:/droo
ltest"
===============================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
17:56:37,035 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6
17:56:37,470 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
17:56:37,588 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Alpha1 (WildFly Core 3.0.0.Beta11) starting
17:56:39,405 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-
service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-r
esource-description operation to learn more about the deprecation.
17:56:39,426 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 22) WFLYCTL0028: Attribute 'security-realm' in the resource at addres
s '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of
the read-resource-description operation to learn more about the deprecation.
17:56:39,445 INFO [org.wildfly.security] (ServerService Thread Pool -- 2) ELY00001: WildFly Elytron version 1.1.0.Beta33
17:56:39,466 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment kie-drools-wb.war
17:56:40,561 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment kie-server.war
17:56:40,604 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-drools-wb.war in deployment directory. To trigger de
ployment create a file called kie-drools-wb.war.dodeploy
17:56:40,605 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deplo
yment create a file called kie-server.war.dodeploy
17:56:40,632 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
17:56:40,644 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.5.0.Beta2
17:56:40,661 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.5.0.Beta2
17:56:40,709 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 42) WFLYRS0016: RESTEasy version 3.0.21.Final
17:56:40,728 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 58) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is uniqu
e.
17:56:40,741 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 49) WFLYNAM0001: Activating Naming Subsystem
17:56:40,754 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
17:56:40,757 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.2.Final)
17:56:40,758 INFO [org.jboss.as.security] (ServerService Thread Pool -- 57) WFLYSEC0002: Activating Security Subsystem
17:56:40,765 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 60) WFLYWS0002: Activating WebServices Extension
17:56:40,793 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main]
17:56:40,837 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads
based on your 4 available processors
17:56:40,865 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.11.Final starting
17:56:40,868 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.0.Beta1
17:56:40,872 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.4)
17:56:40,914 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
17:56:40,978 INFO [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service
17:56:40,986 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
17:56:41,107 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0014: Creating file handler for path 'D:\Project Software\wildfly-11.0.0.A
lpha1-drools7.0\wildfly-11.0.0.Alpha1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths:
'[]']
17:56:41,258 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
17:56:41,286 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
17:56:41,364 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is
derived from thread worker pool sizing.
17:56:41,364 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is
derived from the number of CPUs on this host.
17:56:41,447 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.0.Beta19
17:56:41,581 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 172.19.65.41:8083
17:56:41,821 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
17:56:42,017 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
17:56:42,044 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
17:56:42,052 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly
-11.0.0.Alpha1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
17:56:42,076 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Project Software
\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\standalone\deployments
17:56:42,378 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "kie-server.war" (runtime-name: "kie-server.war")
17:56:42,381 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "kie-drools-wb.war" (runtime-name: "kie-drools-wb.war
")
17:56:42,616 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTPS listener https listening on 172.19.65.41:8446
17:56:42,756 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final
17:56:42,966 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.8.Final (Apache CXF 3.1.10)
17:56:52,900 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
17:56:52,906 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-core.jar in /D:/Project Software/wildfly-11.0.0.Alpha1
-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
17:56:53,029 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.ms
c.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "kie-server.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
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: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.jav
a:274)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:154)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:81)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeployme
ntUnitProcessor.java:57)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
17:57:18,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-api.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
17:57:18,765 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-core.jar in /D:/Project Software/wildfly-11.0.0.Alpha1
-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
17:57:18,903 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xml-apis.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.
17:57:18,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xercesImpl.jar in /D:/Project Software/wildfly-11.0.0.Alpha
1-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
17:57:18,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xml-apis.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
17:57:18,920 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry serializer.jar in /D:/Project Software/wildfly-11.0.0.Alpha
1-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
17:57:19,028 INFO [org.jboss.as.pojo] (MSC service thread 1-6) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xm
l features (potential exceptions).
17:57:20,828 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.module.service."deployment.kie-drools-wb.war".main:
org.jboss.msc.service.StartException in service jboss.module.service."deployment.kie-drools-wb.war".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb
.war
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
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: org.jboss.modules.ModuleNotFoundException: org.jboss.sasl
at org.jboss.modules.Module.addPaths(Module.java:1212)
at org.jboss.modules.Module.link(Module.java:1568)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1596)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:286)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:270)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
... 5 more
17:57:20,835 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie
-drools-wb.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.kie-drools-wb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.s
ervice.\"deployment.kie-drools-wb.war\".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb.war
Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.sasl"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.module.service.\"deployment.kie-drools-wb.war\".main"]
}
17:57:20,840 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie
-server.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kie-server.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ki
e-server.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"kie-server.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"kie-server.war\".PARSE"]
}
17:57:20,915 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "kie-server.war" (runtime-name : "kie-server.war")
17:57:20,916 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "kie-drools-wb.war" (runtime-name : "kie-drools-wb.war")
17:57:20,918 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deploy
ment.unit."kie-server.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "kie-server.war"
service jboss.module.service."deployment.kie-drools-wb.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.kie-drools-wb
.war".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb.war
17:57:21,081 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
17:57:21,084 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9993/management
17:57:21,084 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9993
17:57:21,085 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 11.0.0.Alpha1 (WildFly Core 3.0.0.Beta11) started (with errors) in 44493ms - Star
ted 414 of 660 services (3 services failed or missing dependencies, 430 services are lazy, passive or on-demand)
17:57:21,821 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment kie-server.war (runtime-name: kie-server.war) in 688ms
17:57:22,688 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment kie-drools-wb.war (runtime-name: kie-drools-wb.war) in 15
58ms
17:57:22,786 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "kie-server.war" (runtime-name: "kie-server.war")
17:57:22,787 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "kie-drools-wb.war" (runtime-name: "kie-drools-wb.war")
17:57:22,788 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.service."deployment.kie-drools-wb.war".main (missing) dependents: [service jboss.deployment.unit."kie-drools-wb.war".FIRST_MODULE_USE]
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."kie-server.war".PARSE
service jboss.module.service."deployment.kie-drools-wb.war".main
17:57:25,972 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-drools-wb.war in deployment directory. To trigger de
ployment create a file called kie-drools-wb.war.dodeploy
17:57:25,974 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deplo
yment create a file called kie-server.war.dodeploy
Jainath Gupta
Jul 17, 2017, 8:46:45 AM7/17/17
to Drools Setup
I forgot to add datasource in standalone.xml
But it was also showing error
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\bin>standalone.bat
Calling "D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\bin\standalone.conf.bat"
Setting JAVA property to "D:\Project Software\jdk1.8.0_45\bin\java"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: "D:\Project Software\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1"
JAVA: "D:\Project Software\jdk1.8.0_45\bin\java"
JAVA_OPTS: "-Dprogram.name=standalone.bat -Xms512M -Xmx2048M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Dor
g.kie.demo=false -Dorg.kie.example=false -Dorg.kie.server.user=jainath -Dorg.kie.server.pwd=jainath1! -Dorg.kie.server.id=jai-kie-server -Dorg.kie.server.location=htt
p://172.19.65.41:8083/kie-server/services/rest/server -Dorg.kie.server.controller=http://172.19.65.41:8083/kie-wb/rest/controller -Dorg.kie.server.controller.user=kie
server -Dorg.kie.server.controller.pwd=kieserver1! -Dorg.kie.server.persistence.dialect=org.hibernate.dialect.OracleDialect -Dorg.kie.server.persistence.ds=java:/droo
ltest"
===============================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256M; support was removed in 8.0
18:14:21,470 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta6
18:14:21,982 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1
18:14:22,126 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 11.0.0.Alpha1 (WildFly Core 3.0.0.Beta11) starting
18:14:24,082 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-
service=management/management-interface=http-interface' is deprecated, and may be removed in future version. See the attribute description in the output of the read-r
esource-description operation to learn more about the deprecation.
18:14:24,115 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 28) WFLYCTL0028: Attribute 'security-realm' in the resource at addres
s '/subsystem=undertow/server=default-server/https-listener=https' is deprecated, and may be removed in future version. See the attribute description in the output of
the read-resource-description operation to learn more about the deprecation.
18:14:24,124 INFO [org.wildfly.security] (ServerService Thread Pool -- 27) ELY00001: WildFly Elytron version 1.1.0.Beta33
18:14:24,191 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment kie-drools-wb.war
18:14:25,179 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment kie-server.war
18:14:25,241 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-drools-wb.war in deployment directory. To trigger de
ployment create a file called kie-drools-wb.war.dodeploy
18:14:25,241 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deplo
yment create a file called kie-server.war.dodeploy
18:14:25,286 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
18:14:25,314 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.5.0.Beta2
18:14:25,328 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.5.0.Beta2
18:14:25,359 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
18:14:25,376 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 60) WFLYWS0002: Activating WebServices Extension
18:14:25,379 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 42) WFLYRS0016: RESTEasy version 3.0.21.Final
18:14:25,379 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 58) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is uniqu
e.
18:14:25,383 INFO [org.jboss.as.security] (ServerService Thread Pool -- 57) WFLYSEC0002: Activating Security Subsystem
18:14:25,389 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 49) WFLYNAM0001: Activating Naming Subsystem
18:14:25,423 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads
based on your 4 available processors
18:14:25,452 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 47) WFLYJSF0007: Activated the following JSF Implementations: [main]
18:14:25,480 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.0.Beta1
18:14:25,489 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
18:14:25,491 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
18:14:25,595 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.2.Final)
18:14:25,651 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.dr
iver.OracleDriver (version 10.2)
18:14:25,663 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 1.4.11.Final starting
18:14:25,678 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 36) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "com.db2")
]) - failure description: "WFLYJCA0041: Failed to load module for driver [com.db2]"
18:14:25,683 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = com.oracle
18:14:25,703 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.4)
18:14:25,706 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
18:14:26,030 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is
derived from thread worker pool sizing.
18:14:26,039 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is
derived from the number of CPUs on this host.
18:14:26,133 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.0.Beta19
18:14:26,171 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0014: Creating file handler for path 'D:\Project Software\wildfly-11.0.0.A
lpha1-drools7.0\wildfly-11.0.0.Alpha1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths:
'[]']
18:14:26,205 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
18:14:26,237 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
18:14:26,336 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 172.19.65.41:8083
18:14:26,817 INFO [org.jboss.as.patching] (MSC service thread 1-7) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
18:14:26,860 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Project Software
\wildfly-11.0.0.Alpha1-drools7.0\wildfly-11.0.0.Alpha1\standalone\deployments
18:14:26,968 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "kie-drools-wb.war" (runtime-name: "kie-drools-wb.war
")
18:14:26,974 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "kie-server.war" (runtime-name: "kie-server.war")
18:14:27,909 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final
18:14:28,097 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0493: EJB subsystem suspension complete
18:14:28,232 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 172.19.65.41:8446
18:14:28,293 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/drooltest]
18:14:28,296 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
18:14:28,460 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.8.Final (Apache CXF 3.1.10)
18:14:34,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
18:14:34,736 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-core.jar in /D:/Project Software/wildfly-11.0.0.Alpha1
-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
18:14:34,858 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.ms
c.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment "kie-server.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
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: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:669)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.jav
a:274)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:154)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:81)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeployme
ntUnitProcessor.java:57)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:76)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more
18:15:01,067 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/jaxb-core-2.2.11.jar does not point to a valid jar for a Class-Path reference.
18:15:01,070 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-core.jar in /D:/Project Software/wildfly-11.0.0.Alpha1
-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/jaxb-impl-2.2.11.jar does not point to a valid jar for a Class-Path reference.
18:15:01,208 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.
18:15:01,223 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xercesImpl.jar in /D:/Project Software/wildfly-11.0.0.Alpha
1-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
18:15:01,224 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /D:/Project Software/wildfly-11.0.0.Alpha1-
drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
18:15:01,225 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry serializer.jar in /D:/Project Software/wildfly-11.0.0.Alpha
1-drools7.0/wildfly-11.0.0.Alpha1/standalone/deployments/kie-drools-wb.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
18:15:01,354 INFO [org.jboss.as.pojo] (MSC service thread 1-7) WFLYPOJO0001: Found legacy bean/pojo namespace: urn:jboss:bean-deployer:2.0 - might be missing some xm
l features (potential exceptions).
18:15:02,619 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.module.service."deployment.kie-drools-wb.war".main:
org.jboss.msc.service.StartException in service jboss.module.service."deployment.kie-drools-wb.war".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb
.war
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
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: org.jboss.modules.ModuleNotFoundException: org.jboss.sasl
at org.jboss.modules.Module.addPaths(Module.java:1212)
at org.jboss.modules.Module.link(Module.java:1568)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1596)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:286)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:270)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:68)
... 5 more
18:15:02,625 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie
-drools-wb.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.module.service.\"deployment.kie-drools-wb.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.s
ervice.\"deployment.kie-drools-wb.war\".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb.war
Caused by: org.jboss.modules.ModuleNotFoundException: org.jboss.sasl"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.module.service.\"deployment.kie-drools-wb.war\".main"]
}
18:15:02,627 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie
-server.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"kie-server.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ki
e-server.war\".PARSE: WFLYSRV0153: Failed to process phase PARSE of deployment \"kie-server.war\"
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"},
"WFLYCTL0412: Required services that are not installed:" => ["jboss.deployment.unit.\"kie-server.war\".PARSE"]
}
18:15:02,678 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "kie-server.war" (runtime-name : "kie-server.war")
18:15:02,679 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "kie-drools-wb.war" (runtime-name : "kie-drools-wb.war")
18:15:02,681 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.module.service."deployment.kie-drools-wb.war".main: org.jboss.msc.service.StartException in service
jboss.module.service."deployment.kie-drools-wb.war".main: WFLYSRV0179: Failed to load module: deployment.kie-drools-wb.war
service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: WFLYSRV0153:
Failed to process phase PARSE of deployment "kie-server.war"
18:15:02,818 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
18:15:02,820 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9993/management
18:15:02,821 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9993
18:15:02,822 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 11.0.0.Alpha1 (WildFly Core 3.0.0.Beta11) started (with errors) in 41782ms - Star
ted 421 of 667 services (3 services failed or missing dependencies, 431 services are lazy, passive or on-demand)
18:15:03,565 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment kie-server.war (runtime-name: kie-server.war) in 702ms
18:15:04,278 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment kie-drools-wb.war (runtime-name: kie-drools-wb.war) in 14
15ms
18:15:04,345 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "kie-server.war" (runtime-name: "kie-server.war")
18:15:04,346 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "kie-drools-wb.war" (runtime-name: "kie-drools-wb.war")
18:15:04,347 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.module.service."deployment.kie-drools-wb.war".main (missing) dependents: [service jboss.deployment.unit."kie-drools-wb.war".FIRST_MODULE_USE]
WFLYCTL0186: Services which failed to start: service jboss.module.service."deployment.kie-drools-wb.war".main
service jboss.deployment.unit."kie-server.war".PARSE
18:15:07,751 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-drools-wb.war in deployment directory. To trigger de
ployment create a file called kie-drools-wb.war.dodeploy
18:15:07,752 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deplo
yment create a file called kie-server.war.dodeploy
Maciej Swiderski
Jul 17, 2017, 8:49:19 AM7/17/17
to drools...@googlegroups.com
start wildfly with standalone-full profile
standalone.bat --server-config=standalone-full.xml
Maciej
--
You received this message because you are subscribed to the Google Groups "Drools Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to drools-setup...@googlegroups.com.
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/5ea8a547-9bb8-445f-b965-c51e826edd4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Maciej Swiderski
Jul 17, 2017, 9:26:02 AM7/17/17
to drools...@googlegroups.com
you have bunch of errors with your server config - like missing data sources etc. Please go over the logs and fix the config issues.
Maciej
To post to this group, send email to drools...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/drools-setup/4254417f-f721-4c1f-bf42-5e6a273e0d32%40googlegroups.com.
<server.log>
Jainath Gupta
Jul 17, 2017, 9:43:48 AM7/17/17
to Drools Setup
Hi Maciej,
I am using same DB for Drools 6.5. So it was showing error. Because I tried to create the same table twice here:
So for that we need to create different DB ?
Thanks
...
Jainath Gupta
Jul 17, 2017, 9:52:49 AM7/17/17
to Drools Setup
Actually, I am using only BRMS so can I stop connection with DB ?
...
0 new messages