Solucionado (ver solução)
Solucionado
(ver solução)
27
respostas

Erro após instalar o driver mysql - Aula 3 , Atividade 7 - Criando o Datasource

Referente ao curso EJB com Jakarta EE: API Rest com o servidor WildFly, no capítulo Persistência com JPA e atividade Criando o Datasource

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Após realizar os códigos no prompt de comando para instalar o driver, surgiu a mensagem {"outcome => "success"}. Na vídeo aula, no minuto 7:52 do vídeo Atividade 7 - Criando o Datasource da Aula 3 , o professor digita no navegador: "localhost:8080" e em seguida abre a página do Wildfly. Fiz isso e funcionou. Porém quando eu cliquei no link: Administration Console, a página apresentou o seguinte texto: "Welcome to WildFly Your WildFly Application Server is running. However you have not yet added any users to be able to access the admin console.

To add a new user execute the add-user.bat script within the bin folder of your WildFly installation and enter the requested information.

By default the realm name used by WildFly is "ManagementRealm" this is already selected by default.

After you have added the user follow this link to Try Again."

e o endereço mostrado na barra de endereço do navegador foi: "http://localhost:9990/error/index_win.html".

Estou no aguardo de uma solução para que eu possa continuar o curso.

Grato.

27 respostas
por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo, bom dia. Você precisa configurar o usuário para acessar a console do servidor. Criamos um tutorial nesta seção aqui: https://cursos.alura.com.br/course/ejb-jakarta-ee-api-rest-wildfly/task/81584 com este passo a passo você conseguirá incluir o seu usuário e prosseguir com as aulas =)

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Olá, João. Deu certo. Eu pulei essa etapa pensando que fosse exatamente igual a do vídeo. Desculpe pelo vacilo.

Agora tenho outro problema lá na configuração do Datasource. Fiz todas as etapas acompanhando as suas explicações no vídeo e ao clicar no botão Test Conection apareceu a seguinte mensagem de erro:

17:39:36,941 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("test-connection-in-pool") failed - address: ([ ("subsystem" => "datasources"), ("data-source" => "AgendamentoEmailDS") ]) - failure description: "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid" 17:39:36,943 INFO [org.jboss.as.controller] (External Management Request Threads -- 1) WFLYCTL0183: Service status report WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."agendamento-email-0.0.1-SNAPSHOT.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "agendamento-email-0.0.1-SNAPSHOT.war"

Eu voltei e refiz tudo novamente, mas continua apresentando o mesmo erro.

Aguardo resposta. Grato.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Olá, Ivo. Bom dia. Quando você sobe sua aplicação, aparece algum erro na console? Ou só esse erro quando você tenta testar a conexão?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Olá, João. Agradeço por retornar.

Esse erro eu copiei do console.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo. Mas o erro ocasiona no momento em que você sobe a aplicação ou só no momento de realizar o teste da conexão?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Ah, sim. Esse erro no momento de realizar o teste de conexão.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Legal. O driver do mysql foi instalado né? Você pode me informar as suas configurações do datasource?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Descupe-me, João. Seria no arquivo standalone-full.xml? Esse:

<datasources>
                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true" statistics-enabled="${wildfly.datasources.statistics-enabled:${wildfly.statistics-enabled:false}}">
                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>sa</password>
                    </security>
                </datasource>
                <datasource jndi-name="java:/AgendamentoEmailDS" pool-name="AgendamentoEmailDS" enabled="true">
                    <connection-url>jdbc:mysql://localhost:3306/agendamentoemaildb</connection-url>
                    <driver-class>com.mysql.cj.jdbc.Driver</driver-class>
                    <driver>mysql</driver>
                    <security>
                        <user-name>root</user-name>
                        <password>mysql</password>
                    </security>
                    <validation>
                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
                        <background-validation>true</background-validation>
                        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
                    </validation>
                </datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                    <driver name="mysql" module="com.mysql">
                        <xa-datasource-class>com.mysql.cj.jdbc.MysqlXADataSource</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo, boa noite. Com essas informações do datasource você consegue acessar o seu mysql local sem problemas?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Não entendi a pergunta. O nome do usuário e a senha estão corretos. Acesso com eles. Você se refere a isso?

solução!
por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Isso. A database que você configurou no datasource é a mesma que você tem no seu mysql? O usuário e senha também né?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Olá, João. A database, usuário e senha são esses mesmos que estão no datasource. Já conferi e estão digitados certo.

Eu marquei sem querer o teu comentário como solucionado.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Você pode me informar em qual diretório está salvo o seu persistence.xml?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Olá João. Não encontrei o persistence.xml. Em qual momento eu deveria tê-lo criado? Repassei os vídeos e não vi nada sobre o persistence.xml.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo, boa tarde. No vídeo "Criando Datasource", a partir dos 11 minutos, nós criamos o arquivo persistence.xml.

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Ok. Acabei de conferir. O problema é que o erro está antes da criação do persistence.xml

Esse meu erro aparece no Test Connection lá no minuto 10:19. Agora eu fiz o persistence.xml mas apresenta erro no console após iniciar o servidor.

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Aparece o mesmo erro ao iniciar o servidor?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Aparecem outros erros, inclusive o do Time Zone:

Caused by: java.sql.SQLException: The server time zone value 'Hora Padr?o Brasil Central' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'serverTimezone' configuration property) to use a more specifc time zone value if you want to utilize time zone support.
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:129)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:97)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:89)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:63)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:73)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:76)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:836)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:456)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:197)
    at org.jboss.ironjacamar.jdbcadapters@1.4.22.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)
por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts
Caused by: com.mysql.cj.exceptions.InvalidConnectionAttributeException: The server time zone value 'Hora Padr?o Brasil Central' is unrecognized or represents more than one time zone. You must configure either the server or JDBC driver (via the 'serverTimezone' configuration property) to use a more specifc time zone value if you want to utilize time zone support.
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:500)
    at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:481)
    at com.mysql@8.0.20//com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:61)
    at com.mysql@8.0.20//com.mysql.cj.exceptions.ExceptionFactory.createException(ExceptionFactory.java:85)
    at com.mysql@8.0.20//com.mysql.cj.util.TimeUtil.getCanonicalTimezone(TimeUtil.java:132)
    at com.mysql@8.0.20//com.mysql.cj.protocol.a.NativeProtocol.configureTimezone(NativeProtocol.java:2120)
    at com.mysql@8.0.20//com.mysql.cj.protocol.a.NativeProtocol.initServerSession(NativeProtocol.java:2143)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.initializePropsFromServer(ConnectionImpl.java:1310)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.connectOneTryOnly(ConnectionImpl.java:967)
    at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:826)
por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts
6:06:28,830 WARN  [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator] (ServerService Thread Pool -- 88) HHH000342: Could not obtain connection to query metadata : javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:/AgendamentoEmailDS
16:06:28,893 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 88) MSC000001: Failed to start service jboss.persistenceunit."agendamento-email-0.0.1-SNAPSHOT.war#AgendamentoEmailDS": org.jboss.msc.service.StartException in service jboss.persistenceunit."agendamento-email-0.0.1-SNAPSHOT.war#AgendamentoEmailDS": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.jboss.as.jpa@20.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa@20.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.12.1.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:658)
    at org.jboss.as.jpa@20.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:832)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:275)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:237)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate@5.3.17.Final//org.hibernate.id.factory.internal.DefaultIdentifierGeneratorFactory.injectServices(DefaultIdentifierGeneratorFactory.java:152)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.injectDependencies(AbstractServiceRegistryImpl.java:286)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:243)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:214)
    at org.hibernate@5.3.17.Final//org.hibernate.boot.internal.InFlightMetadataCollectorImpl.<init>(InFlightMetadataCollectorImpl.java:179)
    at org.hibernate@5.3.17.Final//org.hibernate.boot.model.process.spi.MetadataBuildingProcess.complete(MetadataBuildingProcess.java:119)
    at org.hibernate@5.3.17.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.metadata(EntityManagerFactoryBuilderImpl.java:1215)
    at org.hibernate@5.3.17.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:1246)
    at org.hibernate.jipijapa-hibernate5-3@20.0.1.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@20.0.1.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts
Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set
    at org.hibernate@5.3.17.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:100)
    at org.hibernate@5.3.17.Final//org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl.buildDialect(DialectFactoryImpl.java:54)
    at org.hibernate@5.3.17.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:137)
    at org.hibernate@5.3.17.Final//org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator.initiateService(JdbcEnvironmentInitiator.java:35)
    at org.hibernate@5.3.17.Final//org.hibernate.boot.registry.internal.StandardServiceRegistryImpl.initiateService(StandardServiceRegistryImpl.java:94)
    at org.hibernate@5.3.17.Final//org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:263)
    ... 21 more

16:06:28,907 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "agendamento-email-0.0.1-SNAPSHOT.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.persistenceunit.\"agendamento-email-0.0.1-SNAPSHOT.war#AgendamentoEmailDS\"" => "org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
    Caused by: org.hibernate.HibernateException: Access to DialectResolutionInfo cannot be null when 'hibernate.dialect' not set"}}
16:06:29,312 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 48) WFLYSRV0010: Deployed "agendamento-email-0.0.1-SNAPSHOT.war" (runtime-name : "agendamento-email-0.0.1-SNAPSHOT.war")
16:06:29,316 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186:   Services which failed to start:      service jboss.persistenceunit."agendamento-email-0.0.1-SNAPSHOT.war#AgendamentoEmailDS": org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.jdbc.env.spi.JdbcEnvironment]
WFLYCTL0448: 24 additional services are down due to their dependencies being missing or failed
16:06:29,505 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
16:06:29,510 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) started (with errors) in 80230ms - Started 513 of 758 services (29 services failed or missing dependencies, 392 services are lazy, passive or on-demand)
16:06:29,516 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
16:06:29,516 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

Só isso tudo. :-()

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo, você consegue me enviar o link do seu github com o seu projeto do jeito que está?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Olá, professor. Segue o link do meu Github com o projeto. https://github.com/IvoLeonardo/agendamento-email

por João Victor
| 348.1k xp | 540 posts
Instrutor Software Engineer

Ivo, boa noite. Importei a sua aplicação aqui e configurei o datasource novamente. Em connection / Connection URL eu inseri: jdbc:mysql://localhost:3306/agendamentoemaildb?useTimezone=true&serverTimezone=UTC

Fiz o teste de conexão e funcionou 100%. Pode testar dessa maneira?

por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Novo erro:

15:43:37,230 INFO  [org.jboss.modules] (main) JBoss Modules version 1.10.1.Final
15:43:38,417 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
15:43:38,435 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
15:43:38,642 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) starting
15:43:40,581 INFO  [org.wildfly.security] (ServerService Thread Pool -- 29) ELY00001: WildFly Elytron version 1.12.1.Final
15:43:41,320 INFO  [org.jboss.as.controller] (Controller Boot Thread) OPVDX002: falha ao formatar erro de validação: null
15:43:41,323 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
    at org.jboss.as.controller@12.0.3.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.ServerService.boot(ServerService.java:395)
    at org.jboss.as.controller@12.0.3.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
    at java.base/java.lang.Thread.run(Thread.java:832)
Caused by: javax.xml.stream.XMLStreamException: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'serverTimezone'
 at [row,col {unknown-source}]: [166,115]
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$DataSourceSubsystemParser.readElement(DataSourcesExtension.java:651)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$DataSourceSubsystemParser.readElement(DataSourcesExtension.java:205)
    at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
    at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.parsing.StandaloneXml_13.parseServerProfile(StandaloneXml_13.java:673)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.parsing.StandaloneXml_13.readServerElement(StandaloneXml_13.java:243)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.parsing.StandaloneXml_13.readElement(StandaloneXml_13.java:140)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:135)
    at org.jboss.as.server@12.0.3.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52)
    at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
    at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
    at org.jboss.as.controller@12.0.3.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'serverTimezone'
 at [row,col {unknown-source}]: [166,115]
    at org.codehaus.woodstox//com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:666)
    at org.codehaus.woodstox//com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2080)
    at org.codehaus.woodstox//com.ctc.wstx.sr.StreamScanner.fullyResolveEntity(StreamScanner.java:1538)
    at org.codehaus.woodstox//com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4777)
    at org.codehaus.woodstox//com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4223)
    at org.codehaus.woodstox//com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:702)
    at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLExtendedStreamReaderImpl.getElementText(XMLExtendedStreamReaderImpl.java:144)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.util.AbstractParser.rawElementText(AbstractParser.java:61)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSource_4_0(DsParser.java:1960)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DsParser.parseDataSources(DsParser.java:229)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DsParser.parse(DsParser.java:189)
    at org.jboss.as.connector@20.0.1.Final//org.jboss.as.connector.subsystems.datasources.DataSourcesExtension$DataSourceSubsystemParser.readElement(DataSourcesExtension.java:644)
    ... 14 more

15:43:41,325 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
15:43:41,344 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: WildFly Full 20.0.1.Final (WildFly Core 12.0.3.Final) stopped in 14ms
por Ivo Leonardo da Silva Costa
| 150.5k xp | 49 posts

Agradeço pela ajuda e paciência, João. Vou dar uma pausa nesse curso e depois recomeço. Minha paciência chegou no limite. Já reiniciei o projeto umas 3 vezes incluindo a instalação do Wildfly. Quando eu estiver mais tranquilo eu recomeço. Vou estudar outra coisa. Grato.

Quer mergulhar em tecnologia e aprendizagem?

Receba a newsletter que o nosso CEO escreve pessoalmente, com insights do mercado de trabalho, ciência e desenvolvimento de software