Error al cargar un .war al Jboss EAP 7.1.0

lemaedu

Miembro Activo
Se incorporó
13 Noviembre 2018
Mensajes
1
Tengo una app web corriendo en Glasfish 4.1.0(Sin problemas), pero la misma app quiero correr en Jboss EAP 7.1.0 al cargar el .war me sale el siguiente error,

upload_2018-11-13_16-10-37.png


Me genera el siguiente log,
2018-11-13 15:55:11,932 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Iniciando la implementaci�n de Sisbweb-1.0-SNAPSHOT.war" (runtime-name: "Sisbweb-1.0-SNAPSHOT.war")
2018-11-13 15:55:27,231 WARN [org.jboss.modules] (MSC service thread 1-5) Failed to define class org.hibernate.jpa.internal.EntityManagerMessageLogger in Module "deployment.Sisbweb-1.0-SNAPSHOT.war" from Service Module Loader: java.lang.NoClassDefFoundError: Failed to link org/hibernate/jpa/internal/EntityManagerMessageLogger (Module "deployment.Sisbweb-1.0-SNAPSHOT.war" from Service Module Loader): org/hibernate/internal/CoreMessageLogger
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
at org.jboss.modules.Module.loadModuleClass(Module.java:713)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at org.hibernate.jpa.internal.HEMLogging.messageLogger(HEMLogging.java:45)
at org.hibernate.jpa.internal.HEMLogging.messageLogger(HEMLogging.java:41)
at org.hibernate.ejb.HibernatePersistence.<clinit>(HibernatePersistence.java:46)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.jboss.as.jpa.processor.PersistenceProviderHandler.deploy(PersistenceProviderHandler.java:74)
at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:49)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

2018-11-13 15:55:27,232 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."Sisbweb-1.0-SNAPSHOT.war".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Sisbweb-1.0-SNAPSHOT.war".FIRST_MODULE_USE: WFLYSRV0153: Error al procesar la fase FIRST_MODULE_USE de deployment "Sisbweb-1.0-SNAPSHOT.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NoClassDefFoundError: Failed to link org/hibernate/jpa/internal/EntityManagerMessageLogger (Module "deployment.Sisbweb-1.0-SNAPSHOT.war" from Service Module Loader): org/hibernate/internal/CoreMessageLogger
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
at org.jboss.modules.Module.loadModuleClass(Module.java:713)
at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:412)
at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:400)
at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
at org.hibernate.jpa.internal.HEMLogging.messageLogger(HEMLogging.java:45)
at org.hibernate.jpa.internal.HEMLogging.messageLogger(HEMLogging.java:41)
at org.hibernate.ejb.HibernatePersistence.<clinit>(HibernatePersistence.java:46)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at org.jboss.as.jpa.processor.PersistenceProviderHandler.deploy(PersistenceProviderHandler.java:74)
at org.jboss.as.jpa.processor.PersistenceBeginInstallProcessor.deploy(PersistenceBeginInstallProcessor.java:49)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
... 5 more

2018-11-13 15:55:27,233 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 3) WFLYCTL0013: Operaci�n ("add") fall� - direcci�n: ([("deployment" => "Sisbweb-1.0-SNAPSHOT.war")]) - descripci�n de la falla: {"WFLYCTL0080: Servicios fallidos" => {"jboss.deployment.unit.\"Sisbweb-1.0-SNAPSHOT.war\".FIRST_MODULE_USE" => "WFLYSRV0153: Error al procesar la fase FIRST_MODULE_USE de deployment \"Sisbweb-1.0-SNAPSHOT.war\"
Caused by: java.lang.NoClassDefFoundError: Failed to link org/hibernate/jpa/internal/EntityManagerMessageLogger (Module \"deployment.Sisbweb-1.0-SNAPSHOT.war\" from Service Module Loader): org/hibernate/internal/CoreMessageLogger"}}
2018-11-13 15:55:27,233 ERROR [org.jboss.as.server] (External Management Request Threads -- 3) WFLYSRV0021: La implementaci�n de "Sisbweb-1.0-SNAPSHOT.war" se deshizo con el siguiente mensaje de fallo:
{"WFLYCTL0080: Servicios fallidos" => {"jboss.deployment.unit.\"Sisbweb-1.0-SNAPSHOT.war\".FIRST_MODULE_USE" => "WFLYSRV0153: Error al procesar la fase FIRST_MODULE_USE de deployment \"Sisbweb-1.0-SNAPSHOT.war\"
Caused by: java.lang.NoClassDefFoundError: Failed to link org/hibernate/jpa/internal/EntityManagerMessageLogger (Module \"deployment.Sisbweb-1.0-SNAPSHOT.war\" from Service Module Loader): org/hibernate/internal/CoreMessageLogger"}}
2018-11-13 15:55:28,689 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Se detuvo la implementaci�nSisbweb-1.0-SNAPSHOT.war (runtime-name: Sisbweb-1.0-SNAPSHOT.war) en 1455ms
2018-11-13 15:56:28,321 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 63) WFLYDR0009: El contenido C:\jboss EAP\standalone\data\content\22\23017eea2d82a7d60aafff5dde7e055b4cc2ee es obsoleto y se borrar�
2018-11-13 15:56:28,331 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 63) WFLYDR0002: Contenido borrado del sitio C:\jboss EAP\standalone\data\content\22\23017eea2d82a7d60aafff5dde7e055b4cc2ee\content


Alguien que me ayude a solucionar el problema, gracias
 

Archivo adjunto

  • upload_2018-11-13_16-9-59.png
    upload_2018-11-13_16-9-59.png
    216,8 KB · Visitas: 158

Cosme

Gold Member
Se incorporó
27 Febrero 2005
Mensajes
8.281
Estan instaladas las dependencias dem modulo? El error es class not def, que suele pasar cuando estan mal declaradas las dependencias y no te avisa en el checkeo pre-deploy
 
Upvote 0
Subir