Erro 404 inicialização fluig windows

2019-12-11 09:57:42,222 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.2.Final 2019-12-11 09:57:42,385 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final 2019-12-11 09:57:42,453 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting 2019-12-11 09:57:42,510 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.4.0.Final 2019-12-11 09:57:42,514 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.4.0.Final 2019-12-11 09:57:42,692 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.21.Final 2019-12-11 09:57:48,617 INFO [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) initializeParsers (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl@55680c54) 2019-12-11 09:57:48,618 INFO [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) initialize (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionContextImpl@561afe2b) 2019-12-11 09:57:48,620 INFO [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 35) getResourceDescriptionResolver (keyPrefix=null) = dbupdate 2019-12-11 09:57:48,628 INFO [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) SubsystemDefinition () 2019-12-11 09:57:48,629 INFO [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) registerAttributes (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@483a3549) 2019-12-11 09:57:48,629 INFO [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 35) registerOperations (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@483a3549) 2019-12-11 09:57:48,968 INFO [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 2) populateModel (operation={ "operation" => "add", "address" => [("subsystem" => "dbupdate")] }, model=undefined) 2019-12-11 09:57:49,121 INFO [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 18) performBoottime (context=org.jboss.as.controller.ParallelBootOperationContext@7fa42d3a, operation={ "operation" => "add", "address" => [("subsystem" => "dbupdate")] }, resource=org.jboss.as.controller.registry.BasicResource@8ea4c3f) 2019-12-11 09:57:49,125 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. 2019-12-11 09:57:49,136 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) WFLYSEC0002: Activating Security Subsystem 2019-12-11 09:57:49,153 INFO [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 18) execute (processorTarget=org.jboss.as.server.AbstractDeploymentChainStep$1@5d3c9fa5) 2019-12-11 09:57:49,147 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.6.Final 2019-12-11 09:57:49,168 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0001: Activating Infinispan subsystem. 2019-12-11 09:57:49,179 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 38) WFLYWS0002: Activating WebServices Extension 2019-12-11 09:57:49,190 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main] 2019-12-11 09:57:49,191 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 60) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors 2019-12-11 09:57:49,192 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 48) WFLYNAM0001: Activating Naming Subsystem 2019-12-11 09:57:49,228 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 58) WFLYIIOP0001: Activating IIOP Subsystem 2019-12-11 09:57:49,232 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final) 2019-12-11 09:57:49,245 INFO [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36) WCM MOD SERV ON 2019-12-11 09:57:49,245 INFO [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36) DIR: D:\fluig\appserver\apps 2019-12-11 09:57:49,245 INFO [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 36) REFRESH: 15000 2019-12-11 09:57:49,419 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.4.0.Final starting 2019-12-11 09:57:49,503 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 63) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0) 2019-12-11 09:57:49,508 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = sqlserverDriver 2019-12-11 09:57:49,508 INFO [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Starting Naming Service 2019-12-11 09:57:49,509 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default] 2019-12-11 09:57:49,928 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 39) WFLYUT0014: Creating file handler for path 'D:\fluig/repository/wcmdir/static' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]'] 2019-12-11 09:57:49,974 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/FluigDSRO 2019-12-11 09:57:49,974 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/AppDS 2019-12-11 09:57:50,162 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:/jdbc/FluigDS] 2019-12-11 09:57:50,176 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server. 2019-12-11 09:57:50,177 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting 2019-12-11 09:57:50,216 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 10.0.75.1:8081 2019-12-11 09:57:50,447 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO. 2019-12-11 09:57:50,452 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-1) WFLYDM0111: Keystore D:\fluig\appserver\domain\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost 2019-12-11 09:57:50,731 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=D:\fluig\appserver\domain\servers\fluig1\data\activemq\journal,bindingsDirectory=D:\fluig\appserver\domain\servers\fluig1\data\activemq\bindings,largeMessagesDirectory=D:\fluig\appserver\domain\servers\fluig1\data\activemq\largemessages,pagingDirectory=D:\fluig\appserver\domain\servers\fluig1\data\activemq\paging) 2019-12-11 09:57:50,802 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221013: Using NIO Journal 2019-12-11 09:57:50,878 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final 2019-12-11 09:57:50,958 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 76) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,960 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 76) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,959 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 75) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,958 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,963 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 75) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,963 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,965 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,966 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 71) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated. 2019-12-11 09:57:50,971 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6) 2019-12-11 09:57:51,170 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE 2019-12-11 09:57:51,200 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started 2019-12-11 09:57:51,319 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP 2019-12-11 09:57:51,331 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ 2019-12-11 09:57:51,332 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP 2019-12-11 09:57:51,473 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 71) WFLYCLINF0002: Started default-host cache from web container 2019-12-11 09:57:51,473 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started LOCAL_MAP cache from LOCAL_MAP container 2019-12-11 09:57:51,477 INFO [com.totvs.technology.wcm.WCMService] (MSC service thread 1-5) WCM MOD SERV START 2019-12-11 09:57:52,208 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 2019-12-11 09:57:52,209 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 2019-12-11 09:57:52,209 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor 2019-12-11 09:57:52,208 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor 2019-12-11 09:57:52,528 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221007: Server is now live 2019-12-11 09:57:52,529 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017 [nodeID=d62965a1-1c06-11ea-8b48-d54231a76b0c] 2019-12-11 09:57:52,559 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 66) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechQueueConnectionFactory 2019-12-11 09:57:52,603 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 101) AMQ221003: trying to deploy queue jms.queue.DLQ 2019-12-11 09:57:52,626 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 100) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderSocial 2019-12-11 09:57:52,627 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 98) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialQueueConnectionFactory 2019-12-11 09:57:52,628 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 89) AMQ221003: trying to deploy queue jms.topic.MessagingIntegrationListenerTopic 2019-12-11 09:57:52,634 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 97) AMQ221003: trying to deploy queue jms.queue.FluigMailQueue 2019-12-11 09:57:52,635 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 99) AMQ221003: trying to deploy queue jms.queue.TOTVSTechDeployQueue 2019-12-11 09:57:52,636 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 102) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechConnectionFactory 2019-12-11 09:57:52,636 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 95) AMQ221003: trying to deploy queue jms.topic.FluigNotificationTopic 2019-12-11 09:57:52,637 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 93) AMQ221003: trying to deploy queue jms.topic.wdkDocument 2019-12-11 09:57:52,637 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 92) AMQ221003: trying to deploy queue jms.queue.TOTVSTechIntegrationRegisterQueue 2019-12-11 09:57:52,638 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 96) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialPostDeliveryConnectionFactory 2019-12-11 09:57:52,638 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 82) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialDeliveryQueueConnectionFactory 2019-12-11 09:57:52,639 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 91) AMQ221003: trying to deploy queue jms.topic.TOTVSTechSocialListenerTopic 2019-12-11 09:57:52,639 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 94) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechTopicConnectionFactory 2019-12-11 09:57:52,640 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 87) AMQ221003: trying to deploy queue jms.topic.TOTVSTechIntegrationListenerTopic 2019-12-11 09:57:52,640 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 85) AMQ221003: trying to deploy queue jms.queue.WorkflowServiceAsyncQueue 2019-12-11 09:57:52,641 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 88) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory 2019-12-11 09:57:52,641 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 90) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue 2019-12-11 09:57:52,642 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderFdn 2019-12-11 09:57:52,642 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 83) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderEcm 2019-12-11 09:57:52,643 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 86) AMQ221003: trying to deploy queue jms.queue.TOTVSTechocialPostDeliveryQueue 2019-12-11 09:57:52,643 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 80) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/FluigXAConnectionFactory 2019-12-11 09:57:52,643 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 81) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderLms 2019-12-11 09:57:52,644 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 79) AMQ221003: trying to deploy queue jms.queue.FluigThumbnail 2019-12-11 09:57:52,644 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ221003: trying to deploy queue jms.queue.QuotaControl 2019-12-11 09:57:52,645 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 70) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/FluigRemoteXAConnectionFactory 2019-12-11 09:57:52,645 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 72) AMQ221003: trying to deploy queue jms.queue.FluigDeployQueue 2019-12-11 09:57:52,646 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69) AMQ221003: trying to deploy queue jms.queue.TOTVSTechSocialQueue 2019-12-11 09:57:52,646 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderPortal 2019-12-11 09:57:52,647 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 77) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechLocalQueueConnectionFactory 2019-12-11 09:57:52,647 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 67) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory 2019-12-11 09:57:52,648 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221003: trying to deploy queue jms.queue.Document 2019-12-11 09:57:52,648 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221003: trying to deploy queue jms.queue.TOTVSTechAsyncQueue 2019-12-11 09:57:52,648 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221003: trying to deploy queue jms.queue.ECMNotificationQueue 2019-12-11 09:57:52,649 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 76) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TopicConnectionFactory 2019-12-11 09:57:52,649 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221003: trying to deploy queue jms.queue.FluigNotificationPushSenderBpm 2019-12-11 09:57:52,739 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0007: Registered connection factory java:/JmsXA 2019-12-11 09:57:52,779 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-7) Resource adaptor started 2019-12-11 09:57:52,780 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatoractivemq-ra 2019-12-11 09:57:52,781 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA] 2019-12-11 09:57:52,782 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory 2019-12-11 09:57:53,474 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 11748ms - Started 495 of 798 services (562 services are lazy, passive or on-demand) 2019-12-11 09:57:53,479 INFO [com.totvs.technology.wcm.WCMService] (Thread-97) WCM DEPLOY STARTING 2019-12-11 09:57:54,074 FATAL [com.fluig.startup.validation] (Thread-97) =================================================================== 2019-12-11 09:57:54,074 FATAL [com.fluig.startup.validation] (Thread-97) == Alterar o collation da base == 2019-12-11 09:57:54,074 FATAL [com.fluig.startup.validation] (Thread-97) == Collation correto Latin1_General_CI_AS == 2019-12-11 09:57:54,074 FATAL [com.fluig.startup.validation] (Thread-97) =================================================================== 2019-12-11 09:57:54,075 ERROR [stderr] (Thread-97) com.totvs.technology.wcm.exception.StartupException: Collation Error.

2019-12-11 09:57:54,075 ERROR [stderr] (Thread-97) at com.totvs.technology.wcm.validation.ValidateCollateCharset.execute(ValidateCollateCharset.java:39)

2019-12-11 09:57:54,075 ERROR [stderr] (Thread-97) at com.totvs.technology.wcm.WCMService.executeValidation(WCMService.java:1467)

2019-12-11 09:57:54,075 ERROR [stderr] (Thread-97) at com.totvs.technology.wcm.WCMService.doStartUp(WCMService.java:446)

2019-12-11 09:57:54,075 ERROR [stderr] (Thread-97) at com.totvs.technology.wcm.WCMService.access$100(WCMService.java:102)

2019-12-11 09:57:54,076 ERROR [stderr] (Thread-97) at com.totvs.technology.wcm.WCMService$StandAloneScanner.run(WCMService.java:999)

2019-12-11 09:57:54,076 ERROR [stderr] (Thread-97) at java.lang.Thread.run(Thread.java:748)

2019-12-11 09:57:54,076 INFO [stdout] (Thread-97) *

2019-12-11 09:57:54,076 INFO [stdout] (Thread-97) Startup stoped.

2019-12-11 09:57:54,076 INFO [stdout] (Thread-97) *

compartilhar
  1. Você vai ver essas setas em qualquer página de pergunta. Com elas, você pode dizer se uma pergunta ou uma resposta foram relevantes ou não.
  2. Edite sua pergunta ou resposta caso queira alterar ou adicionar detalhes.
  3. Caso haja alguma dúvida sobre a pergunta, adicione um comentário. O espaço de respostas deve ser utilizado apenas para responder a pergunta.
  4. Se o autor da pergunta marcar uma resposta como solucionada, esta marca aparecerá.
  5. Clique aqui para mais detalhes sobre o funcionamento do fluig Forum!

1 resposta

Não é a resposta que estava procurando? Procure outras perguntas com as tags erro404 ou faça a sua própria pergunta.