4 Replies Latest reply on May 11, 2017 11:50 AM by getgolfedkid

The applications fail to be deployed JBoss EAP 7

getgolfedkid May 9, 2017 12:09 PM

Hello,

I have the task to migrate an application that's running on tomEE. I have installed JBoss EAP 7 and can run the quickstarts provided by RedHat. However, I have (as expected) some problems to deploy my application using JBoss.

I am totally new to JBoss thus the solution may be obvious but I'm lost. I have tried many solution on stackoverflow or jboss.org but none worked so far.

Best Regards.

Here's the trace :

17:27:00,935 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1

17:27:01,206 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1

17:27:01,292 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre

17:27:03,383 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 11) WFLYDS0006: Le comportement de déploiement fiable n'est pas possible lorsque l'auto-déploiement de contenu explosé est activé (c'est-à-dire le déploiement sans utilisation des fichiers marqueurs ".dodeploy"). La configuration d'auto-déploiement de contenu explosé n'est pas recommandée dans toutes les situations quand on espère une certaine fiabilité. Configurer le paramètre auto-deploy-exploded de l'analyseur déploiement à false conseillé.

17:27:03,576 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-admin.war n'a pas abouti

17:27:03,802 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-wli.war n'a pas abouti

17:27:03,955 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)

17:27:03,974 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1

17:27:03,982 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1

17:27:04,035 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan

17:27:04,064 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Déploiement du pilote compatible JDCB class org.h2.Driver (version 1.3)

17:27:04,083 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Propriété d'identificateur de noeud définie à la valeur par défaut. Veillez à ce que cette valeur soit bien unique.

17:27:04,106 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: L'employé 'default' a configuré automatiquement les fils principaux 8 avec les fils de tâche 64 selon vos 4 processeurs disponibles

17:27:04,117 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité

17:27:04,132 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices

17:27:04,148 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1

17:27:04,151 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage

17:27:04,276 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)

17:27:04,298 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]

17:27:04,336 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Démarrage du service de nommage

17:27:04,337 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]

17:27:04,332 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2

17:27:04,347 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow

17:27:04,350 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow

17:27:04,728 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Création de gestionnaire de fichier pour le chemin 'C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0/welcome-content' avec les options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

17:27:04,735 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool utilise une taille d'instance max de 64 (par classe), qui est dérivée de la taille du pool de worker de threads.

17:27:04,736 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool utilise une taille d'instance max de 16 (par classe), qui est dérivée du nombre de CPU présents sur cet hôte.

17:27:05,258 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final-redhat-1

17:27:05,300 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: A démarré le serveur default-server.

17:27:05,345 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0018: L'hôte default-host démarre

17:27:05,445 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080

17:27:05,500 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")

17:27:05,505 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments

17:27:05,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")

17:27:05,506 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:27:05,509 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:27:05,987 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1

17:27:06,388 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)

17:27:06,507 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]

17:27:07,461 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war

17:27:07,481 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war

17:27:07,659 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.4.Final-redhat-1

17:27:08,889 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war

17:27:08,889 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war

17:27:09,062 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 2.3.3 (redhat)

17:27:09,185 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war

17:27:09,192 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war

17:27:15,734 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:15,736 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:15,741 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:15,769 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:27:16,055 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:27:16,059 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: java.lang.IllegalArgumentException: WFLYEJB0059: La méthode AroundTimeout, sur la classe org.apache.openejb.monitoring.StatsInterceptor, annotée par @javax.interceptor.AroundTimeout doit renvoyer un type Objet

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:27:16,246 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /jboss-helloworld

17:27:16,657 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»

17:27:17,813 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess

17:27:20,918 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:20,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:20,919 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:27:20,920 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,920 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-impl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,921 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,921 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry activation.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,939 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:27:20,950 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,978 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,979 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:27:20,979 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry serializer.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:27:21,055 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:27:21,062 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:27:21,065 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("deploy") a échoué - adresse : ([("deployment" => "xa-cms-admin.war")]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"

17:27:21,066 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("deploy") a échoué - adresse : ([("deployment" => "xa-cms-wli.war")]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"

17:27:21,098 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")

17:27:21,099 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")

17:27:21,101 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:27:21,102 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:27:21,149 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service

WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

17:27:21,353 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management

17:27:21,354 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990

17:27:21,354 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré (avec des erreurs) en 20829ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)

17:27:22,263 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 616ms

17:27:22,725 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1077ms

17:27:22,827 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:27:22,828 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:27:22,828 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service

WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE

service jboss.deployment.unit."xa-cms-admin.war".PARSE

17:28:30,166 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:28:30,167 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:28:33,858 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:33,859 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:33,860 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:33,874 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:28:33,985 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:28:34,003 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:28:36,389 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:36,390 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:36,391 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:36,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jaxb-impl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,392 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,393 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry activation.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,414 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:28:36,430 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,477 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,478 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,479 WARN [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class Path entry serializer.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:28:36,550 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:28:36,553 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:28:36,557 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("deploy") a échoué - adresse : ([("deployment" => "xa-cms-admin.war")]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"

17:28:36,558 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("deploy") a échoué - adresse : ([("deployment" => "xa-cms-wli.war")]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"

17:28:36,612 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:28:36,612 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:28:36,613 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service

WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

17:28:52,961 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 498ms

17:28:52,962 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:28:56,393 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:56,394 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:56,394 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:28:56,408 WARN [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:28:56,477 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:28:56,479 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:28:56,480 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"

17:28:56,529 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Le déploiement "xa-cms-admin.war" a été remplacé par le déploiement "xa-cms-admin.war"

17:28:56,530 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service

service jboss.deployment.unit."xa-cms-admin.war".PARSE

17:29:44,657 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 748ms

17:29:44,659 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:29:49,343 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:29:49,345 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:29:49,346 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:29:49,346 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,347 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-impl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,347 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,347 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry activation.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,365 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:29:49,377 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,402 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,403 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,403 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry serializer.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:29:49,445 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:29:49,447 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:29:49,448 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"

17:29:49,481 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Le déploiement "xa-cms-wli.war" a été remplacé par le déploiement "xa-cms-wli.war"

17:29:49,481 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service

service jboss.deployment.unit."xa-cms-wli.war".PARSE

17:37:10,960 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 521ms

17:37:10,961 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:37:14,328 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:14,329 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:14,330 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:14,345 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:37:14,422 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Échec de l'analyse du descripteur XML "/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/jboss-web.xml" sur [1,15]

at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:87)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '"' (code 34); expected '=' after 'version'

at [row,col,system-id]: [1,15,"N/A"]

at com.ctc.wstx.io.InputBootstrapper.reportUnexpectedChar(InputBootstrapper.java:507)

at com.ctc.wstx.io.InputBootstrapper.handleEq(InputBootstrapper.java:417)

at com.ctc.wstx.io.InputBootstrapper.readXmlVersion(InputBootstrapper.java:320)

at com.ctc.wstx.io.InputBootstrapper.readXmlDecl(InputBootstrapper.java:263)

at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:170)

at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:545)

at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:605)

at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:618)

at com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:324)

at __redirected.__XMLInputFactory.createXMLStreamReader(__XMLInputFactory.java:134)

at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:72)

... 6 more

17:37:14,424 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"

Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Échec de l'analyse du descripteur XML \"/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/jboss-web.xml\" sur [1,15]

Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '\"' (code 34); expected '=' after 'version'

at [row,col,system-id]: [1,15,\"N/A\"]"}}

17:37:14,464 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Le déploiement "xa-cms-admin.war" a été remplacé par le déploiement "xa-cms-admin.war"

17:37:14,465 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service

service jboss.deployment.unit."xa-cms-admin.war".PARSE

17:37:51,714 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 492ms

17:37:51,714 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")

17:37:54,515 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:54,516 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:54,516 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:37:54,528 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:37:54,590 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:37:54,591 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-admin.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-admin.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-admin.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:37:54,592 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"

17:37:54,632 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Le déploiement "xa-cms-admin.war" a été remplacé par le déploiement "xa-cms-admin.war"

17:37:54,632 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service

WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE

17:41:09,513 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 800ms

17:41:09,514 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")

17:41:14,534 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:41:14,535 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:41:14,535 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.

17:41:14,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,536 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,537 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,575 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.

17:41:14,587 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,614 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,614 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,614 WARN [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry serializer.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.

17:41:14,665 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Lecture de persistence.xml de xa-cms

17:41:14,668 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

at java.lang.Thread.run(Thread.java:745)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)

at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)

at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)

... 5 more

17:41:14,668 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"

17:41:14,704 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Le déploiement "xa-cms-wli.war" a été remplacé par le déploiement "xa-cms-wli.war"

17:41:14,704 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service

service jboss.deployment.unit."xa-cms-wli.war".PARSE

1. Re: The applications fail to be deployed JBoss EAP 7

jamezp May 9, 2017 4:33 PM (in response to getgolfedkid)

Are you including OpenEJB in your deployment by chance?

The error is basically saying the org.apache.openejb.monitoring.StatsInterceptor doesn't have the correct return type.

--
James R. Perkins
Actions
2. Re: The applications fail to be deployed JBoss EAP 7

getgolfedkid May 10, 2017 8:40 AM (in response to jamezp)

Thank you for your answer.

Concernant OpenEJB I have the following ejb-jar.xml file in my parent directory :

<ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" />

After searching in the provided RedHat quickstart applications I found the following beans.xml :

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://xmlns.jcp.org/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="
      http://xmlns.jcp.org/xml/ns/javaee
      http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd"
    bean-discovery-mode="all">
</beans>

However after adding them to the WEB-INF folder of my web applications and then rebuilding with Maven and launching the server again the same error appears to it didn't have any relevance.

I'm trying to learn how OpenEJB works but couldn't find on the internet which files I should had to my project to include it in the deployment. Moreover, no one in the company seems to be familiar with EJB either. I hope you will be able to help me again.

Regards
Actions
3. Re: The applications fail to be deployed JBoss EAP 7

jamezp May 10, 2017 11:13 AM (in response to getgolfedkid)

JBoss EAP doesn't use OpenEJB. If you're including OpenEJB in your deployment that could be an issue. JBoss EAP 7 is a Java EE 7 compliant container. You don't want to include any implementation of the EJB spec (like OpenEJB) in your deployment.

--
James R. Perkins
Actions
4. Re: The applications fail to be deployed JBoss EAP 7

getgolfedkid May 11, 2017 11:50 AM (in response to jamezp)

I have been able to deploy my apps through the management console. It was because of the name of the war files.

Thank you for your help.
Actions

Go to original post