Erro ao subir minha aplicação - Wildfly

6 respostas
S
Boa tarde...

 Estou usando WildFly-8.2.1.Final startando ele por dentro do Eclipse. Mas não estou conseguindo subir minha aplicação. O log de erro que ele apresenta é esse : 

15:11:40,978 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
15:11:43,109 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
15:11:43,280 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (MSC service thread 1-8) JBAS015899: WildFly 8.2.1.Final Tweek starting

15:12:02,061 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

15:12:02,142 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.3.0.Final

15:12:02,152 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.0.Final

15:12:02,192 INFO  [org.jboss.as.naming] (ServerService Thread Pool  40) JBAS011800: Activating Naming Subsystem

15:12:02,192 WARN  [org.jboss.as.txn] (ServerService Thread Pool  46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

15:12:02,192 INFO  [org.jboss.as.security] (ServerService Thread Pool  45) JBAS013171: Activating Security Subsystem

15:12:02,192 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool  32) JBAS010280: Activating Infinispan subsystem.

15:12:02,232 INFO  [org.jboss.as.jsf] (ServerService Thread Pool  38) JBAS012615: Activated the following JSF Implementations: [main]

15:12:02,332 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.21.Final

15:12:02,393 INFO  [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service

15:12:02,383 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) JBAS015400: Bound mail session [java:jboss/mail/Default]

15:12:02,393 INFO  [org.jboss.as.webservices] (ServerService Thread Pool  48) JBAS015537: Activating WebServices Extension

15:12:02,433 INFO  [<a href="http://org.wildfly.extension.io">org.wildfly.extension.io</a>] (ServerService Thread Pool  31) WFLYIO001: Worker default has auto-configured to 8 core threads with 64 task threads based on your 4 available processors

15:12:02,627 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)

15:12:02,710 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.1.8.Final starting

15:12:02,710 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool  47) JBAS017502: Undertow 1.1.8.Final starting

15:12:03,170 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool  27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

15:12:03,271 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2

15:12:03,433 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.7.Final

15:12:03,886 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool  47) JBAS017527: Creating file handler for path C:\Users\pc\Desktop\wildfly-8.2.1.Final/welcome-content

15:12:04,162 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.

15:12:04,503 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017531: Host default-host starting

15:12:04,524 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017519: Undertow HTTP listener default listening on localhost/127.0.0.1:8080

15:12:05,456 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

15:12:05,668 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\pc\Desktop\wildfly-8.2.1.Final\standalone\deployments

15:12:05,819 INFO  [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final

15:12:07,208 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) JBAS015961: Http management interface listening on <a href="http://127.0.0.1:9990/management">http://127.0.0.1:9990/management</a>

15:12:07,208 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) JBAS015951: Admin console listening on <a href="http://127.0.0.1:9990">http://127.0.0.1:9990</a>

15:12:07,208 INFO  [<a href="http://org.jboss.as">org.jboss.as</a>] (Controller Boot Thread) JBAS015874: WildFly 8.2.1.Final Tweek started in 26662ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)

15:12:40,736 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found Sisprot.war in deployment directory. To trigger deployment create a file called Sisprot.war.dodeploy

15:12:40,781 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of Sisprot.war (runtime-name: Sisprot.war)

15:13:21,890 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.Sisprot.war.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.Sisprot.war.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment "Sisprot.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]

at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.8.0_181]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.8.0_181]

at java.lang.Thread.run(Unknown Source) [rt.jar:1.8.0_181]

Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class br.com.sms.sisprot.controlador.Filtros with ClassLoader ModuleClassLoader for Module deployment.Sisprot.war:main from Service Module Loader

at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:72) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:58)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:107)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:92)

at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:77)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

 5 more

Caused by: java.lang.NoClassDefFoundError: IOException

at java.lang.Class.getDeclaredMethods0(Native Method) [rt.jar:1.8.0_181]

at java.lang.Class.privateGetDeclaredMethods(Unknown Source) [rt.jar:1.8.0_181]

at java.lang.Class.getDeclaredMethods(Unknown Source) [rt.jar:1.8.0_181]

at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.(ClassReflectionIndex.java:65) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:68) [wildfly-server-8.2.1.Final.jar:8.2.1.Final]

 10 more

Caused by: java.lang.ClassNotFoundException: IOException from [Module “deployment.Sisprot.war:main” from Service Module Loader]

at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:213) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:459) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:408) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:389) [jboss-modules.jar:1.3.3.Final]

at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:134) [jboss-modules.jar:1.3.3.Final]

 15 more
15:13:21,900 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) JBAS014613: Operation (deploy) failed - address: ([(deployment => Sisprot.war)]) - failure description: {JBAS014671: Failed services => {jboss.deployment.unit.Sisprot.war.POST_MODULE => "org.jboss.msc.service.StartException in service jboss.deployment.unit.“Sisprot.war”.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment “Sisprot.war"

Caused by: java.lang.RuntimeException: JBAS018757: Error getting reflective information for class br.com.sms.sisprot.controlador.Filtros with ClassLoader ModuleClassLoader for Module deployment.Sisprot.war:main from Service Module Loader

Caused by: java.lang.NoClassDefFoundError: IOException

Caused by: java.lang.ClassNotFoundException: IOException from [Module deployment.Sisprot.war:main from Service Module Loader]}}

15:13:22,091 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018559: Deployed Sisprot.war (runtime-name : Sisprot.war)

15:13:22,091 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

JBAS014777:   Services which failed to start:      service jboss.deployment.unit.Sisprot.war.POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit.Sisprot.war.POST_MODULE: JBAS018733: Failed to process phase POST_MODULE of deployment Sisprot.war

O que está dando errado ?

6 Respostas

darlan_machado

Esta é uma classe que você criou?

S

Sim…

darlan_machado

Pode ser o uso de diferentes versões para compilar e para rodar o teu sistema.
Vi aqui

S

Onde posso alterar essa configuração ?

darlan_machado

Primeiro, certifique-se de que você tem mais de uma versão do jdk instalado.
Depois, verifique qual está configurada para o wildfly (isso você vê nas propriedades de configuração do mesmo, no eclipse)
Por último, verifique a versão dos projetos no eclipse e altere, caso necessário.

S

Consegui resolver…grato pela atenção, colega…

Criado 26 de julho de 2018
Ultima resposta 30 de jul. de 2018
Respostas 6
Participantes 2