Boa Tarde a todos,
estou tentando fazer login no sistema CITSMART, com usuário "consultor" e senha "consultor" contudo não houve sucesso. Ao analisar o log do servidor encontrei alguns "WARNINGS" suspeitos, que podem refletir na conexão com o banco de dados.
Abaixo segue as partes do log que eu citei acima:
17:43:22,596 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "2-cit-portal-web-2.1.0.war"
17:43:22,596 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "3-cit-tabelas-corp-web-2.0.0.war"
17:43:22,598 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "1-cas-db-1.0.0-RELEASE.war"
17:43:27,715 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry jaxb-api.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/jaxb-impl-2.2.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,716 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry activation.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/jaxb-impl-2.2.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry jsr173_1.0_api.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/jaxb-impl-2.2.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,717 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry jaxb1-impl.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/jaxb-impl-2.2.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,720 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry xml-apis.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,724 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry xercesImpl.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,724 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry xml-apis.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:43:27,725 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) Class Path entry serializer.jar in "/content/1-cas-db-1.0.0-RELEASE.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
17:43:28,621 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
17:43:32,211 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-2) HHH000204: Processing PersistenceUnitInfo [
name: CasPersistence
...]
17:43:33,326
WARN
[org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator]
(MSC service thread 1-2) HHH000181: No appropriate connection provider
encountered, assuming application will be supplying connections
7:43:45,160
WARN [org.jboss.as.ee] (MSC service thread 1-3) JBAS011006: Not
installing optional component
org.springframework.web.context.request.async.StandardServletAsyncWebRequest
due to exception:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
JBAS011054: Could not find default constructor for class
org.springframework.web.context.request.async.StandardServletAsyncWebRequest
at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113)
[jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_80]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_80]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80]
17:43:45,467 INFO [org.springframework.web.context.ContextLoader] (MSC service thread 1-6) Root WebApplicationContext: initialization started
17:43:45,724 WARN [org.jboss.as.ee] (MSC service thread 1-7) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest
at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_80]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_80]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80]
17:43:45,750 INFO [br.com.centralit.framework.util.CustomApplicationContextInitializer] (MSC service thread 1-6) ========== Caminho do properties:'classpath:cit-app.properties' carregado com a ordem: 'FIRST' ==========
Alguém que já passou por essa dificuldade poderia me ajudar.
Att,
--
Diego Patrick da Silva Santos
Analista de Sistemas
Coordenação Geral de Modernização em Informática - CGMI
Coordenação de Desenvolvimento de Sistemas e Administração de
Dados
Ministério das Cidades
Tel: 2108-1342
Diego Patrick da Silva Santos
13 de Julho de 2016 às 20:49Boa Tarde a todos,
Pablo Bandeira