Migração Fluig 1.6 para 1.7

Olá comunidade Fluig.

Neste final de semana realizamos a migração da versão 1.6. do Fluig para 1.7 no ambiente de teste. Entretanto, os serviços do Fluig não iniciaram, deixando assim a aplicação com erro 404 Page Not Found.

Verificando o log do servidor foi possível encontrar a seguinte mensagem de erro pelo.

2020-07-04 15:25:55,854 INFO  [org.xnio] (MSC service thread 1-2) XNIO version 3.7.3.Final
2020-07-04 15:25:55,862 INFO  [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.7.3.Final
2020-07-04 15:25:55,898 INFO  [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.15.Final
2020-07-04 15:25:56,233 INFO  [org.wildfly.security] (ServerService Thread Pool -- 2) ELY00001: WildFly Elytron version 1.10.4.Final
2020-07-04 15:25:57,285 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 42) initializeParsers (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionParsingContextImpl@fc5647e)
2020-07-04 15:25:57,285 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 42) initialize (context=org.jboss.as.controller.extension.ExtensionRegistry$ExtensionContextImpl@79a1d4a1)
2020-07-04 15:25:57,286 INFO  [com.fluig.database.service.extension.SubsystemExtension] (ServerService Thread Pool -- 42) getResourceDescriptionResolver (keyPrefix=null) = dbupdate
2020-07-04 15:25:57,287 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 42) SubsystemDefinition ()
2020-07-04 15:25:57,288 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 42) registerAttributes (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@51c3dbe)
2020-07-04 15:25:57,288 INFO  [com.fluig.database.service.extension.SubsystemDefinition] (ServerService Thread Pool -- 42) registerOperations (resourceRegistration=org.jboss.as.controller.registry.ConcreteResourceRegistration@51c3dbe)
2020-07-04 15:25:58,071 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 4) populateModel (operation={
    "operation" => "add",
    "address" => [("subsystem" => "dbupdate")]
}, model=undefined)
2020-07-04 15:25:58,271 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 18) performBoottime (context=org.jboss.as.controller.ParallelBootOperationContext@19ce8524, operation={
    "operation" => "add",
    "address" => [("subsystem" => "dbupdate")]
}, resource=org.jboss.as.controller.registry.BasicResource@7b7f2ee5)
2020-07-04 15:25:58,286 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 45) WFLYWS0002: Activating WebServices Extension
2020-07-04 15:25:58,296 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 49) WFLYSEC0002: Activating Security Subsystem
2020-07-04 15:25:58,288 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 47) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
2020-07-04 15:25:58,335 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 55) WFLYNAM0001: Activating Naming Subsystem
2020-07-04 15:25:58,357 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 43)    WCM MOD SERV ON
2020-07-04 15:25:58,357 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 43)           DIR: /opt/fluig/appserver/apps
2020-07-04 15:25:58,357 INFO  [com.totvs.technology.wcm.WCMService] (ServerService Thread Pool -- 43)       REFRESH: 15000
2020-07-04 15:25:58,320 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 61) WFLYJSF0007: Activated the following JSF Implementations: [main]
2020-07-04 15:25:58,356 INFO  [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 57) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
2020-07-04 15:25:58,346 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 66) WFLYRS0016: RESTEasy version 3.9.1.Final
2020-07-04 15:25:58,370 INFO  [com.fluig.database.service.extension.SubsystemAdd] (ServerService Thread Pool -- 18) execute (processorTarget=org.jboss.as.server.AbstractDeploymentChainStep$1@56457a98)
2020-07-04 15:25:58,374 INFO  [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 56) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
2020-07-04 15:25:58,376 INFO  [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.3.Final
2020-07-04 15:25:58,384 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 69) WFLYIIOP0001: Activating IIOP Subsystem
2020-07-04 15:25:58,393 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 68) WFLYCLINF0001: Activating Infinispan subsystem.
2020-07-04 15:25:58,382 INFO  [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
2020-07-04 15:25:58,434 INFO  [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Starting Naming Service
2020-07-04 15:25:58,441 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 67) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
2020-07-04 15:25:58,468 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 2.0.27.Final starting
2020-07-04 15:25:58,474 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 46) WFLYUT0014: Creating file handler for path '/opt/fluig//repository/wcmdir/static' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2020-07-04 15:25:58,473 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 76) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
2020-07-04 15:25:58,484 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2020-07-04 15:25:58,562 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = mysqlDriver
2020-07-04 15:25:59,066 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/FluigDSRO
2020-07-04 15:25:59,095 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/AppDS
2020-07-04 15:25:59,119 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
2020-07-04 15:25:59,120 INFO  [com.totvs.technology.wcm.WCMService] (MSC service thread 1-4)    WCM MOD SERV START
2020-07-04 15:25:59,144 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: Host default-host starting
2020-07-04 15:25:59,253 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 54.39.21.0:8080
2020-07-04 15:25:59,257 INFO  [org.jboss.as.patching] (MSC service thread 1-6) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2020-07-04 15:25:59,349 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-2) WFLYDM0111: Keystore /opt/fluig/appserver/domain/configuration/application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
2020-07-04 15:25:59,473 INFO  [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.3) 
2020-07-04 15:25:59,584 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0493: EJB subsystem suspension complete
2020-07-04 15:25:59,710 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:/jdbc/FluigDS]
2020-07-04 15:25:59,775 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-7) WFLYIIOP0009: CORBA ORB Service started
2020-07-04 15:25:59,883 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=/opt/fluig/appserver/domain/servers/fluig1/data/activemq/journal,bindingsDirectory=/opt/fluig/appserver/domain/servers/fluig1/data/activemq/bindings,largeMessagesDirectory=/opt/fluig/appserver/domain/servers/fluig1/data/activemq/largemessages,pagingDirectory=/opt/fluig/appserver/domain/servers/fluig1/data/activemq/paging)
2020-07-04 15:25:59,976 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221012: Using AIO Journal
2020-07-04 15:26:00,014 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.16.Final
2020-07-04 15:26:00,091 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
2020-07-04 15:26:00,092 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
2020-07-04 15:26:00,092 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2020-07-04 15:26:00,093 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
2020-07-04 15:26:00,201 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221034: Waiting indefinitely to obtain live lock
2020-07-04 15:26:00,202 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221035: Live Server Obtained live lock
2020-07-04 15:26:00,728 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
2020-07-04 15:26:00,729 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2020-07-04 15:26:00,729 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
2020-07-04 15:26:00,729 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
2020-07-04 15:26:00,751 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 81) WFLYCLINF0002: Started default-host cache from web container
2020-07-04 15:26:01,137 INFO  [com.totvs.technology.wcm.WCMService] (Thread-91)    WCM DEPLOY STARTING
2020-07-04 15:26:01,774 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221007: Server is now live
2020-07-04 15:26:01,774 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.10.1 [default, nodeID=30f51d55-be2c-11ea-ba14-fa163ed82b2f] 
2020-07-04 15:26:01,804 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 81) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/FluigRemoteXAConnectionFactory
2020-07-04 15:26:01,890 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechQueueConnectionFactory
2020-07-04 15:26:01,891 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialDeliveryQueueConnectionFactory
2020-07-04 15:26:01,897 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 87) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechLocalQueueConnectionFactory
2020-07-04 15:26:01,914 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:/JmsXA
2020-07-04 15:26:01,977 FATAL [com.fluig.startup.validation] (Thread-91) ============================================================================================
2020-07-04 15:26:01,977 FATAL [com.fluig.startup.validation] (Thread-91) == Installed version of fluig is not compatible with the database ==========================
2020-07-04 15:26:01,977 FATAL [com.fluig.startup.validation] (Thread-91) == Cannot upgrade to a version with the database version greater ===========================
2020-07-04 15:26:01,982 FATAL [com.fluig.startup.validation] (Thread-91) == Cannot upgrade to a version 1.7.x with the database version under Fluig 1.6.5-200318 ====
2020-07-04 15:26:01,982 FATAL [com.fluig.startup.validation] (Thread-91) == For more information, visit: https://tdn.totvs.com/x/h5lGGg =============================
2020-07-04 15:26:01,982 FATAL [com.fluig.startup.validation] (Thread-91) ============================================================================================
2020-07-04 15:26:01,983 ERROR [stderr] (Thread-91) com.totvs.technology.wcm.exception.StartupException: Update
2020-07-04 15:26:01,983 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.validation.UpdateVersionChecker.throwUpdateException(UpdateVersionChecker.java:70)
2020-07-04 15:26:01,983 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.validation.UpdateVersionChecker.execute(UpdateVersionChecker.java:28)
2020-07-04 15:26:01,983 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.WCMService.executeValidation(WCMService.java:1616)
2020-07-04 15:26:01,983 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.WCMService.doStartUp(WCMService.java:459)
2020-07-04 15:26:01,984 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.WCMService.access$000(WCMService.java:111)
2020-07-04 15:26:01,984 ERROR [stderr] (Thread-91)     at com.totvs.technology.wcm//com.totvs.technology.wcm.WCMService$StandAloneScanner.run(WCMService.java:1067)
2020-07-04 15:26:01,984 ERROR [stderr] (Thread-91)     at java.base/java.lang.Thread.run(Thread.java:834)
2020-07-04 15:26:01,984 INFO  [stdout] (Thread-91) ***************************************
2020-07-04 15:26:01,984 INFO  [stdout] (Thread-91) Startup stoped.
2020-07-04 15:26:01,984 INFO  [stdout] (Thread-91) ***************************************
2020-07-04 15:26:02,045 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-3) AMQ151007: Resource adaptor started
2020-07-04 15:26:02,046 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-3) IJ020002: Deployed: file://RaActivatoractivemq-ra
2020-07-04 15:26:02,053 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
2020-07-04 15:26:02,053 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
2020-07-04 15:26:02,089 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 86) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
2020-07-04 15:26:02,090 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 117) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialPostDeliveryConnectionFactory
2020-07-04 15:26:02,123 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 111) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechConnectionFactory
2020-07-04 15:26:02,124 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 110) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechSocialQueueConnectionFactory
2020-07-04 15:26:02,136 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 107) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TOTVSTechTopicConnectionFactory
2020-07-04 15:26:02,193 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 95) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2020-07-04 15:26:02,203 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 89) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/FluigXAConnectionFactory
2020-07-04 15:26:02,207 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 80) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/TopicConnectionFactory
2020-07-04 15:26:02,331 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2020-07-04 15:26:02,336 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) started in 7768ms - Started 496 of 878 services (614 services are lazy, passive or on-demand)
  • Verifiquei a versão do banco de dados do ambiente de teste e a mesma encontra-se na versão 5.7 do MySQL que está apta para atender a nova versão do Fluig 1.7.

É necessário realizar alteração de alguma parâmetro via banco de dados ou é algum arquivo de configuração?

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!

4 respostas

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