KIE Server 6.5.0.Final - Error on startup
1,843 views
Skip to first unread message
Nick Wong
Nov 6, 2016, 10:11:11 AM11/6/16
to jBPM Setup
I got the following when starting up kie-server 6.5.0.Final on docker container (see the dockefile below)
JAVA_OPTS already set in environment; overriding default settings with values: -XX:MaxPermSize=256m -Xms256m -Xmx512m
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss/wildfly
JAVA: /usr/lib/jvm/java/bin/java
JAVA_OPTS: -server -XX:MaxPermSize=256m -Xms256m -Xmx512m
=========================================================================
14:38:24,963 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
14:38:26,391 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
14:38:26,625 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
14:38:33,126 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found kie-server.war in deployment directory. To trigger deployment create a file called kie-server.war.dodeploy
14:38:33,195 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
14:38:33,395 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
14:38:33,429 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
14:38:33,646 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 35) JBAS010280: Activating Infinispan subsystem.
14:38:33,661 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 34) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
14:38:33,705 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 42) JBAS012615: Activated the following JSF Implementations: [main]
14:38:33,729 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
14:38:33,708 INFO [org.jboss.as.jacorb] (ServerService Thread Pool -- 36) JBAS016300: Activating JacORB Subsystem
14:38:33,773 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) JBAS011800: Activating Naming Subsystem
14:38:33,786 INFO [org.jboss.as.security] (ServerService Thread Pool -- 51) JBAS013171: Activating Security Subsystem
14:38:33,788 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 52) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
14:38:33,840 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 54) JBAS015537: Activating WebServices Extension
14:38:33,844 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 30) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:38:33,953 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017502: Undertow 1.1.0.Final starting
14:38:34,222 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Final
14:38:34,358 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
14:38:34,541 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017502: Undertow 1.1.0.Final starting
14:38:34,560 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 53) JBAS017527: Creating file handler for path /opt/jboss/wildfly/welcome-content
14:38:34,723 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2
14:38:34,729 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
14:38:34,753 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:38:35,104 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server.
14:38:35,469 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
14:38:35,781 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
14:38:35,965 WARN [jacorb.codeset] (MSC service thread 1-2) Warning - unknown codeset (ASCII) - defaulting to ISO-8859-1
14:38:36,122 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016330: CORBA ORB Service started
14:38:36,283 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
14:38:36,297 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "kie-server.war" (runtime-name: "kie-server.war")
14:38:38,478 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
14:38:39,027 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
14:38:39,228 WARN [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011600: AIO wasn't located on this platform, it will fall back to using pure Java NIO. If your platform is Linux, install LibAIO to enable the AIO journal
14:38:39,513 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/opt/jboss/wildfly/standalone/data/messagingjournal,bindingsDirectory=/opt/jboss/wildfly/standalone/data/messagingbindings,largeMessagesDirectory=/opt/jboss/wildfly/standalone/data/messaginglargemessages,pagingDirectory=/opt/jboss/wildfly/standalone/data/messagingpaging)
14:38:39,526 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221006: Waiting to obtain live lock
14:38:39,534 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:38:39,600 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221013: Using NIO Journal
14:38:39,907 INFO [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 56) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
14:38:40,014 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support CORE
14:38:40,073 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support AMQP
14:38:40,076 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221043: Adding protocol support STOMP
14:38:40,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221034: Waiting to obtain live lock
14:38:40,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221035: Live Server Obtained live lock
14:38:40,374 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
14:38:40,382 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
14:38:40,609 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221007: Server is now live
14:38:40,610 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [b517421a-a42e-11e6-af8a-67b5d721e620]
14:38:40,614 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.DLQ
14:38:40,813 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
14:38:40,863 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
14:38:40,866 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 58) HQ121005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "e407337732c6". If this new address is incorrect please manually configure the connector to use the proper one.
14:38:40,867 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
14:38:40,868 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
14:38:40,873 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
14:38:40,903 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
14:38:41,002 INFO [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started
14:38:41,002 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
14:38:41,005 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
14:38:41,005 INFO [org.jboss.as.messaging] (MSC service thread 1-2) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
14:38:43,340 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb-api.jar in /opt/jboss/wildfly/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.
14:38:43,407 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb-core.jar in /opt/jboss/wildfly/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
14:38:43,412 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb-impl.jar in /opt/jboss/wildfly/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
14:38:43,434 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015960: Class Path entry jaxb-core.jar in /opt/jboss/wildfly/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.
14:38:44,166 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "kie-server.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_111]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_111]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /opt/jboss/wildfly/standalone/deployments/kie-server.war/META-INF/kie-server-jms.xml
at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:99)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /opt/jboss/wildfly/standalone/deployments/kie-server.war/META-INF/kie-server-jms.xml
at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:96)
... 6 more
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:90)
... 6 more
14:38:44,198 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "kie-server.war")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"kie-server.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"kie-server.war\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"kie-server.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /opt/jboss/wildfly/standalone/deployments/kie-server.war/META-INF/kie-server-jms.xml
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011666: Could not parse file /opt/jboss/wildfly/standalone/deployments/kie-server.war/META-INF/kie-server-jms.xml
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]
Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}}
14:38:44,335 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "kie-server.war" (runtime-name : "kie-server.war")
14:38:44,338 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."kie-server.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."kie-server.war".PARSE: JBAS018733: Failed to process phase PARSE of deployment "kie-server.war"
14:38:44,386 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
14:38:44,386 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
14:38:44,387 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 22394ms - Started 221 of 271 services (1 services failed or missing dependencies, 93 services are lazy, passive or on-demand)
Dockerfile
####### BASE ############
FROM jboss/wildfly:8.2.0.Final
####### ENVIRONMENT ############
ENV JBOSS_BIND_ADDRESS 0.0.0.0
ENV KIE_REPOSITORY https://repository.jboss.org/nexus/content/groups/public-jboss
ENV KIE_VERSION 6.5.0.Final
ENV KIE_CLASSIFIER ee7
ENV KIE_CONTEXT_PATH kie-server
ENV JAVA_OPTS -XX:MaxPermSize=256m -Xms256m -Xmx512m
####### KIE-SERVER ############
RUN curl -o $HOME/$KIE_CONTEXT_PATH.war $KIE_REPOSITORY/org/kie/server/kie-server/$KIE_VERSION/kie-server-$KIE_VERSION-$KIE_CLASSIFIER.war && \
unzip -q $HOME/$KIE_CONTEXT_PATH.war -d $JBOSS_HOME/standalone/deployments/$KIE_CONTEXT_PATH.war && \
touch $JBOSS_HOME/standalone/deployments/$KIE_CONTEXT_PATH.war.dodeploy && \
rm -rf $HOME/$KIE_CONTEXT_PATH.war
####### RUNNING KIE-SERVER ############
WORKDIR $JBOSS_HOME/bin/
CMD ["./standalone.sh", "-b", "$JBOSS_BIND_ADDRESS", "-c", "standalone-full.xml"]
The docker file is based on https://hub.docker.com/r/jboss/kie-server/
Maciej Swiderski
Nov 6, 2016, 11:05:59 AM11/6/16
to Nick Wong, jBPM Setup
Kie server in 6.5 requires wildfly 10 so you need to upgrade your server as you rob on 8.2
Maciej
--
You received this message because you are subscribed to the Google Groups "jBPM Setup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jbpm-setup+...@googlegroups.com.
To post to this group, send email to jbpm-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jbpm-setup/90b6a894-5496-441c-9d3e-d0284bbb8eb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Nick Wong
Nov 6, 2016, 11:36:33 AM11/6/16
to jBPM Setup, lhw...@gmail.com
I got errors when using 6.5.0.Final with wildfly 10.0.0.Final.
JAVA_OPTS already set in environment; overriding default settings with values: -XX:MaxPermSize=256m -Xms256m -Xmx512m
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss/wildfly
JAVA: /usr/lib/jvm/java/bin/java
JAVA_OPTS: -server -XX:MaxPermSize=256m -Xms256m -Xmx512m
=========================================================================
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
16:16:03,383 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
16:16:03,838 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
16:16:03,942 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
16:16:06,457 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deployment create a file called kie-server.war.dodeploy
16:16:06,547 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
16:16:06,597 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final
16:16:06,625 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final
16:16:06,731 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final
16:16:06,735 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("interface" => "public")]) - failure description: "WFLYCTL0101: Invalid address ${jboss.bind.address:127.0.0.1} ($JBOSS_BIND_ADDRESS: Name or service not known)"
16:16:06,882 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
16:16:06,945 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
16:16:07,003 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
16:16:07,168 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
16:16:07,184 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
16:16:07,199 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
16:16:07,231 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:16:07,236 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
16:16:07,307 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
16:16:07,411 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
16:16:07,417 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=4.9.4.Final
16:16:07,445 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: "JBWS022117: Invalid address provided: $JBOSS_BIND_ADDRESS"
16:16:07,463 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.15.Final starting
16:16:07,510 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "webservices"),
("endpoint-config" => "Standard-Endpoint-Config")
]) - failure description: "WFLYWS0068: Service jboss.ws.config not available"
16:16:07,515 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "webservices"),
("endpoint-config" => "Recording-Endpoint-Config")
]) - failure description: "WFLYWS0068: Service jboss.ws.config not available"
16:16:07,516 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "webservices"),
("endpoint-config" => "Recording-Endpoint-Config"),
("pre-handler-chain" => "recording-handlers")
]) - failure description: "WFLYWS0051: Config Recording-Endpoint-Config doesn't exist"
16:16:07,549 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.15.Final starting
16:16:07,573 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "webservices"),
("endpoint-config" => "Recording-Endpoint-Config"),
("pre-handler-chain" => "recording-handlers"),
("handler" => "RecordingHandler")
]) - failure description: "WFLYWS0051: Config Recording-Endpoint-Config doesn't exist"
16:16:07,574 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "webservices"),
("client-config" => "Standard-Client-Config")
]) - failure description: "WFLYWS0068: Service jboss.ws.config not available"
16:16:07,584 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
16:16:07,586 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
16:16:07,587 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
16:16:07,986 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path '/opt/jboss/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
16:16:07,992 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
16:16:07,992 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
16:16:08,016 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 62) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: "JBWS022117: Invalid address provided: $JBOSS_BIND_ADDRESS"
16:16:08,164 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
16:16:08,165 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
16:16:09,019 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:16:09,021 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
16:16:09,082 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/jboss/wildfly/standalone/deployments
16:16:09,114 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "kie-server.war" (runtime-name: "kie-server.war")
16:16:17,879 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /opt/jboss/wildfly/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.
16:16:18,065 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-core.jar in /opt/jboss/wildfly/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
16:16:18,072 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /opt/jboss/wildfly/standalone/deployments/kie-server.war/WEB-INF/lib/jaxb-xjc-2.2.11.jar does not point to a valid jar for a Class-Path reference.
16:16:18,089 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-core.jar in /opt/jboss/wildfly/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.
16:16:18,219 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("core-service" => "management"),
("management-interface" => "http-interface")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.serverManagement.controller.management.http",
"jboss.serverManagement.controller.management.http.shutdown"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,230 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("socket-binding-group" => "standard-sockets")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.socket-binding-manager is missing [jboss.network.public]"]}
16:16:18,242 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "management-http")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.management-http"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,246 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "http")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.http"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,250 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "https")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.https"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,256 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "iiop")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.iiop"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,258 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "iiop-ssl")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.iiop-ssl"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,263 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "txn-recovery-environment")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.txn-recovery-environment"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,280 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("socket-binding" => "txn-status-manager")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.socket-binding.txn-status-manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,288 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("socket-binding-group" => "standard-sockets"),
("remote-destination-outbound-socket-binding" => "mail-smtp")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.network.outbound-socket-binding.mail-smtp"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,289 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "kie-server.war")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"kie-server.war\".PARSE is missing [jboss.ws.config]"]}
16:16:18,290 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ee"),
("context-service" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.concurrent.ee.context.service.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,292 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ee"),
("managed-thread-factory" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.concurrent.ee.threadfactory.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,297 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ee"),
("managed-executor-service" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.concurrent.ee.executor.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,313 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ee"),
("managed-scheduled-executor-service" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.concurrent.ee.scheduledexecutor.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,318 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["org.wildfly.data-source.ExampleDS"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,325 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "mail"),
("mail-session" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.mail-session.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,332 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "security")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.security.transaction-manager-locator"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,335 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jca")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.connector.transactionintegration",
"jboss.rarepository"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,343 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.jsr77.ejb"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,346 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "messaging-activemq"),
("server" => "default")
]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging-activemq.default is missing [jboss.http-upgrade-registry.default]"],
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.messaging-activemq.default.jms.manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}
}
16:16:18,348 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("data-source" => "ExampleDS")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"org.wildfly.data-source.ExampleDS",
"jboss.data-source.reference-factory.ExampleDS",
"jboss.naming.context.java.jboss.datasources.ExampleDS",
"org.wildfly.data-source.ExampleDS"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config",
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,352 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.iiop-openjdk.naming-service",
"jboss.iiop-openjdk.orb-service",
"jboss.iiop-openjdk.poa-service.irpoa",
"jboss.iiop-openjdk.poa-service.namingpoa",
"jboss.iiop-openjdk.poa-service.rootpoa"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,364 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("http-listener" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.undertow.listener.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,366 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "jca"),
("bootstrap-context" => "default")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.connector.bootstrapcontext.default"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,367 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "jca"),
("cached-connection-manager" => "cached-connection-manager")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.cached-connection-manager"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,368 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.concurrent.ee.tsp",
"jboss.naming.context.java.TransactionManager",
"jboss.naming.context.java.jboss.TransactionManager",
"jboss.naming.context.java.jboss.TransactionSynchronizationRegistry",
"jboss.naming.context.java.jboss.UserTransaction",
"jboss.txn.ArjunaRecoveryManager",
"jboss.txn.ArjunaTransactionManager",
"jboss.txn.TransactionManager",
"jboss.txn.TransactionSynchronizationRegistry",
"jboss.txn.UserTransaction"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,370 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => [
"jboss.ejb.default-local-ejb-receiver-service",
"jboss.ejb.tx-recovery-service",
"jboss.ejb.utilities",
"jboss.ejb3.ejbClientContext.default",
"jboss.ejb3.localEjbReceiver.value"
],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,372 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "timer-service"),
("file-data-store" => "default-file-store")
]) - failure description: {"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.ejb3.timerService.timerPersistence.default-file-store"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}}
16:16:18,378 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "ejb3"),
("service" => "remote")
]) - failure description: {
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"],
"WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
"Services that were unable to start:" => ["jboss.ejb.remote-transactions-repository"],
"Services that may be the cause:" => [
"jboss.http-upgrade-registry.default",
"jboss.network.public",
"jboss.remoting.remotingConnectorInfoService.http-remoting-connector",
"jboss.ws.config"
]
}
}
16:16:18,422 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "kie-server.war" (runtime-name : "kie-server.war")
16:16:18,424 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.http-upgrade-registry.default (missing) dependents: [service jboss.messaging-activemq.default]
service jboss.network.public (missing) dependents: [service jboss.socket-binding-manager]
service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]
service jboss.ws.config (missing) dependents: [service jboss.deployment.unit."kie-server.war".PARSE]
16:16:18,648 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0063: Http management interface is not enabled
16:16:18,652 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0054: Admin console is not enabled
16:16:18,654 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 15995ms - Started 215 of 569 services (52
services failed or missing dependencies, 383 services are lazy, passive or on-demand)
16:16:18,853 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment kie-server.war (runtime-name: kie-server.war) in 139ms
16:16:18,954 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "kie-server.war" (runtime-name: "kie-server.war")
16:16:23,471 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found kie-server.war in deployment directory. To trigger deployment create a file called kie-server.war.dodeploy
####### BASE ############
FROM jboss/wildfly:10.0.0.Final
####### ENVIRONMENT ############
ENV JBOSS_BIND_ADDRESS 0.0.0.0
ENV KIE_REPOSITORY https://repository.jboss.org/nexus/content/groups/public-jboss
ENV KIE_VERSION 6.5.0.Final
ENV KIE_CLASSIFIER ee7
ENV KIE_CONTEXT_PATH kie-server
ENV JAVA_OPTS -XX:MaxPermSize=256m -Xms256m -Xmx512m
####### KIE-SERVER ############
RUN curl -o $HOME/$KIE_CONTEXT_PATH.war $KIE_REPOSITORY/org/kie/server/kie-server/$KIE_VERSION/kie-server-$KIE_VERSION-$KIE_CLASSIFIER.war && \
unzip -q $HOME/$KIE_CONTEXT_PATH.war -d $JBOSS_HOME/standalone/deployments/$KIE_CONTEXT_PATH.war && \
touch $JBOSS_HOME/standalone/deployments/$KIE_CONTEXT_PATH.war.dodeploy && \
rm -rf $HOME/$KIE_CONTEXT_PATH.war
####### RUNNING KIE-SERVER ############
WORKDIR $JBOSS_HOME/bin/
CMD ["./standalone.sh", "-b", "$JBOSS_BIND_ADDRESS", "-c", "standalone-full.xml"]
Nick Wong
Nov 6, 2016, 11:41:13 AM11/6/16
to jBPM Setup, lhw...@gmail.com
My dockerfile for 6.5.0.Final with wildfly 10.0.0.Final
Nick Wong
Nov 6, 2016, 5:56:16 PM11/6/16
to jBPM Setup, lhw...@gmail.com
Nick Wong
Nov 6, 2016, 7:09:54 PM11/6/16
to jBPM Setup, lhw...@gmail.com
It is confirmed that the cause is the passing of -b bind address. It has nothing to do with kie-server.
Reply all
Reply to author
Forward
0 new messages