Versão atual:

Ao reiniciar o serviço do Fluig, o mesmo não inicia mais

Pessoal, o serviço do Fluig foi reiniciado, porém agora está apresentando erro na reinicialização referente ao WildFly. Segue o log de erro.

2018-03-14 12:26:32,699 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final
2018-03-14 12:26:33,237 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
2018-03-14 12:26:33,504 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
2018-03-14 12:26:33,740 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.4.0.Final
2018-03-14 12:26:33,774 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.4.0.Final
2018-03-14 12:26:33,844 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.21.Final
2018-03-14 12:26:36,690 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) initializeParsers (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl@7e989b88)
2018-03-14 12:26:36,720 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) initialize (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionContextImpl@593faff8)
2018-03-14 12:26:36,726 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) getResourceDescriptionResolver (keyPrefix=null) = dbupdate
2018-03-14 12:26:36,774 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) SubsystemDefinition ()
2018-03-14 12:26:36,774 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) registerAttributes (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@15b1975a)
2018-03-14 12:26:36,774 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) registerOperations (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@15b1975a)
2018-03-14 12:26:37,759 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 29) populateModel (operation={
    "operation" => "add",
    "address" => [("subsystem" => "dbupdate")]
}, model=undefined)
2018-03-14 12:26:38,267 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 13) performBoottime (context=org.jboss.as.controller.ParallelBootOperationContext@54f3ed3, operation={
    "operation" => "add",
    "address" => [("subsystem" => "dbupdate")]
}, resource=org.jboss.as.controller.registry.BasicResource@268e48a8)
2018-03-14 12:26:38,297 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 40) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
2018-03-14 12:26:38,427 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 42) WFLYSEC0002: Activating Security Subsystem
2018-03-14 12:26:38,526 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 38) WFLYWS0002: Activating WebServices Extension
2018-03-14 12:26:38,538 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36)    WCM MOD SERV ON
2018-03-14 12:26:38,539 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36)           DIR: /mnt/part_app/fluig/appserver/apps
2018-03-14 12:26:38,539 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36)       REFRESH: 15000
2018-03-14 12:26:38,540 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0001: Activating Infinispan subsystem.
2018-03-14 12:26:38,506 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.6.Final
2018-03-14 12:26:38,561 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 60) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
2018-03-14 12:26:38,536 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 63) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
2018-03-14 12:26:38,595 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 48) WFLYNAM0001: Activating Naming Subsystem
2018-03-14 12:26:38,639 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Undertow 1.4.0.Final starting
2018-03-14 12:26:38,681 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 13) execute (processorTarget=org.jboss.as.server.AbstractDeploymentChainStep$1@71b89743)
2018-03-14 12:26:38,703 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
2018-03-14 12:26:38,710 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 58) WFLYIIOP0001: Activating IIOP Subsystem
2018-03-14 12:26:38,928 INFO  [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
2018-03-14 12:26:39,033 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2018-03-14 12:26:39,056 INFO  [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
2018-03-14 12:26:39,069 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = mysqlDriver
2018-03-14 12:26:40,033 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/FluigDSRO
2018-03-14 12:26:40,075 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
2018-03-14 12:26:40,085 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: Host default-host starting
2018-03-14 12:26:40,343 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Address already in use /10.171.234.4:8080
    at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:151)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
    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)

2018-03-14 12:26:40,687 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:/jdbc/FluigDS]
2018-03-14 12:26:40,981 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-6) WFLYIIOP0009: CORBA ORB Service started
2018-03-14 12:26:41,178 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore /mnt/part_app/fluig/appserver/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
2018-03-14 12:26:41,718 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
2018-03-14 12:26:41,823 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 68) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,830 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 68) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,833 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,838 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 69) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,840 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 66) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,841 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 68) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,842 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 68) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:41,849 INFO  [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 69) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
2018-03-14 12:26:42,668 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started LOCAL_MAP cache from LOCAL_MAP container
2018-03-14 12:26:42,689 INFO  [com.totvs.technology.wcm.WCMService] (MSC service thread 1-6)    WCM MOD SERV START
2018-03-14 12:26:42,773 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) WFLYCLINF0002: Started default-host cache from web container
2018-03-14 12:26:44,702 INFO  [com.totvs.technology.wcm.WCMService] (Thread-93)    WCM DEPLOY STARTING
2018-03-14 12:26:45,299 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
    "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.ws.config"],
        "Services that may be the cause:" => [
            "jboss.http-upgrade-registry.default",
            "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:45,309 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - failure description: {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
    "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.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:45,327 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
    "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.ejb3.ejbClientContext.default",
            "jboss.ejb3.localEjbReceiver.value"
        ],
        "Services that may be the cause:" => [
            "jboss.http-upgrade-registry.default",
            "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:45,327 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "ejb3"),
    ("service" => "remote")
]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"]
}
2018-03-14 12:26:45,329 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "messaging-activemq"),
    ("server" => "default")
]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => ["jboss.http-upgrade-registry.default"],
    "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.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:45,330 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: {
    "WFLYCTL0080: Failed services" => {"jboss.undertow.listener.default" => "org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Address already in use /10.171.234.4:8080"},
    "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.listener.default"],
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined
}
2018-03-14 12:26:45,462 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.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector] 
WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Address already in use /10.171.234.4:8080

2018-03-14 12:26:46,354 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started (with errors) in 14937ms - Started 399 of 782 services (9 services failed or missing dependencies, 559 services are lazy, passive or on-demand)
2018-03-14 12:26:46,627 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "01001-fluig-database-wcm.jar" (runtime-name: "01001-fluig-database-wcm.jar")
2018-03-14 12:26:46,798 ERROR [org.jboss.as.controller.management-operation] (WCM DEPLOYER-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "01001-fluig-database-wcm.jar")]) - failure description: {
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
    "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.deployment.unit.\"01001-fluig-database-wcm.jar\".PARSE"],
        "Services that may be the cause:" => [
            "jboss.http-upgrade-registry.default",
            "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:46,801 ERROR [org.jboss.as.server] (WCM DEPLOYER-threads - 1) WFLYSRV0021: Deploy of deployment "01001-fluig-database-wcm.jar" was rolled back with the following failure message: 
{
    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
    "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.deployment.unit.\"01001-fluig-database-wcm.jar\".PARSE"],
        "Services that may be the cause:" => [
            "jboss.http-upgrade-registry.default",
            "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
        ]
    }
}
2018-03-14 12:26:46,826 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment 01001-fluig-database-wcm.jar (runtime-name: 01001-fluig-database-wcm.jar) in 25ms
2018-03-14 12:26:46,827 INFO  [org.jboss.as.controller] (WCM DEPLOYER-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.undertow.listener.default: org.jboss.msc.service.StartException in service jboss.undertow.listener.default: Address already in use /10.171.234.4:8080

2018-03-14 12:26:46,831 ERROR [stderr] (Thread-93) java.lang.Exception: {
2018-03-14 12:26:46,835 ERROR [stderr] (Thread-93)     "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined,
2018-03-14 12:26:46,836 ERROR [stderr] (Thread-93)     "WFLYCTL0288: One or more services were unable to start due to one or more indirect dependencies not being available." => {
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)         "Services that were unable to start:" => ["jboss.deployment.unit.\"01001-fluig-database-wcm.jar\".PARSE"],
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)         "Services that may be the cause:" => [
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)             "jboss.http-upgrade-registry.default",
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)             "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)         ]
2018-03-14 12:26:46,837 ERROR [stderr] (Thread-93)     }
2018-03-14 12:26:46,838 ERROR [stderr] (Thread-93) }
2018-03-14 12:26:46,838 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.WCMStandaloneDeploymentManager$ServerDeploymentPlanResultFuture.getActionResult(WCMStandaloneDeploymentManager.java:263)
2018-03-14 12:26:46,839 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.WCMStandaloneDeploymentManager$ServerDeploymentPlanResultFuture.getResultFromNode(WCMStandaloneDeploymentManager.java:251)
2018-03-14 12:26:46,840 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.WCMStandaloneDeploymentManager$ServerDeploymentPlanResultFuture.get(WCMStandaloneDeploymentManager.java:231)
2018-03-14 12:26:46,840 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.WCMStandaloneDeploymentManager$ServerDeploymentPlanResultFuture.get(WCMStandaloneDeploymentManager.java:146)
2018-03-14 12:26:46,840 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.StandaloneDeployer.deploy(StandaloneDeployer.java:124)
2018-03-14 12:26:46,841 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.deployment.StandaloneDeployer.deploy(StandaloneDeployer.java:234)
2018-03-14 12:26:46,841 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.WCMService.doStartUp(WCMService.java:488)
2018-03-14 12:26:46,843 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.WCMService.access$100(WCMService.java:92)
2018-03-14 12:26:46,843 ERROR [stderr] (Thread-93)     at com.totvs.technology.wcm.WCMService$StandAloneScanner.run(WCMService.java:1032)
2018-03-14 12:26:46,843 ERROR [stderr] (Thread-93)     at java.lang.Thread.run(Thread.java:745)
2018-03-14 12:26:46,903 ERROR [com.totvs.technology.wcm.WCMService] (Thread-93)    WCM MOD SERV STARTUP FAILED

Versão (1):

Ver a versão formatada

Ao reiniciar o serviço do Fluig, o mesmo não inicia mais

Comentário

new question