API tools faq
paste
Guest User

antoine_serverlog_part2

a guest
May 12th, 2017
303
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 466.02 KB | None | 0 0
raw download clone embed print report
  1. 2017-05-11 16:05:44,546 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2. 2017-05-11 16:05:44,866 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  3. 2017-05-11 16:05:44,952 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  4. 2017-05-11 16:05:44,953 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  5. awt.toolkit = sun.awt.windows.WToolkit
  6. file.encoding = Cp1252
  7. file.encoding.pkg = sun.io
  8. file.separator = \
  9. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  10. java.awt.headless = true
  11. java.awt.printerjob = sun.awt.windows.WPrinterJob
  12. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  13. java.class.version = 52.0
  14. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  15. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  16. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  17. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  18. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  19. java.net.preferIPv4Stack = true
  20. java.runtime.name = Java(TM) SE Runtime Environment
  21. java.runtime.version = 1.8.0_121-b13
  22. java.specification.name = Java Platform API Specification
  23. java.specification.vendor = Oracle Corporation
  24. java.specification.version = 1.8
  25. java.util.logging.manager = org.jboss.logmanager.LogManager
  26. java.vendor = Oracle Corporation
  27. java.vendor.url = http://java.oracle.com/
  28. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  29. java.version = 1.8.0_121
  30. java.vm.info = mixed mode
  31. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  32. java.vm.specification.name = Java Virtual Machine Specification
  33. java.vm.specification.vendor = Oracle Corporation
  34. java.vm.specification.version = 1.8
  35. java.vm.vendor = Oracle Corporation
  36. java.vm.version = 25.121-b13
  37. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  38. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  39. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  40. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  41. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  42. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  43. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  44. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  45. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  46. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  47. jboss.bind.address = localhost
  48. jboss.bind.address.management = localhost
  49. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  50. jboss.host.name = l82564
  51. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  52. jboss.modules.system.pkgs = org.jboss.byteman
  53. jboss.node.name = l82564
  54. jboss.qualified.host.name = l82564
  55. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  56. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  57. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  58. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  59. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  60. jboss.server.name = l82564
  61. jboss.server.persist.config = true
  62. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  63. line.separator =
  64.  
  65. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  66. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  67. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  68. org.jboss.logmanager.nocolor = true
  69. org.jboss.resolver.warning = true
  70. org.xml.sax.driver = __redirected.__XMLReaderFactory
  71. os.arch = amd64
  72. os.name = Windows 7
  73. os.version = 6.1
  74. path.separator = ;
  75. program.name = JBossTools: Red Hat JBoss EAP 7.x
  76. sun.arch.data.model = 64
  77. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  78. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  79. sun.cpu.endian = little
  80. sun.cpu.isalist = amd64
  81. sun.desktop = windows
  82. sun.io.unicode.encoding = UnicodeLittle
  83. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  84. sun.java.launcher = SUN_STANDARD
  85. sun.jnu.encoding = Cp1252
  86. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  87. sun.os.patch.level = Service Pack 1
  88. sun.rmi.dgc.client.gcInterval = 3600000
  89. sun.rmi.dgc.server.gcInterval = 3600000
  90. user.country = FR
  91. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  92. user.home = C:\Utilisateurs\A665340
  93. user.language = fr
  94. user.name = A665340
  95. user.script =
  96. user.timezone = Europe/Paris
  97. user.variant =
  98. 2017-05-11 16:05:44,954 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  99. 2017-05-11 16:05:46,844 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 24) 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é.
  100. 2017-05-11 16:05:46,948 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  101. 2017-05-11 16:05:46,969 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
  102. 2017-05-11 16:05:46,978 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  103. 2017-05-11 16:05:47,047 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  104. 2017-05-11 16:05:47,059 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.
  105. 2017-05-11 16:05:47,062 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  106. 2017-05-11 16:05:47,083 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
  107. 2017-05-11 16:05:47,085 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  108. 2017-05-11 16:05:47,102 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  109. 2017-05-11 16:05:47,112 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  110. 2017-05-11 16:05:47,296 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  111. 2017-05-11 16:05:47,296 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)
  112. 2017-05-11 16:05:47,316 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  113. 2017-05-11 16:05:47,331 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  114. 2017-05-11 16:05:47,340 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Démarrage du service de nommage
  115. 2017-05-11 16:05:47,384 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)
  116. 2017-05-11 16:05:47,385 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  117. 2017-05-11 16:05:47,428 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  118. 2017-05-11 16:05:47,618 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: '[]']
  119. 2017-05-11 16:05:47,881 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  120. 2017-05-11 16:05:47,884 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
  121. 2017-05-11 16:05:48,117 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final-redhat-1
  122. 2017-05-11 16:05:48,181 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: A démarré le serveur default-server.
  123. 2017-05-11 16:05:48,182 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: L'hôte default-host démarre
  124. 2017-05-11 16:05:48,312 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  125. 2017-05-11 16:05:48,543 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  126. 2017-05-11 16:05:48,547 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  127. 2017-05-11 16:05:48,560 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  128. 2017-05-11 16:05:49,167 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  129. 2017-05-11 16:05:49,304 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  130. 2017-05-11 16:05:49,494 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  131. 2017-05-11 16:05:50,358 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  132. 2017-05-11 16:05:50,360 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  133. 2017-05-11 16:05:50,473 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  134. 2017-05-11 16:05:50,753 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  135. 2017-05-11 16:05:50,753 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  136. 2017-05-11 16:05:50,783 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.3.3 (redhat)
  137. 2017-05-11 16:05:50,817 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  138. 2017-05-11 16:05:50,817 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  139. 2017-05-11 16:05:51,937 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 61) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  140. 2017-05-11 16:05:51,960 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  141. 2017-05-11 16:05:52,476 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  142. 2017-05-11 16:05:52,507 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  143. 2017-05-11 16:05:52,507 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  144. 2017-05-11 16:05:52,698 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  145. 2017-05-11 16:05:52,699 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  146. 2017-05-11 16:05:52,699 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 8675ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  147. 2017-05-11 16:06:24,317 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0236: Suspending server with no timeout.
  148. 2017-05-11 16:06:24,332 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  149. 2017-05-11 16:06:24,459 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  150. 2017-05-11 16:06:24,470 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  151. 2017-05-11 16:06:24,496 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  152. 2017-05-11 16:06:24,503 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: L'hôte default-host s'arrête
  153. 2017-05-11 16:06:24,528 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  154. 2017-05-11 16:06:24,620 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  155. 2017-05-11 16:06:24,632 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  156. 2017-05-11 16:06:24,641 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  157. 2017-05-11 16:06:24,683 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  158. 2017-05-11 16:06:24,685 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  159. 2017-05-11 16:06:24,712 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 357ms
  160. 2017-05-11 16:06:24,736 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 385ms
  161. 2017-05-11 16:06:24,746 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 384ms
  162. 2017-05-11 16:06:59,058 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  163. 2017-05-11 16:06:59,491 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  164. 2017-05-11 16:06:59,591 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  165. 2017-05-11 16:06:59,594 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  166. awt.toolkit = sun.awt.windows.WToolkit
  167. file.encoding = Cp1252
  168. file.encoding.pkg = sun.io
  169. file.separator = \
  170. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  171. java.awt.headless = true
  172. java.awt.printerjob = sun.awt.windows.WPrinterJob
  173. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  174. java.class.version = 52.0
  175. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  176. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  177. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  178. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  179. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  180. java.net.preferIPv4Stack = true
  181. java.runtime.name = Java(TM) SE Runtime Environment
  182. java.runtime.version = 1.8.0_121-b13
  183. java.specification.name = Java Platform API Specification
  184. java.specification.vendor = Oracle Corporation
  185. java.specification.version = 1.8
  186. java.util.logging.manager = org.jboss.logmanager.LogManager
  187. java.vendor = Oracle Corporation
  188. java.vendor.url = http://java.oracle.com/
  189. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  190. java.version = 1.8.0_121
  191. java.vm.info = mixed mode
  192. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  193. java.vm.specification.name = Java Virtual Machine Specification
  194. java.vm.specification.vendor = Oracle Corporation
  195. java.vm.specification.version = 1.8
  196. java.vm.vendor = Oracle Corporation
  197. java.vm.version = 25.121-b13
  198. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  199. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  200. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  201. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  202. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  203. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  204. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  205. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  206. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  207. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  208. jboss.bind.address = localhost
  209. jboss.bind.address.management = localhost
  210. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  211. jboss.host.name = l82564
  212. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  213. jboss.modules.system.pkgs = org.jboss.byteman
  214. jboss.node.name = l82564
  215. jboss.qualified.host.name = l82564
  216. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  217. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  218. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  219. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  220. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  221. jboss.server.name = l82564
  222. jboss.server.persist.config = true
  223. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  224. line.separator =
  225.  
  226. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  227. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  228. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  229. org.jboss.logmanager.nocolor = true
  230. org.jboss.resolver.warning = true
  231. org.xml.sax.driver = __redirected.__XMLReaderFactory
  232. os.arch = amd64
  233. os.name = Windows 7
  234. os.version = 6.1
  235. path.separator = ;
  236. program.name = JBossTools: Red Hat JBoss EAP 7.x
  237. sun.arch.data.model = 64
  238. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  239. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  240. sun.cpu.endian = little
  241. sun.cpu.isalist = amd64
  242. sun.desktop = windows
  243. sun.io.unicode.encoding = UnicodeLittle
  244. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  245. sun.java.launcher = SUN_STANDARD
  246. sun.jnu.encoding = Cp1252
  247. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  248. sun.os.patch.level = Service Pack 1
  249. sun.rmi.dgc.client.gcInterval = 3600000
  250. sun.rmi.dgc.server.gcInterval = 3600000
  251. user.country = FR
  252. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  253. user.home = C:\Utilisateurs\A665340
  254. user.language = fr
  255. user.name = A665340
  256. user.script =
  257. user.timezone = Europe/Paris
  258. user.variant =
  259. 2017-05-11 16:06:59,595 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  260. 2017-05-11 16:07:01,730 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 9) 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é.
  261. 2017-05-11 16:07:01,969 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "jboss-helloworld.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"jboss-helloworld.war\")] en double"
  262. 2017-05-11 16:07:01,973 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  263. 2017-05-11 16:07:01,976 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  264. 2017-05-11 16:07:02,011 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 26ms
  265. 2017-05-11 16:07:17,397 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  266. 2017-05-11 16:07:17,754 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  267. 2017-05-11 16:07:17,838 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  268. 2017-05-11 16:07:17,841 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  269. awt.toolkit = sun.awt.windows.WToolkit
  270. file.encoding = Cp1252
  271. file.encoding.pkg = sun.io
  272. file.separator = \
  273. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  274. java.awt.headless = true
  275. java.awt.printerjob = sun.awt.windows.WPrinterJob
  276. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  277. java.class.version = 52.0
  278. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  279. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  280. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  281. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  282. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  283. java.net.preferIPv4Stack = true
  284. java.runtime.name = Java(TM) SE Runtime Environment
  285. java.runtime.version = 1.8.0_121-b13
  286. java.specification.name = Java Platform API Specification
  287. java.specification.vendor = Oracle Corporation
  288. java.specification.version = 1.8
  289. java.util.logging.manager = org.jboss.logmanager.LogManager
  290. java.vendor = Oracle Corporation
  291. java.vendor.url = http://java.oracle.com/
  292. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  293. java.version = 1.8.0_121
  294. java.vm.info = mixed mode
  295. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  296. java.vm.specification.name = Java Virtual Machine Specification
  297. java.vm.specification.vendor = Oracle Corporation
  298. java.vm.specification.version = 1.8
  299. java.vm.vendor = Oracle Corporation
  300. java.vm.version = 25.121-b13
  301. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  302. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  303. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  304. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  305. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  306. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  307. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  308. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  309. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  310. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  311. jboss.bind.address = localhost
  312. jboss.bind.address.management = localhost
  313. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  314. jboss.host.name = l82564
  315. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  316. jboss.modules.system.pkgs = org.jboss.byteman
  317. jboss.node.name = l82564
  318. jboss.qualified.host.name = l82564
  319. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  320. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  321. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  322. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  323. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  324. jboss.server.name = l82564
  325. jboss.server.persist.config = true
  326. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  327. line.separator =
  328.  
  329. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  330. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  331. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  332. org.jboss.logmanager.nocolor = true
  333. org.jboss.resolver.warning = true
  334. org.xml.sax.driver = __redirected.__XMLReaderFactory
  335. os.arch = amd64
  336. os.name = Windows 7
  337. os.version = 6.1
  338. path.separator = ;
  339. program.name = JBossTools: Red Hat JBoss EAP 7.x
  340. sun.arch.data.model = 64
  341. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  342. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  343. sun.cpu.endian = little
  344. sun.cpu.isalist = amd64
  345. sun.desktop = windows
  346. sun.io.unicode.encoding = UnicodeLittle
  347. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  348. sun.java.launcher = SUN_STANDARD
  349. sun.jnu.encoding = Cp1252
  350. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  351. sun.os.patch.level = Service Pack 1
  352. sun.rmi.dgc.client.gcInterval = 3600000
  353. sun.rmi.dgc.server.gcInterval = 3600000
  354. user.country = FR
  355. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  356. user.home = C:\Utilisateurs\A665340
  357. user.language = fr
  358. user.name = A665340
  359. user.script =
  360. user.timezone = Europe/Paris
  361. user.variant =
  362. 2017-05-11 16:07:17,843 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  363. 2017-05-11 16:07:20,007 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 13) 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é.
  364. 2017-05-11 16:07:20,049 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  365. 2017-05-11 16:07:20,074 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  366. 2017-05-11 16:07:20,085 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  367. 2017-05-11 16:07:20,180 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.
  368. 2017-05-11 16:07:20,188 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  369. 2017-05-11 16:07:20,190 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  370. 2017-05-11 16:07:20,217 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  371. 2017-05-11 16:07:20,231 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  372. 2017-05-11 16:07:20,256 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)
  373. 2017-05-11 16:07:20,271 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  374. 2017-05-11 16:07:20,299 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
  375. 2017-05-11 16:07:20,449 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Démarrage du service de nommage
  376. 2017-05-11 16:07:20,451 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  377. 2017-05-11 16:07:20,452 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  378. 2017-05-11 16:07:20,454 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  379. 2017-05-11 16:07:20,455 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  380. 2017-05-11 16:07:20,483 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  381. 2017-05-11 16:07:20,497 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  382. 2017-05-11 16:07:20,630 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: '[]']
  383. 2017-05-11 16:07:20,897 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  384. 2017-05-11 16:07:20,898 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  385. 2017-05-11 16:07:21,262 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: A démarré le serveur default-server.
  386. 2017-05-11 16:07:21,275 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: L'hôte default-host démarre
  387. 2017-05-11 16:07:21,332 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.18.Final-redhat-1
  388. 2017-05-11 16:07:21,371 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  389. 2017-05-11 16:07:21,541 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  390. 2017-05-11 16:07:21,565 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")
  391. 2017-05-11 16:07:21,568 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  392. 2017-05-11 16:07:21,822 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  393. 2017-05-11 16:07:21,826 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  394. 2017-05-11 16:07:22,273 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  395. 2017-05-11 16:07:23,391 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  396. 2017-05-11 16:07:23,392 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  397. 2017-05-11 16:07:23,495 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  398. 2017-05-11 16:07:23,790 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  399. 2017-05-11 16:07:23,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  400. 2017-05-11 16:07:23,834 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.3 (redhat)
  401. 2017-05-11 16:07:23,886 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  402. 2017-05-11 16:07:23,886 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  403. 2017-05-11 16:07:25,180 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 62) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  404. 2017-05-11 16:07:25,197 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  405. 2017-05-11 16:07:25,741 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  406. 2017-05-11 16:07:25,768 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  407. 2017-05-11 16:07:25,769 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  408. 2017-05-11 16:07:25,939 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  409. 2017-05-11 16:07:25,940 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  410. 2017-05-11 16:07:25,940 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 9078ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  411. 2017-05-11 16:08:51,957 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")
  412. 2017-05-11 16:08:51,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  413. 2017-05-11 16:08:52,377 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Contexte web enregistré : /xa-cms-admin
  414. 2017-05-11 16:08:52,581 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0021: Contexte web enregistré : /xa-cms-wli
  415. 2017-05-11 16:08:52,721 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  416. 2017-05-11 16:08:52,721 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  417. 2017-05-11 16:17:18,254 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 30) WFLYDR0009: Le contenu C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\29\ccc50ca4944c117563c9358cc23c5cf0d1be66 est obsolète et va être supprimé
  418. 2017-05-11 16:17:18,263 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 30) WFLYDR0002: Contenu supprimé de la location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\29\ccc50ca4944c117563c9358cc23c5cf0d1be66\content
  419. 2017-05-11 16:17:18,263 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 30) WFLYDR0009: Le contenu C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\98\86f494a4065f662063c12ce1919ec08975be6f est obsolète et va être supprimé
  420. 2017-05-11 16:17:18,271 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 30) WFLYDR0002: Contenu supprimé de la location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\98\86f494a4065f662063c12ce1919ec08975be6f\content
  421. 2017-05-11 16:32:14,406 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0022: Contexte web désenregistré : /xa-cms-wli
  422. 2017-05-11 16:32:14,517 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 184ms
  423. 2017-05-11 16:32:14,690 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  424. 2017-05-11 16:32:19,809 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  425. 2017-05-11 16:32:22,032 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.
  426. 2017-05-11 16:32:22,033 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.
  427. 2017-05-11 16:32:22,072 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.
  428. 2017-05-11 16:32:23,308 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".POST_MODULE: WFLYSRV0153: N'a pas pu traiter la phase POST_MODULE de deployment "xa-cms-wli.war"
  429. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  430. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  431. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  432. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  433. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  434. at java.lang.Thread.run(Thread.java:745)
  435. Caused by: java.lang.RuntimeException: WFLYSRV0177: Erreur d'obtention d'informations réflectives pour class org.apache.tapestry5.TapestryFilter pour le ClassLoader (Chargeur de classe) ModuleClassLoader for Module "deployment.xa-cms-wli.war:main" from Service Module Loader
  436. at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:70)
  437. at org.jboss.as.ee.metadata.MethodAnnotationAggregator.runtimeAnnotationInformation(MethodAnnotationAggregator.java:57)
  438. at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.handleAnnotations(InterceptorAnnotationProcessor.java:106)
  439. at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:91)
  440. at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:76)
  441. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  442. ... 5 more
  443. Caused by: java.lang.NoClassDefFoundError: org/apache/tapestry5/ioc/services/SymbolProvider
  444. at java.lang.Class.getDeclaredFields0(Native Method)
  445. at java.lang.Class.privateGetDeclaredFields(Class.java:2583)
  446. at java.lang.Class.getDeclaredFields(Class.java:1916)
  447. at org.jboss.as.server.deployment.reflect.ClassReflectionIndex.<init>(ClassReflectionIndex.java:72)
  448. at org.jboss.as.server.deployment.reflect.DeploymentReflectionIndex.getClassIndex(DeploymentReflectionIndex.java:66)
  449. ... 10 more
  450. Caused by: java.lang.ClassNotFoundException: org.apache.tapestry5.ioc.services.SymbolProvider from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader]
  451. at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:198)
  452. at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
  453. at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
  454. at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
  455. ... 15 more
  456.  
  457. 2017-05-11 16:32:23,372 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\".POST_MODULE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".POST_MODULE: WFLYSRV0153: N'a pas pu traiter la phase POST_MODULE de deployment \"xa-cms-wli.war\"
  458. Caused by: java.lang.RuntimeException: WFLYSRV0177: Erreur d'obtention d'informations réflectives pour class org.apache.tapestry5.TapestryFilter pour le ClassLoader (Chargeur de classe) ModuleClassLoader for Module \"deployment.xa-cms-wli.war:main\" from Service Module Loader
  459. Caused by: java.lang.NoClassDefFoundError: org/apache/tapestry5/ioc/services/SymbolProvider
  460. Caused by: java.lang.ClassNotFoundException: org.apache.tapestry5.ioc.services.SymbolProvider from [Module \"deployment.xa-cms-wli.war:main\" from Service Module Loader]"}}
  461. 2017-05-11 16:32:23,539 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  462. 2017-05-11 16:32:23,540 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  463. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".POST_MODULE: WFLYSRV0153: N'a pas pu traiter la phase POST_MODULE de deployment "xa-cms-wli.war"
  464.  
  465. 2017-05-11 16:32:29,305 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 401ms
  466. 2017-05-11 16:32:29,310 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  467. 2017-05-11 16:32:37,536 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-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  468. 2017-05-11 16:32:37,537 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  469. 2017-05-11 16:32:37,538 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  470. 2017-05-11 16:32:38,603 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld xa-cms-wli.war
  471. 2017-05-11 16:32:38,931 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0004: Déploiement du pilote compatible JDCB class org.hsqldb.jdbc.JDBCDriver (version 2.3)
  472. 2017-05-11 16:32:38,936 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0005: Déploiement du pilote non compatible JDCB class com.mysql.jdbc.Driver (version 5.1)
  473. 2017-05-11 16:32:38,937 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : xa-cms-wli.war
  474. 2017-05-11 16:32:38,943 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  475. 2017-05-11 16:32:38,946 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement xa-cms-wli.war
  476. 2017-05-11 16:32:38,944 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  477. 2017-05-11 16:32:40,830 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 75) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «»
  478. 2017-05-11 16:32:47,804 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0021: Contexte web enregistré : /
  479. 2017-05-11 16:32:47,867 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"
  480. 2017-05-11 16:32:47,868 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  481. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".POST_MODULE
  482.  
  483. 2017-05-11 16:32:53,595 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 75) WFLYUT0022: Contexte web désenregistré : /
  484. 2017-05-11 16:32:53,596 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  485. 2017-05-11 16:32:53,597 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  486. 2017-05-11 16:32:53,616 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Arrêt du service Weld pour le déploiement xa-cms-wli.war
  487. 2017-05-11 16:32:55,697 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 2102ms
  488. 2017-05-11 16:32:55,698 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  489. 2017-05-11 16:33:05,022 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.
  490. 2017-05-11 16:33:05,023 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.
  491. 2017-05-11 16:33:05,023 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.
  492. 2017-05-11 16:33:05,024 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.
  493. 2017-05-11 16:33:05,025 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.
  494. 2017-05-11 16:33:05,026 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.
  495. 2017-05-11 16:33:05,026 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.
  496. 2017-05-11 16:33:05,048 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.
  497. 2017-05-11 16:33:05,086 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.
  498. 2017-05-11 16:33:05,086 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.
  499. 2017-05-11 16:33:05,087 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.
  500. 2017-05-11 16:33:05,565 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld xa-cms-wli.war
  501. 2017-05-11 16:33:05,821 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0004: Déploiement du pilote compatible JDCB class org.hsqldb.jdbc.JDBCDriver (version 2.3)
  502. 2017-05-11 16:33:05,825 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0005: Déploiement du pilote non compatible JDCB class com.mysql.jdbc.Driver (version 5.1)
  503. 2017-05-11 16:33:05,826 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : xa-cms-wli.war
  504. 2017-05-11 16:33:05,830 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  505. 2017-05-11 16:33:05,831 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  506. 2017-05-11 16:33:05,832 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement xa-cms-wli.war
  507. 2017-05-11 16:33:05,993 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.xmlbeans.XMLBeansJSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.MappedXMLOutputFactory from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  508. 2017-05-11 16:33:05,959 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomPojoProvider because of underlying class loading error: Type org.apache.abdera.model.ExtensibleElement from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  509. 2017-05-11 16:33:06,000 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomEntryProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  510. 2017-05-11 16:33:06,002 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomFeedProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  511. 2017-05-11 16:33:06,324 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.json.JSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.TypeConverter from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  512. 2017-05-11 16:33:06,720 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  513. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
  514. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  515. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  516. at java.lang.Thread.run(Thread.java:745)
  517. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider
  518. at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:208)
  519. at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:107)
  520. at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:122)
  521. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:136)
  522. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:127)
  523. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
  524. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
  525. at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  526. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  527. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  528. at java.lang.Thread.run(Thread.java:745)
  529. at org.jboss.threads.JBossThread.run(JBossThread.java:320)
  530.  
  531. 2017-05-11 16:33:06,725 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\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".WeldStartService: Failed to start service
  532. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider"}}
  533. 2017-05-11 16:33:06,786 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"
  534. 2017-05-11 16:33:06,787 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  535. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  536.  
  537. 2017-05-11 16:35:55,922 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  538. 2017-05-11 16:35:55,923 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  539. 2017-05-11 16:35:56,962 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1041ms
  540. 2017-05-11 16:35:56,963 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")
  541. 2017-05-11 16:36:20,839 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.
  542. 2017-05-11 16:36:20,840 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.
  543. 2017-05-11 16:36:20,841 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.
  544. 2017-05-11 16:36:20,842 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.
  545. 2017-05-11 16:36:20,843 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.
  546. 2017-05-11 16:36:20,844 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.
  547. 2017-05-11 16:36:20,844 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.
  548. 2017-05-11 16:36:20,875 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.
  549. 2017-05-11 16:36:20,914 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.
  550. 2017-05-11 16:36:20,915 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.
  551. 2017-05-11 16:36:20,915 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.
  552. 2017-05-11 16:36:21,488 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld xa-cms-wli.war
  553. 2017-05-11 16:36:21,840 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0004: Déploiement du pilote compatible JDCB class org.hsqldb.jdbc.JDBCDriver (version 2.3)
  554. 2017-05-11 16:36:21,842 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0005: Déploiement du pilote non compatible JDCB class com.mysql.jdbc.Driver (version 5.1)
  555. 2017-05-11 16:36:21,843 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Démarrage des services pour le déploiement CDI : xa-cms-wli.war
  556. 2017-05-11 16:36:21,845 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  557. 2017-05-11 16:36:21,845 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  558. 2017-05-11 16:36:21,846 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement xa-cms-wli.war
  559. 2017-05-11 16:36:21,908 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomPojoProvider because of underlying class loading error: Type org.apache.abdera.model.ExtensibleElement from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  560. 2017-05-11 16:36:21,913 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.xmlbeans.XMLBeansJSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.MappedXMLOutputFactory from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  561. 2017-05-11 16:36:21,919 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomEntryProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  562. 2017-05-11 16:36:21,921 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomFeedProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  563. 2017-05-11 16:36:21,933 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 2) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.json.JSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.TypeConverter from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  564. 2017-05-11 16:36:22,196 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  565. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
  566. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  567. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  568. at java.lang.Thread.run(Thread.java:745)
  569. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider
  570. at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:208)
  571. at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:107)
  572. at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:122)
  573. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:136)
  574. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:127)
  575. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
  576. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
  577. at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  578. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  579. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  580. at java.lang.Thread.run(Thread.java:745)
  581. at org.jboss.threads.JBossThread.run(JBossThread.java:320)
  582.  
  583. 2017-05-11 16:36:22,281 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\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".WeldStartService: Failed to start service
  584. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider"}}
  585. 2017-05-11 16:36:22,349 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"
  586. 2017-05-11 16:36:22,352 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  587. WFLYCTL0184: Nouvelles dépendances manquantes/non complétées :
  588. Dépendances service jboss.deployment.unit."xa-cms-wli.war".WeldBootstrapService (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator, WFLYCTL0208: ... and 8 more ]
  589. Dépendances service jboss.deployment.unit."xa-cms-wli.war".WeldStartService (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator, service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".WeldInstantiator, WFLYCTL0208: ... and 10 more ]
  590. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START]
  591. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  592. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START]
  593. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  594. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  595. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  596. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  597. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  598. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  599. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  600. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  601. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  602. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".START]
  603. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  604. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.cxf.transport.http.Servlet3ContinuationProvider$Servlet3Continuation".START]
  605. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".START]
  606. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  607. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".START]
  608. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START]
  609. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  610. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$1".START]
  611. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START]
  612. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  613. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".START]
  614. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldInitialListener".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
  615. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldInitialListener".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  616. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldInitialListener".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldInitialListener".START]
  617. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".CREATE (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
  618. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".START (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  619. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".WeldInstantiator (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".START]
  620. Dépendances service jboss.deployment.unit."xa-cms-wli.war".ee.ComponentRegistry (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  621. Dépendances service jboss.deployment.unit."xa-cms-wli.war".jndiDependencyService (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".component."org.apache.tapestry5.TapestryFilter".START, service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START, service jboss.deployment.unit."xa-cms-wli.war".component."org.jboss.weld.servlet.WeldTerminalListener".START, WFLYCTL0208: ... and 7 more ]
  622. Dépendances service jboss.undertow.deployment.default-server.default-host./ (non disponibles) : [service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService]
  623. Dépendances service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./]
  624. Dépendances service jboss.undertow.deployment.default-server.default-host./.codec (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  625. Dépendances service jboss.undertow.deployment.default-server.default-host./.session (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  626. Dépendances service org.wildfly.request-controller.control-point."xa-cms-wli.war".undertow (non disponibles) : [service jboss.undertow.deployment.default-server.default-host./.UndertowDeploymentInfoService]
  627. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".WeldStartService
  628. service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  629.  
  630. 2017-05-11 16:37:10,800 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  631. 2017-05-11 16:37:10,799 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  632. 2017-05-11 16:37:11,847 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 1048ms
  633. 2017-05-11 16:37:11,850 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")
  634. 2017-05-11 16:37:27,927 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-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  635. 2017-05-11 16:37:27,927 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  636. 2017-05-11 16:37:27,928 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  637. 2017-05-11 16:37:27,928 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-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.
  638. 2017-05-11 16:37:27,928 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  639. 2017-05-11 16:37:27,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  640. 2017-05-11 16:37:27,929 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  641. 2017-05-11 16:37:27,950 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  642. 2017-05-11 16:37:27,980 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  643. 2017-05-11 16:37:27,980 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  644. 2017-05-11 16:37:27,980 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) 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.
  645. 2017-05-11 16:37:28,416 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Traitement du déploiement Weld xa-cms-wli.war
  646. 2017-05-11 16:37:28,545 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0004: Déploiement du pilote compatible JDCB class org.hsqldb.jdbc.JDBCDriver (version 2.3)
  647. 2017-05-11 16:37:28,548 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0005: Déploiement du pilote non compatible JDCB class com.mysql.jdbc.Driver (version 5.1)
  648. 2017-05-11 16:37:28,548 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Démarrage des services pour le déploiement CDI : xa-cms-wli.war
  649. 2017-05-11 16:37:28,550 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  650. 2017-05-11 16:37:28,551 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  651. 2017-05-11 16:37:28,551 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Lancement du service Weld pour le déploiement xa-cms-wli.war
  652. 2017-05-11 16:37:28,605 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 4) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomPojoProvider because of underlying class loading error: Type org.apache.abdera.model.ExtensibleElement from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  653. 2017-05-11 16:37:28,610 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.xmlbeans.XMLBeansJSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.MappedXMLOutputFactory from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  654. 2017-05-11 16:37:28,612 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomEntryProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  655. 2017-05-11 16:37:28,617 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.atom.AtomFeedProvider because of underlying class loading error: Type org.apache.abdera.Abdera from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  656. 2017-05-11 16:37:28,645 INFO [org.jboss.weld.Bootstrap] (Weld Thread Pool -- 3) WELD-000119: Not generating any bean definitions from org.apache.cxf.jaxrs.provider.json.JSONProvider because of underlying class loading error: Type org.codehaus.jettison.mapped.TypeConverter from [Module "deployment.xa-cms-wli.war:main" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error.
  657. 2017-05-11 16:37:28,818 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  658. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
  659. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  660. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  661. at java.lang.Thread.run(Thread.java:745)
  662. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider
  663. at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:208)
  664. at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:107)
  665. at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:122)
  666. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:136)
  667. at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:127)
  668. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
  669. at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
  670. at java.util.concurrent.FutureTask.run(FutureTask.java:266)
  671. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  672. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  673. at java.lang.Thread.run(Thread.java:745)
  674. at org.jboss.threads.JBossThread.run(JBossThread.java:320)
  675.  
  676. 2017-05-11 16:37:28,822 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\".WeldStartService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".WeldStartService: Failed to start service
  677. Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @Dependent: class org.apache.cxf.jaxrs.provider.XSLTJaxbProvider"}}
  678. 2017-05-11 16:37:28,878 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"
  679. 2017-05-11 16:37:28,878 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  680. WFLYCTL0185: Services nouvellement modifiés :
  681. service jboss.deployment.unit."xa-cms-wli.war".component."org.eclipse.jetty.continuation.Servlet3Continuation$2".WeldInstantiator (nouvellement disponible)
  682. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".WeldStartService
  683. service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".WeldStartService: Failed to start service
  684.  
  685. 2017-05-11 16:37:28,885 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  686. 2017-05-11 16:37:28,897 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  687. 2017-05-11 16:37:28,928 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_com.mysql.jdbc.Driver_5_1
  688. 2017-05-11 16:37:28,933 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = xa-cms-wli.war_org.hsqldb.jdbc.JDBCDriver_2_3
  689. 2017-05-11 16:37:29,007 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 83) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  690. 2017-05-11 16:37:29,120 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 82) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  691. 2017-05-11 16:37:29,136 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 86) WFLYUT0022: Contexte web désenregistré : /xa-cms-admin
  692. 2017-05-11 16:37:29,161 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  693. 2017-05-11 16:37:29,207 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  694. 2017-05-11 16:37:29,243 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: L'hôte default-host s'arrête
  695. 2017-05-11 16:37:29,271 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  696. 2017-05-11 16:37:29,287 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 381ms
  697. 2017-05-11 16:37:29,294 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  698. 2017-05-11 16:37:29,298 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 391ms
  699. 2017-05-11 16:37:29,300 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  700. 2017-05-11 16:37:29,302 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  701. 2017-05-11 16:37:29,303 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  702. 2017-05-11 16:37:29,383 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 475ms
  703. 2017-05-11 16:37:30,587 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1680ms
  704. 2017-05-11 16:37:30,613 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 1698ms
  705. 2017-05-11 16:40:49,422 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  706. 2017-05-11 16:40:52,943 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  707. 2017-05-11 16:40:53,256 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  708. 2017-05-11 16:40:53,258 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  709. awt.toolkit = sun.awt.windows.WToolkit
  710. file.encoding = Cp1252
  711. file.encoding.pkg = sun.io
  712. file.separator = \
  713. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  714. java.awt.headless = true
  715. java.awt.printerjob = sun.awt.windows.WPrinterJob
  716. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  717. java.class.version = 52.0
  718. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  719. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  720. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  721. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  722. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  723. java.net.preferIPv4Stack = true
  724. java.runtime.name = Java(TM) SE Runtime Environment
  725. java.runtime.version = 1.8.0_121-b13
  726. java.specification.name = Java Platform API Specification
  727. java.specification.vendor = Oracle Corporation
  728. java.specification.version = 1.8
  729. java.util.logging.manager = org.jboss.logmanager.LogManager
  730. java.vendor = Oracle Corporation
  731. java.vendor.url = http://java.oracle.com/
  732. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  733. java.version = 1.8.0_121
  734. java.vm.info = mixed mode
  735. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  736. java.vm.specification.name = Java Virtual Machine Specification
  737. java.vm.specification.vendor = Oracle Corporation
  738. java.vm.specification.version = 1.8
  739. java.vm.vendor = Oracle Corporation
  740. java.vm.version = 25.121-b13
  741. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  742. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  743. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  744. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  745. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  746. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  747. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  748. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  749. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  750. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  751. jboss.bind.address = localhost
  752. jboss.bind.address.management = localhost
  753. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  754. jboss.host.name = l82564
  755. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  756. jboss.modules.system.pkgs = org.jboss.byteman
  757. jboss.node.name = l82564
  758. jboss.qualified.host.name = l82564
  759. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  760. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  761. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  762. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  763. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  764. jboss.server.name = l82564
  765. jboss.server.persist.config = true
  766. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  767. line.separator =
  768.  
  769. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  770. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  771. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  772. org.jboss.logmanager.nocolor = true
  773. org.jboss.resolver.warning = true
  774. org.xml.sax.driver = __redirected.__XMLReaderFactory
  775. os.arch = amd64
  776. os.name = Windows 7
  777. os.version = 6.1
  778. path.separator = ;
  779. program.name = JBossTools: Red Hat JBoss EAP 7.x
  780. sun.arch.data.model = 64
  781. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  782. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  783. sun.cpu.endian = little
  784. sun.cpu.isalist = amd64
  785. sun.desktop = windows
  786. sun.io.unicode.encoding = UnicodeLittle
  787. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  788. sun.java.launcher = SUN_STANDARD
  789. sun.jnu.encoding = Cp1252
  790. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  791. sun.os.patch.level = Service Pack 1
  792. sun.rmi.dgc.client.gcInterval = 3600000
  793. sun.rmi.dgc.server.gcInterval = 3600000
  794. user.country = FR
  795. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  796. user.home = C:\Utilisateurs\A665340
  797. user.language = fr
  798. user.name = A665340
  799. user.script =
  800. user.timezone = Europe/Paris
  801. user.variant =
  802. 2017-05-11 16:40:53,259 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  803. 2017-05-11 16:40:57,872 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 14) 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é.
  804. 2017-05-11 16:40:58,363 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "jboss-helloworld.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"jboss-helloworld.war\")] en double"
  805. 2017-05-11 16:40:58,409 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  806. 2017-05-11 16:40:58,414 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  807. 2017-05-11 16:40:58,455 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 36ms
  808. 2017-05-11 16:41:52,982 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  809. 2017-05-11 16:41:53,369 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  810. 2017-05-11 16:41:53,484 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  811. 2017-05-11 16:41:53,485 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Propriétés de système configurées :
  812. awt.toolkit = sun.awt.windows.WToolkit
  813. file.encoding = Cp1252
  814. file.encoding.pkg = sun.io
  815. file.separator = \
  816. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  817. java.awt.headless = true
  818. java.awt.printerjob = sun.awt.windows.WPrinterJob
  819. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  820. java.class.version = 52.0
  821. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  822. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  823. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  824. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  825. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  826. java.net.preferIPv4Stack = true
  827. java.runtime.name = Java(TM) SE Runtime Environment
  828. java.runtime.version = 1.8.0_121-b13
  829. java.specification.name = Java Platform API Specification
  830. java.specification.vendor = Oracle Corporation
  831. java.specification.version = 1.8
  832. java.util.logging.manager = org.jboss.logmanager.LogManager
  833. java.vendor = Oracle Corporation
  834. java.vendor.url = http://java.oracle.com/
  835. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  836. java.version = 1.8.0_121
  837. java.vm.info = mixed mode
  838. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  839. java.vm.specification.name = Java Virtual Machine Specification
  840. java.vm.specification.vendor = Oracle Corporation
  841. java.vm.specification.version = 1.8
  842. java.vm.vendor = Oracle Corporation
  843. java.vm.version = 25.121-b13
  844. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  845. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  846. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  847. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  848. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  849. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  850. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  851. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  852. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  853. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  854. jboss.bind.address = localhost
  855. jboss.bind.address.management = localhost
  856. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  857. jboss.host.name = l82564
  858. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  859. jboss.modules.system.pkgs = org.jboss.byteman
  860. jboss.node.name = l82564
  861. jboss.qualified.host.name = l82564
  862. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  863. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  864. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  865. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  866. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  867. jboss.server.name = l82564
  868. jboss.server.persist.config = true
  869. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  870. line.separator =
  871.  
  872. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  873. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  874. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  875. org.jboss.logmanager.nocolor = true
  876. org.jboss.resolver.warning = true
  877. org.xml.sax.driver = __redirected.__XMLReaderFactory
  878. os.arch = amd64
  879. os.name = Windows 7
  880. os.version = 6.1
  881. path.separator = ;
  882. program.name = JBossTools: Red Hat JBoss EAP 7.x
  883. sun.arch.data.model = 64
  884. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  885. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  886. sun.cpu.endian = little
  887. sun.cpu.isalist = amd64
  888. sun.desktop = windows
  889. sun.io.unicode.encoding = UnicodeLittle
  890. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  891. sun.java.launcher = SUN_STANDARD
  892. sun.jnu.encoding = Cp1252
  893. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  894. sun.os.patch.level = Service Pack 1
  895. sun.rmi.dgc.client.gcInterval = 3600000
  896. sun.rmi.dgc.server.gcInterval = 3600000
  897. user.country = FR
  898. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  899. user.home = C:\Utilisateurs\A665340
  900. user.language = fr
  901. user.name = A665340
  902. user.script =
  903. user.timezone = Europe/Paris
  904. user.variant =
  905. 2017-05-11 16:41:53,486 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  906. 2017-05-11 16:41:56,409 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 26) 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é.
  907. 2017-05-11 16:41:56,522 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  908. 2017-05-11 16:41:56,632 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  909. 2017-05-11 16:41:56,638 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  910. 2017-05-11 16:41:56,988 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  911. 2017-05-11 16:41:57,015 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.
  912. 2017-05-11 16:41:57,030 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  913. 2017-05-11 16:41:57,044 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  914. 2017-05-11 16:41:57,064 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  915. 2017-05-11 16:41:57,072 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  916. 2017-05-11 16:41:57,090 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  917. 2017-05-11 16:41:57,123 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
  918. 2017-05-11 16:41:57,142 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  919. 2017-05-11 16:41:57,446 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  920. 2017-05-11 16:41:57,447 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  921. 2017-05-11 16:41:57,653 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)
  922. 2017-05-11 16:41:57,658 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
  923. 2017-05-11 16:41:57,657 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Démarrage du service de nommage
  924. 2017-05-11 16:41:57,666 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  925. 2017-05-11 16:41:57,998 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: '[]']
  926. 2017-05-11 16:41:58,089 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  927. 2017-05-11 16:41:58,089 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  928. 2017-05-11 16:41:59,057 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final-redhat-1
  929. 2017-05-11 16:41:59,078 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")
  930. 2017-05-11 16:41:59,079 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  931. 2017-05-11 16:41:59,154 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  932. 2017-05-11 16:41:59,174 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: A démarré le serveur default-server.
  933. 2017-05-11 16:41:59,410 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: L'hôte default-host démarre
  934. 2017-05-11 16:41:59,685 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  935. 2017-05-11 16:41:59,996 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  936. 2017-05-11 16:42:00,682 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  937. 2017-05-11 16:42:01,216 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  938. 2017-05-11 16:42:02,827 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  939. 2017-05-11 16:42:02,830 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  940. 2017-05-11 16:42:03,191 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  941. 2017-05-11 16:42:03,661 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  942. 2017-05-11 16:42:03,716 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  943. 2017-05-11 16:42:03,865 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.3 (redhat)
  944. 2017-05-11 16:42:03,907 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  945. 2017-05-11 16:42:03,907 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  946. 2017-05-11 16:42:05,977 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 61) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  947. 2017-05-11 16:42:06,050 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  948. 2017-05-11 16:42:07,433 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  949. 2017-05-11 16:42:07,597 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  950. 2017-05-11 16:42:07,597 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  951. 2017-05-11 16:42:07,805 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  952. 2017-05-11 16:42:07,806 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  953. 2017-05-11 16:42:07,807 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 15729ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  954. 2017-05-11 16:44:14,294 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  955. 2017-05-11 16:44:14,310 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  956. 2017-05-11 16:44:14,575 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  957. 2017-05-11 16:44:14,575 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  958. 2017-05-11 16:44:14,653 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: L'hôte default-host s'arrête
  959. 2017-05-11 16:44:14,653 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  960. 2017-05-11 16:44:14,669 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  961. 2017-05-11 16:44:14,731 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  962. 2017-05-11 16:44:14,763 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  963. 2017-05-11 16:44:14,825 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  964. 2017-05-11 16:44:14,825 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  965. 2017-05-11 16:44:14,825 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  966. 2017-05-11 16:44:14,872 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 526ms
  967. 2017-05-11 16:44:14,887 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 541ms
  968. 2017-05-11 16:44:14,903 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 552ms
  969. 2017-05-11 16:45:50,561 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  970. 2017-05-11 16:45:51,015 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  971. 2017-05-11 16:45:51,139 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  972. 2017-05-11 16:45:51,139 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  973. awt.toolkit = sun.awt.windows.WToolkit
  974. file.encoding = Cp1252
  975. file.encoding.pkg = sun.io
  976. file.separator = \
  977. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  978. java.awt.headless = true
  979. java.awt.printerjob = sun.awt.windows.WPrinterJob
  980. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  981. java.class.version = 52.0
  982. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  983. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  984. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  985. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  986. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  987. java.net.preferIPv4Stack = true
  988. java.runtime.name = Java(TM) SE Runtime Environment
  989. java.runtime.version = 1.8.0_121-b13
  990. java.specification.name = Java Platform API Specification
  991. java.specification.vendor = Oracle Corporation
  992. java.specification.version = 1.8
  993. java.util.logging.manager = org.jboss.logmanager.LogManager
  994. java.vendor = Oracle Corporation
  995. java.vendor.url = http://java.oracle.com/
  996. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  997. java.version = 1.8.0_121
  998. java.vm.info = mixed mode
  999. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1000. java.vm.specification.name = Java Virtual Machine Specification
  1001. java.vm.specification.vendor = Oracle Corporation
  1002. java.vm.specification.version = 1.8
  1003. java.vm.vendor = Oracle Corporation
  1004. java.vm.version = 25.121-b13
  1005. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1006. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1007. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1008. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1009. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1010. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1011. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1012. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1013. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1014. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1015. jboss.bind.address = localhost
  1016. jboss.bind.address.management = localhost
  1017. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1018. jboss.host.name = l82564
  1019. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1020. jboss.modules.system.pkgs = org.jboss.byteman
  1021. jboss.node.name = l82564
  1022. jboss.qualified.host.name = l82564
  1023. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1024. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1025. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1026. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1027. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1028. jboss.server.name = l82564
  1029. jboss.server.persist.config = true
  1030. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1031. line.separator =
  1032.  
  1033. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1034. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1035. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1036. org.jboss.logmanager.nocolor = true
  1037. org.jboss.resolver.warning = true
  1038. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1039. os.arch = amd64
  1040. os.name = Windows 7
  1041. os.version = 6.1
  1042. path.separator = ;
  1043. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1044. sun.arch.data.model = 64
  1045. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  1046. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1047. sun.cpu.endian = little
  1048. sun.cpu.isalist = amd64
  1049. sun.desktop = windows
  1050. sun.io.unicode.encoding = UnicodeLittle
  1051. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1052. sun.java.launcher = SUN_STANDARD
  1053. sun.jnu.encoding = Cp1252
  1054. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1055. sun.os.patch.level = Service Pack 1
  1056. sun.rmi.dgc.client.gcInterval = 3600000
  1057. sun.rmi.dgc.server.gcInterval = 3600000
  1058. user.country = FR
  1059. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1060. user.home = C:\Utilisateurs\A665340
  1061. user.language = fr
  1062. user.name = A665340
  1063. user.script =
  1064. user.timezone = Europe/Paris
  1065. user.variant =
  1066. 2017-05-11 16:45:51,139 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  1067. 2017-05-11 16:45:53,713 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 3) 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é.
  1068. 2017-05-11 16:45:54,137 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "jboss-helloworld.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"jboss-helloworld.war\")] en double"
  1069. 2017-05-11 16:45:54,152 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  1070. 2017-05-11 16:45:54,152 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1071. 2017-05-11 16:45:54,168 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 10ms
  1072. 2017-05-11 16:46:15,149 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1073. 2017-05-11 16:46:15,540 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1074. 2017-05-11 16:46:15,664 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  1075. 2017-05-11 16:46:15,664 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  1076. awt.toolkit = sun.awt.windows.WToolkit
  1077. file.encoding = Cp1252
  1078. file.encoding.pkg = sun.io
  1079. file.separator = \
  1080. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1081. java.awt.headless = true
  1082. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1083. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1084. java.class.version = 52.0
  1085. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1086. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1087. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1088. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1089. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  1090. java.net.preferIPv4Stack = true
  1091. java.runtime.name = Java(TM) SE Runtime Environment
  1092. java.runtime.version = 1.8.0_121-b13
  1093. java.specification.name = Java Platform API Specification
  1094. java.specification.vendor = Oracle Corporation
  1095. java.specification.version = 1.8
  1096. java.util.logging.manager = org.jboss.logmanager.LogManager
  1097. java.vendor = Oracle Corporation
  1098. java.vendor.url = http://java.oracle.com/
  1099. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1100. java.version = 1.8.0_121
  1101. java.vm.info = mixed mode
  1102. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1103. java.vm.specification.name = Java Virtual Machine Specification
  1104. java.vm.specification.vendor = Oracle Corporation
  1105. java.vm.specification.version = 1.8
  1106. java.vm.vendor = Oracle Corporation
  1107. java.vm.version = 25.121-b13
  1108. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1109. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1110. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1111. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1112. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1113. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1114. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1115. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1116. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1117. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1118. jboss.bind.address = localhost
  1119. jboss.bind.address.management = localhost
  1120. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1121. jboss.host.name = l82564
  1122. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1123. jboss.modules.system.pkgs = org.jboss.byteman
  1124. jboss.node.name = l82564
  1125. jboss.qualified.host.name = l82564
  1126. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1127. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1128. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1129. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1130. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1131. jboss.server.name = l82564
  1132. jboss.server.persist.config = true
  1133. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1134. line.separator =
  1135.  
  1136. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1137. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1138. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1139. org.jboss.logmanager.nocolor = true
  1140. org.jboss.resolver.warning = true
  1141. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1142. os.arch = amd64
  1143. os.name = Windows 7
  1144. os.version = 6.1
  1145. path.separator = ;
  1146. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1147. sun.arch.data.model = 64
  1148. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  1149. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1150. sun.cpu.endian = little
  1151. sun.cpu.isalist = amd64
  1152. sun.desktop = windows
  1153. sun.io.unicode.encoding = UnicodeLittle
  1154. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1155. sun.java.launcher = SUN_STANDARD
  1156. sun.jnu.encoding = Cp1252
  1157. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1158. sun.os.patch.level = Service Pack 1
  1159. sun.rmi.dgc.client.gcInterval = 3600000
  1160. sun.rmi.dgc.server.gcInterval = 3600000
  1161. user.country = FR
  1162. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1163. user.home = C:\Utilisateurs\A665340
  1164. user.language = fr
  1165. user.name = A665340
  1166. user.script =
  1167. user.timezone = Europe/Paris
  1168. user.variant =
  1169. 2017-05-11 16:46:15,664 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  1170. 2017-05-11 16:46:18,205 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é.
  1171. 2017-05-11 16:46:18,376 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1172. 2017-05-11 16:46:18,393 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.3.6.Final-redhat-1
  1173. 2017-05-11 16:46:18,393 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1174. 2017-05-11 16:46:18,486 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.
  1175. 2017-05-11 16:46:18,502 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1176. 2017-05-11 16:46:18,564 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1177. 2017-05-11 16:46:18,596 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1178. 2017-05-11 16:46:18,643 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1179. 2017-05-11 16:46:18,658 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1180. 2017-05-11 16:46:18,845 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
  1181. 2017-05-11 16:46:18,877 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1182. 2017-05-11 16:46:18,908 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  1183. 2017-05-11 16:46:18,908 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Démarrage du service de nommage
  1184. 2017-05-11 16:46:18,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1185. 2017-05-11 16:46:18,986 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)
  1186. 2017-05-11 16:46:19,017 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  1187. 2017-05-11 16:46:19,033 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1188. 2017-05-11 16:46:19,033 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1189. 2017-05-11 16:46:19,563 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: '[]']
  1190. 2017-05-11 16:46:19,845 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: A démarré le serveur default-server.
  1191. 2017-05-11 16:46:19,860 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
  1192. 2017-05-11 16:46:19,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: L'hôte default-host démarre
  1193. 2017-05-11 16:46:19,876 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.18.Final-redhat-1
  1194. 2017-05-11 16:46:19,860 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  1195. 2017-05-11 16:46:20,110 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1196. 2017-05-11 16:46:20,406 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  1197. 2017-05-11 16:46:20,531 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1198. 2017-05-11 16:46:20,687 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1199. 2017-05-11 16:46:21,515 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  1200. 2017-05-11 16:46:21,562 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1201. 2017-05-11 16:46:21,733 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1202. 2017-05-11 16:46:22,670 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1203. 2017-05-11 16:46:22,670 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1204. 2017-05-11 16:46:22,811 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1205. 2017-05-11 16:46:23,120 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1206. 2017-05-11 16:46:23,151 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1207. 2017-05-11 16:46:23,167 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.3 (redhat)
  1208. 2017-05-11 16:46:23,245 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1209. 2017-05-11 16:46:23,276 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1210. 2017-05-11 16:46:25,014 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 60) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1211. 2017-05-11 16:46:25,015 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1212. 2017-05-11 16:46:25,701 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1213. 2017-05-11 16:46:25,733 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1214. 2017-05-11 16:46:25,733 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1215. 2017-05-11 16:46:26,013 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1216. 2017-05-11 16:46:26,013 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1217. 2017-05-11 16:46:26,013 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 11551ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  1218. 2017-05-11 16:48:50,899 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1219. 2017-05-11 16:48:50,929 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1220. 2017-05-11 16:48:51,025 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1221. 2017-05-11 16:48:51,029 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1222. 2017-05-11 16:48:51,100 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: L'hôte default-host s'arrête
  1223. 2017-05-11 16:48:51,102 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1224. 2017-05-11 16:48:51,109 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1225. 2017-05-11 16:48:51,147 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1226. 2017-05-11 16:48:51,182 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  1227. 2017-05-11 16:48:51,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1228. 2017-05-11 16:48:51,292 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 339ms
  1229. 2017-05-11 16:48:51,300 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  1230. 2017-05-11 16:48:51,308 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1231. 2017-05-11 16:48:51,365 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 409ms
  1232. 2017-05-11 16:48:51,376 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 421ms
  1233. 2017-05-11 16:49:52,806 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1234. 2017-05-11 16:49:53,098 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1235. 2017-05-11 16:49:53,182 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
  1236. 2017-05-11 16:49:53,184 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Propriétés de système configurées :
  1237. awt.toolkit = sun.awt.windows.WToolkit
  1238. file.encoding = Cp1252
  1239. file.encoding.pkg = sun.io
  1240. file.separator = \
  1241. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1242. java.awt.headless = true
  1243. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1244. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1245. java.class.version = 52.0
  1246. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1247. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1248. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1249. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1250. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  1251. java.net.preferIPv4Stack = true
  1252. java.runtime.name = Java(TM) SE Runtime Environment
  1253. java.runtime.version = 1.8.0_121-b13
  1254. java.specification.name = Java Platform API Specification
  1255. java.specification.vendor = Oracle Corporation
  1256. java.specification.version = 1.8
  1257. java.util.logging.manager = org.jboss.logmanager.LogManager
  1258. java.vendor = Oracle Corporation
  1259. java.vendor.url = http://java.oracle.com/
  1260. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1261. java.version = 1.8.0_121
  1262. java.vm.info = mixed mode
  1263. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1264. java.vm.specification.name = Java Virtual Machine Specification
  1265. java.vm.specification.vendor = Oracle Corporation
  1266. java.vm.specification.version = 1.8
  1267. java.vm.vendor = Oracle Corporation
  1268. java.vm.version = 25.121-b13
  1269. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1270. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1271. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1272. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1273. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1274. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1275. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1276. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1277. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1278. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1279. jboss.bind.address = localhost
  1280. jboss.bind.address.management = localhost
  1281. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1282. jboss.host.name = l82564
  1283. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1284. jboss.modules.system.pkgs = org.jboss.byteman
  1285. jboss.node.name = l82564
  1286. jboss.qualified.host.name = l82564
  1287. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1288. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1289. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1290. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1291. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1292. jboss.server.name = l82564
  1293. jboss.server.persist.config = true
  1294. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1295. line.separator =
  1296.  
  1297. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1298. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1299. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1300. org.jboss.logmanager.nocolor = true
  1301. org.jboss.resolver.warning = true
  1302. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1303. os.arch = amd64
  1304. os.name = Windows 7
  1305. os.version = 6.1
  1306. path.separator = ;
  1307. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1308. sun.arch.data.model = 64
  1309. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  1310. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1311. sun.cpu.endian = little
  1312. sun.cpu.isalist = amd64
  1313. sun.desktop = windows
  1314. sun.io.unicode.encoding = UnicodeLittle
  1315. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1316. sun.java.launcher = SUN_STANDARD
  1317. sun.jnu.encoding = Cp1252
  1318. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1319. sun.os.patch.level = Service Pack 1
  1320. sun.rmi.dgc.client.gcInterval = 3600000
  1321. sun.rmi.dgc.server.gcInterval = 3600000
  1322. user.country = FR
  1323. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1324. user.home = C:\Utilisateurs\A665340
  1325. user.language = fr
  1326. user.name = A665340
  1327. user.script =
  1328. user.timezone = Europe/Paris
  1329. user.variant =
  1330. 2017-05-11 16:49:53,184 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  1331. 2017-05-11 16:49:55,115 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 16) 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é.
  1332. 2017-05-11 16:49:55,436 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1333. 2017-05-11 16:49:55,456 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.3.6.Final-redhat-1
  1334. 2017-05-11 16:49:55,466 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1335. 2017-05-11 16:49:55,526 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)
  1336. 2017-05-11 16:49:55,542 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  1337. 2017-05-11 16:49:55,550 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1338. 2017-05-11 16:49:55,580 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  1339. 2017-05-11 16:49:55,584 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.
  1340. 2017-05-11 16:49:55,587 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1341. 2017-05-11 16:49:55,595 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1342. 2017-05-11 16:49:55,598 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1343. 2017-05-11 16:49:55,625 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1344. 2017-05-11 16:49:55,632 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1345. 2017-05-11 16:49:55,632 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1346. 2017-05-11 16:49:55,645 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1347. 2017-05-11 16:49:55,803 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
  1348. 2017-05-11 16:49:55,871 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Démarrage du service de nommage
  1349. 2017-05-11 16:49:55,871 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1350. 2017-05-11 16:49:56,113 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: '[]']
  1351. 2017-05-11 16:49:56,216 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
  1352. 2017-05-11 16:49:56,252 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  1353. 2017-05-11 16:49:56,404 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: A démarré le serveur default-server.
  1354. 2017-05-11 16:49:56,409 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: L'hôte default-host démarre
  1355. 2017-05-11 16:49:56,422 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
  1356. 2017-05-11 16:49:56,562 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1357. 2017-05-11 16:49:56,914 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1358. 2017-05-11 16:49:57,080 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1359. 2017-05-11 16:49:57,084 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1360. 2017-05-11 16:49:57,094 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1361. 2017-05-11 16:49:57,095 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1362. 2017-05-11 16:49:57,126 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  1363. 2017-05-11 16:49:57,803 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1364. 2017-05-11 16:49:57,918 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  1365. 2017-05-11 16:49:59,457 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1366. 2017-05-11 16:49:59,518 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1367. 2017-05-11 16:49:59,645 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1368. 2017-05-11 16:50:00,496 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1369. 2017-05-11 16:50:00,520 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1370. 2017-05-11 16:50:00,571 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.3 (redhat)
  1371. 2017-05-11 16:50:00,906 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1372. 2017-05-11 16:50:00,907 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1373. 2017-05-11 16:50:06,339 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1374. 2017-05-11 16:50:06,340 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1375. 2017-05-11 16:50:06,341 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1376. 2017-05-11 16:50:06,364 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1377. 2017-05-11 16:50:06,870 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 61) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1378. 2017-05-11 16:50:06,922 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1379. 2017-05-11 16:50:07,372 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1380. 2017-05-11 16:50:07,376 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"
  1381. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1382. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1383. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1384. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1385. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1386. at java.lang.Thread.run(Thread.java:745)
  1387. 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
  1388. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1389. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1390. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1391. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1392. ... 5 more
  1393.  
  1394. 2017-05-11 16:50:07,616 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1395. 2017-05-11 16:50:08,624 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.
  1396. 2017-05-11 16:50:08,625 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.
  1397. 2017-05-11 16:50:08,625 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.
  1398. 2017-05-11 16:50:08,626 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.
  1399. 2017-05-11 16:50:08,626 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.
  1400. 2017-05-11 16:50:08,626 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.
  1401. 2017-05-11 16:50:08,627 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.
  1402. 2017-05-11 16:50:08,644 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.
  1403. 2017-05-11 16:50:08,655 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.
  1404. 2017-05-11 16:50:08,681 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.
  1405. 2017-05-11 16:50:08,681 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.
  1406. 2017-05-11 16:50:08,681 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.
  1407. 2017-05-11 16:50:08,782 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1408. 2017-05-11 16:50:08,785 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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"
  1409. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1410. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1411. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1412. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1413. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1414. at java.lang.Thread.run(Thread.java:745)
  1415. 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
  1416. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1417. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1418. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1419. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1420. ... 5 more
  1421.  
  1422. 2017-05-11 16:50:08,788 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\"
  1423. 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"}}
  1424. 2017-05-11 16:50:08,789 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\"
  1425. 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"}}
  1426. 2017-05-11 16:50:08,854 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1427. 2017-05-11 16:50:08,855 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1428. 2017-05-11 16:50:08,856 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1429. 2017-05-11 16:50:08,856 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1430. 2017-05-11 16:50:08,858 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  1431. 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"
  1432. 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"
  1433.  
  1434. 2017-05-11 16:50:09,059 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1435. 2017-05-11 16:50:09,060 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1436. 2017-05-11 16:50:09,060 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 16648ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  1437. 2017-05-11 16:50:09,911 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 608ms
  1438. 2017-05-11 16:50:10,263 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 959ms
  1439. 2017-05-11 16:50:10,439 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1440. 2017-05-11 16:50:10,440 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1441. 2017-05-11 16:50:10,440 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  1442. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  1443. service jboss.deployment.unit."xa-cms-admin.war".PARSE
  1444.  
  1445. 2017-05-11 16:52:40,290 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1446. 2017-05-11 16:52:46,863 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.
  1447. 2017-05-11 16:52:46,864 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.
  1448. 2017-05-11 16:52:46,865 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.
  1449. 2017-05-11 16:52:46,866 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.
  1450. 2017-05-11 16:52:46,867 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.
  1451. 2017-05-11 16:52:46,868 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.
  1452. 2017-05-11 16:52:46,868 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.
  1453. 2017-05-11 16:52:46,893 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.
  1454. 2017-05-11 16:52:46,909 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.
  1455. 2017-05-11 16:52:46,944 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.
  1456. 2017-05-11 16:52:46,944 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.
  1457. 2017-05-11 16:52:46,945 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.
  1458. 2017-05-11 16:52:47,061 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1459. 2017-05-11 16:52:47,069 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"
  1460. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1461. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1462. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1463. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1464. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1465. at java.lang.Thread.run(Thread.java:745)
  1466. 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
  1467. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1468. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1469. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1470. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1471. ... 5 more
  1472.  
  1473. 2017-05-11 16:52:47,071 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\"
  1474. 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"}}
  1475. 2017-05-11 16:52:47,136 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1476. 2017-05-11 16:52:47,136 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  1477. 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"
  1478.  
  1479. 2017-05-11 16:53:32,948 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1480. 2017-05-11 16:53:32,962 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1481. 2017-05-11 16:53:33,060 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1482. 2017-05-11 16:53:33,061 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1483. 2017-05-11 16:53:33,166 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: L'hôte default-host s'arrête
  1484. 2017-05-11 16:53:33,209 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1485. 2017-05-11 16:53:33,247 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1486. 2017-05-11 16:53:33,449 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1487. 2017-05-11 16:53:33,469 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  1488. 2017-05-11 16:53:33,518 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1489. 2017-05-11 16:53:33,520 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  1490. 2017-05-11 16:53:33,521 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1491. 2017-05-11 16:53:33,584 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 599ms
  1492. 2017-05-11 16:53:33,587 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 606ms
  1493. 2017-05-11 16:53:34,345 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1361ms
  1494. 2017-05-11 16:53:34,350 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 1368ms
  1495. 2017-05-11 16:54:53,131 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1496. 2017-05-11 16:54:53,430 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1497. 2017-05-11 16:54:53,525 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  1498. 2017-05-11 16:54:53,527 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Propriétés de système configurées :
  1499. awt.toolkit = sun.awt.windows.WToolkit
  1500. file.encoding = Cp1252
  1501. file.encoding.pkg = sun.io
  1502. file.separator = \
  1503. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1504. java.awt.headless = true
  1505. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1506. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1507. java.class.version = 52.0
  1508. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1509. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1510. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1511. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1512. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  1513. java.net.preferIPv4Stack = true
  1514. java.runtime.name = Java(TM) SE Runtime Environment
  1515. java.runtime.version = 1.8.0_121-b13
  1516. java.specification.name = Java Platform API Specification
  1517. java.specification.vendor = Oracle Corporation
  1518. java.specification.version = 1.8
  1519. java.util.logging.manager = org.jboss.logmanager.LogManager
  1520. java.vendor = Oracle Corporation
  1521. java.vendor.url = http://java.oracle.com/
  1522. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1523. java.version = 1.8.0_121
  1524. java.vm.info = mixed mode
  1525. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1526. java.vm.specification.name = Java Virtual Machine Specification
  1527. java.vm.specification.vendor = Oracle Corporation
  1528. java.vm.specification.version = 1.8
  1529. java.vm.vendor = Oracle Corporation
  1530. java.vm.version = 25.121-b13
  1531. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1532. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1533. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1534. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1535. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1536. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1537. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1538. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1539. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1540. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1541. jboss.bind.address = localhost
  1542. jboss.bind.address.management = localhost
  1543. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1544. jboss.host.name = l82564
  1545. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1546. jboss.modules.system.pkgs = org.jboss.byteman
  1547. jboss.node.name = l82564
  1548. jboss.qualified.host.name = l82564
  1549. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1550. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1551. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1552. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1553. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1554. jboss.server.name = l82564
  1555. jboss.server.persist.config = true
  1556. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1557. line.separator =
  1558.  
  1559. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1560. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1561. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1562. org.jboss.logmanager.nocolor = true
  1563. org.jboss.resolver.warning = true
  1564. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1565. os.arch = amd64
  1566. os.name = Windows 7
  1567. os.version = 6.1
  1568. path.separator = ;
  1569. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1570. sun.arch.data.model = 64
  1571. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  1572. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1573. sun.cpu.endian = little
  1574. sun.cpu.isalist = amd64
  1575. sun.desktop = windows
  1576. sun.io.unicode.encoding = UnicodeLittle
  1577. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1578. sun.java.launcher = SUN_STANDARD
  1579. sun.jnu.encoding = Cp1252
  1580. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1581. sun.os.patch.level = Service Pack 1
  1582. sun.rmi.dgc.client.gcInterval = 3600000
  1583. sun.rmi.dgc.server.gcInterval = 3600000
  1584. user.country = FR
  1585. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1586. user.home = C:\Utilisateurs\A665340
  1587. user.language = fr
  1588. user.name = A665340
  1589. user.script =
  1590. user.timezone = Europe/Paris
  1591. user.variant =
  1592. 2017-05-11 16:54:53,528 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  1593. 2017-05-11 16:54:55,495 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 13) 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é.
  1594. 2017-05-11 16:54:55,815 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1595. 2017-05-11 16:54:55,832 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.3.6.Final-redhat-1
  1596. 2017-05-11 16:54:55,838 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1597. 2017-05-11 16:54:55,909 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)
  1598. 2017-05-11 16:54:55,933 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
  1599. 2017-05-11 16:54:55,936 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1600. 2017-05-11 16:54:55,940 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.
  1601. 2017-05-11 16:54:55,945 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1602. 2017-05-11 16:54:55,946 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1603. 2017-05-11 16:54:55,948 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1604. 2017-05-11 16:54:56,014 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1605. 2017-05-11 16:54:56,113 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1606. 2017-05-11 16:54:56,144 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  1607. 2017-05-11 16:54:56,145 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1608. 2017-05-11 16:54:56,151 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1609. 2017-05-11 16:54:56,198 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  1610. 2017-05-11 16:54:56,316 INFO [org.jboss.as.naming] (MSC service thread 1-5) WFLYNAM0003: Démarrage du service de nommage
  1611. 2017-05-11 16:54:56,409 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1612. 2017-05-11 16:54:56,498 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: '[]']
  1613. 2017-05-11 16:54:56,617 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
  1614. 2017-05-11 16:54:56,622 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  1615. 2017-05-11 16:54:57,069 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: A démarré le serveur default-server.
  1616. 2017-05-11 16:54:57,087 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: L'hôte default-host démarre
  1617. 2017-05-11 16:54:57,122 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.18.Final-redhat-1
  1618. 2017-05-11 16:54:57,337 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1619. 2017-05-11 16:54:57,481 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
  1620. 2017-05-11 16:54:57,493 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1621. 2017-05-11 16:54:57,496 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1622. 2017-05-11 16:54:57,499 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1623. 2017-05-11 16:54:57,499 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1624. 2017-05-11 16:54:57,740 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1625. 2017-05-11 16:54:57,859 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1626. 2017-05-11 16:54:58,341 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  1627. 2017-05-11 16:55:00,040 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1628. 2017-05-11 16:55:00,044 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1629. 2017-05-11 16:55:00,628 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1630. 2017-05-11 16:55:01,364 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1631. 2017-05-11 16:55:01,522 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.3.3 (redhat)
  1632. 2017-05-11 16:55:01,739 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1633. 2017-05-11 16:55:02,323 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1634. 2017-05-11 16:55:02,522 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1635. 2017-05-11 16:55:06,589 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1636. 2017-05-11 16:55:06,590 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1637. 2017-05-11 16:55:06,593 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1638. 2017-05-11 16:55:06,614 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1639. 2017-05-11 16:55:06,944 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1640. 2017-05-11 16:55:06,952 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"
  1641. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1642. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1643. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1644. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1645. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1646. at java.lang.Thread.run(Thread.java:745)
  1647. 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
  1648. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1649. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1650. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1651. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1652. ... 5 more
  1653.  
  1654. 2017-05-11 16:55:07,109 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1655. 2017-05-11 16:55:07,146 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1656. 2017-05-11 16:55:07,949 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1657. 2017-05-11 16:55:08,576 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.
  1658. 2017-05-11 16:55:08,577 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.
  1659. 2017-05-11 16:55:08,577 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.
  1660. 2017-05-11 16:55:08,578 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.
  1661. 2017-05-11 16:55:08,578 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.
  1662. 2017-05-11 16:55:08,578 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.
  1663. 2017-05-11 16:55:08,579 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.
  1664. 2017-05-11 16:55:08,601 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.
  1665. 2017-05-11 16:55:08,613 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.
  1666. 2017-05-11 16:55:08,653 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.
  1667. 2017-05-11 16:55:08,653 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.
  1668. 2017-05-11 16:55:08,654 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.
  1669. 2017-05-11 16:55:08,713 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1670. 2017-05-11 16:55:08,715 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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"
  1671. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1672. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1673. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1674. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1675. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1676. at java.lang.Thread.run(Thread.java:745)
  1677. 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
  1678. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1679. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1680. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1681. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1682. ... 5 more
  1683.  
  1684. 2017-05-11 16:55:08,717 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\"
  1685. 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"}}
  1686. 2017-05-11 16:55:08,718 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\"
  1687. 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"}}
  1688. 2017-05-11 16:55:08,758 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1689. 2017-05-11 16:55:08,758 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1690. 2017-05-11 16:55:08,759 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1691. 2017-05-11 16:55:08,759 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1692. 2017-05-11 16:55:08,767 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  1693. 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"
  1694. 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"
  1695.  
  1696. 2017-05-11 16:55:08,966 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1697. 2017-05-11 16:55:08,967 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1698. 2017-05-11 16:55:08,967 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 16247ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  1699. 2017-05-11 16:55:10,284 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 1072ms
  1700. 2017-05-11 16:55:11,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 2046ms
  1701. 2017-05-11 16:55:11,330 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1702. 2017-05-11 16:55:11,331 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1703. 2017-05-11 16:55:11,332 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  1704. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  1705. service jboss.deployment.unit."xa-cms-admin.war".PARSE
  1706.  
  1707. 2017-05-11 16:57:04,069 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")
  1708. 2017-05-11 16:57:04,070 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")
  1709. 2017-05-11 16:57:08,637 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.
  1710. 2017-05-11 16:57:08,639 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.
  1711. 2017-05-11 16:57:08,640 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.
  1712. 2017-05-11 16:57:08,660 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.
  1713. 2017-05-11 16:57:08,736 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1714. 2017-05-11 16:57:08,738 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"
  1715. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1716. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1717. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1718. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1719. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1720. at java.lang.Thread.run(Thread.java:745)
  1721. 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
  1722. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1723. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1724. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1725. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1726. ... 5 more
  1727.  
  1728. 2017-05-11 16:57:11,336 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.
  1729. 2017-05-11 16:57:11,337 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.
  1730. 2017-05-11 16:57:11,337 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.
  1731. 2017-05-11 16:57:11,338 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.
  1732. 2017-05-11 16:57:11,338 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.
  1733. 2017-05-11 16:57:11,338 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.
  1734. 2017-05-11 16:57:11,339 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.
  1735. 2017-05-11 16:57:11,355 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.
  1736. 2017-05-11 16:57:11,367 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.
  1737. 2017-05-11 16:57:11,392 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.
  1738. 2017-05-11 16:57:11,392 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.
  1739. 2017-05-11 16:57:11,393 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.
  1740. 2017-05-11 16:57:11,478 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1741. 2017-05-11 16:57:11,481 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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"
  1742. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1743. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1744. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1745. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1746. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1747. at java.lang.Thread.run(Thread.java:745)
  1748. 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
  1749. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1750. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1751. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1752. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1753. ... 5 more
  1754.  
  1755. 2017-05-11 16:57:11,482 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) 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\"
  1756. 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"}}
  1757. 2017-05-11 16:57:11,482 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) 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\"
  1758. 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"}}
  1759. 2017-05-11 16:57:11,530 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1760. 2017-05-11 16:57:11,530 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1761. 2017-05-11 16:57:11,530 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1762. 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"
  1763. 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"
  1764.  
  1765. 2017-05-11 16:57:38,691 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1027ms
  1766. 2017-05-11 16:57:38,692 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")
  1767. 2017-05-11 16:57:38,694 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".STRUCTURE: WFLYSRV0153: N'a pas pu traiter la phase STRUCTURE de deployment "xa-cms-wli.war"
  1768. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1769. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1770. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1771. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1772. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1773. at java.lang.Thread.run(Thread.java:745)
  1774. Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: N'a pas pu monter le contenu du déploiement
  1775. at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:95)
  1776. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1777. ... 5 more
  1778. Caused by: java.io.FileNotFoundException: C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments\xa-cms-wli.war (Le fichier spécifié est introuvable)
  1779. at java.io.FileInputStream.open0(Native Method)
  1780. at java.io.FileInputStream.open(FileInputStream.java:195)
  1781. at java.io.FileInputStream.<init>(FileInputStream.java:138)
  1782. at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:51)
  1783. at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:259)
  1784. at org.jboss.vfs.VFS.mountZipExpanded(VFS.java:533)
  1785. at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:108)
  1786. at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:91)
  1787. ... 6 more
  1788.  
  1789. 2017-05-11 16:57:38,696 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\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".STRUCTURE: WFLYSRV0153: N'a pas pu traiter la phase STRUCTURE de deployment \"xa-cms-wli.war\"
  1790. Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: N'a pas pu monter le contenu du déploiement
  1791. Caused by: java.io.FileNotFoundException: C:\\Utilisateurs\\A665340\\jboss_eap\\jboss-eap-7.0\\standalone\\deployments\\xa-cms-wli.war (Le fichier spécifié est introuvable)"}}
  1792. 2017-05-11 16:57:38,758 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"
  1793. 2017-05-11 16:57:38,758 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1794. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  1795. 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"
  1796. service jboss.deployment.unit."xa-cms-wli.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".STRUCTURE: WFLYSRV0153: N'a pas pu traiter la phase STRUCTURE de deployment "xa-cms-wli.war"
  1797.  
  1798. 2017-05-11 16:57:47,686 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1799. 2017-05-11 16:57:47,703 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1800. 2017-05-11 16:57:47,763 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 45ms
  1801. 2017-05-11 16:57:47,821 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1802. 2017-05-11 16:57:47,832 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1803. 2017-05-11 16:57:48,028 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1804. 2017-05-11 16:57:48,041 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: L'hôte default-host s'arrête
  1805. 2017-05-11 16:57:48,197 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1806. 2017-05-11 16:57:48,256 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1807. 2017-05-11 16:57:48,295 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  1808. 2017-05-11 16:57:48,327 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1809. 2017-05-11 16:57:48,339 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  1810. 2017-05-11 16:57:48,340 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1811. 2017-05-11 16:57:48,370 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 659ms
  1812. 2017-05-11 16:57:48,385 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 667ms
  1813. 2017-05-11 16:57:48,715 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 1003ms
  1814. 2017-05-11 16:57:48,721 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 1007ms
  1815. 2017-05-11 17:00:00,491 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1816. 2017-05-11 17:00:00,811 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1817. 2017-05-11 17:00:00,916 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  1818. 2017-05-11 17:00:00,917 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  1819. awt.toolkit = sun.awt.windows.WToolkit
  1820. file.encoding = Cp1252
  1821. file.encoding.pkg = sun.io
  1822. file.separator = \
  1823. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1824. java.awt.headless = true
  1825. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1826. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1827. java.class.version = 52.0
  1828. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1829. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1830. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1831. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1832. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  1833. java.net.preferIPv4Stack = true
  1834. java.runtime.name = Java(TM) SE Runtime Environment
  1835. java.runtime.version = 1.8.0_121-b13
  1836. java.specification.name = Java Platform API Specification
  1837. java.specification.vendor = Oracle Corporation
  1838. java.specification.version = 1.8
  1839. java.util.logging.manager = org.jboss.logmanager.LogManager
  1840. java.vendor = Oracle Corporation
  1841. java.vendor.url = http://java.oracle.com/
  1842. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1843. java.version = 1.8.0_121
  1844. java.vm.info = mixed mode
  1845. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1846. java.vm.specification.name = Java Virtual Machine Specification
  1847. java.vm.specification.vendor = Oracle Corporation
  1848. java.vm.specification.version = 1.8
  1849. java.vm.vendor = Oracle Corporation
  1850. java.vm.version = 25.121-b13
  1851. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1852. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1853. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1854. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1855. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1856. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1857. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1858. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1859. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1860. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1861. jboss.bind.address = localhost
  1862. jboss.bind.address.management = localhost
  1863. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1864. jboss.host.name = l82564
  1865. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1866. jboss.modules.system.pkgs = org.jboss.byteman
  1867. jboss.node.name = l82564
  1868. jboss.qualified.host.name = l82564
  1869. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1870. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1871. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1872. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1873. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1874. jboss.server.name = l82564
  1875. jboss.server.persist.config = true
  1876. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1877. line.separator =
  1878.  
  1879. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1880. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1881. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1882. org.jboss.logmanager.nocolor = true
  1883. org.jboss.resolver.warning = true
  1884. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1885. os.arch = amd64
  1886. os.name = Windows 7
  1887. os.version = 6.1
  1888. path.separator = ;
  1889. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1890. sun.arch.data.model = 64
  1891. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  1892. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1893. sun.cpu.endian = little
  1894. sun.cpu.isalist = amd64
  1895. sun.desktop = windows
  1896. sun.io.unicode.encoding = UnicodeLittle
  1897. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1898. sun.java.launcher = SUN_STANDARD
  1899. sun.jnu.encoding = Cp1252
  1900. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1901. sun.os.patch.level = Service Pack 1
  1902. sun.rmi.dgc.client.gcInterval = 3600000
  1903. sun.rmi.dgc.server.gcInterval = 3600000
  1904. user.country = FR
  1905. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1906. user.home = C:\Utilisateurs\A665340
  1907. user.language = fr
  1908. user.name = A665340
  1909. user.script =
  1910. user.timezone = Europe/Paris
  1911. user.variant =
  1912. 2017-05-11 17:00:00,918 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  1913. 2017-05-11 17:00:02,967 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 16) 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é.
  1914. 2017-05-11 17:00:03,329 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1915. 2017-05-11 17:00:03,346 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.6.Final-redhat-1
  1916. 2017-05-11 17:00:03,353 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1917. 2017-05-11 17:00:03,413 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1918. 2017-05-11 17:00:03,438 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1919. 2017-05-11 17:00:03,440 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1920. 2017-05-11 17:00:03,443 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.
  1921. 2017-05-11 17:00:03,449 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1922. 2017-05-11 17:00:03,484 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1923. 2017-05-11 17:00:03,486 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1924. 2017-05-11 17:00:03,492 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1925. 2017-05-11 17:00:03,518 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1926. 2017-05-11 17:00:03,528 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
  1927. 2017-05-11 17:00:03,647 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  1928. 2017-05-11 17:00:03,693 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)
  1929. 2017-05-11 17:00:03,710 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  1930. 2017-05-11 17:00:03,744 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Démarrage du service de nommage
  1931. 2017-05-11 17:00:03,745 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1932. 2017-05-11 17:00:03,905 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: '[]']
  1933. 2017-05-11 17:00:04,076 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
  1934. 2017-05-11 17:00:04,081 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) 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.
  1935. 2017-05-11 17:00:04,432 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final-redhat-1
  1936. 2017-05-11 17:00:04,476 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: A démarré le serveur default-server.
  1937. 2017-05-11 17:00:04,502 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: L'hôte default-host démarre
  1938. 2017-05-11 17:00:04,675 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1939. 2017-05-11 17:00:05,287 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
  1940. 2017-05-11 17:00:05,330 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")
  1941. 2017-05-11 17:00:05,348 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1942. 2017-05-11 17:00:05,363 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")
  1943. 2017-05-11 17:00:05,380 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1944. 2017-05-11 17:00:05,543 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1945. 2017-05-11 17:00:05,582 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1946. 2017-05-11 17:00:05,876 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)
  1947. 2017-05-11 17:00:06,943 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1948. 2017-05-11 17:00:07,019 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1949. 2017-05-11 17:00:07,046 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1950. 2017-05-11 17:00:07,592 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1951. 2017-05-11 17:00:07,601 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1952. 2017-05-11 17:00:07,639 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.3 (redhat)
  1953. 2017-05-11 17:00:07,679 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1954. 2017-05-11 17:00:07,680 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1955. 2017-05-11 17:00:10,040 INFO [org.jboss.as.protocol] (management I/O-2) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 3,5,management-handler-thread]
  1956. 2017-05-11 17:00:12,512 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1957. 2017-05-11 17:00:13,350 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.
  1958. 2017-05-11 17:00:13,351 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.
  1959. 2017-05-11 17:00:13,354 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.
  1960. 2017-05-11 17:00:13,376 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.
  1961. 2017-05-11 17:00:13,402 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 58) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1962. 2017-05-11 17:00:13,583 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1963. 2017-05-11 17:00:13,587 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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"
  1964. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1965. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1966. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1967. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1968. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1969. at java.lang.Thread.run(Thread.java:745)
  1970. 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
  1971. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1972. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1973. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1974. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1975. ... 5 more
  1976.  
  1977. 2017-05-11 17:00:14,311 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1978. 2017-05-11 17:00:16,144 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1979. 2017-05-11 17:00:16,145 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1980. 2017-05-11 17:00:16,146 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1981. 2017-05-11 17:00:16,146 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1982. 2017-05-11 17:00:16,147 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1983. 2017-05-11 17:00:16,147 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1984. 2017-05-11 17:00:16,147 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1985. 2017-05-11 17:00:16,164 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1986. 2017-05-11 17:00:16,176 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1987. 2017-05-11 17:00:16,201 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1988. 2017-05-11 17:00:16,202 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1989. 2017-05-11 17:00:16,202 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) 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.
  1990. 2017-05-11 17:00:16,260 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1991. 2017-05-11 17:00:16,263 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) 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"
  1992. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1993. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1994. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1995. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1996. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1997. at java.lang.Thread.run(Thread.java:745)
  1998. 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
  1999. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2000. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2001. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2002. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2003. ... 5 more
  2004.  
  2005. 2017-05-11 17:00:16,265 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\"
  2006. 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"}}
  2007. 2017-05-11 17:00:16,267 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\"
  2008. 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"}}
  2009. 2017-05-11 17:00:16,302 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2010. 2017-05-11 17:00:16,302 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2011. 2017-05-11 17:00:16,327 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  2012. 2017-05-11 17:00:16,329 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2013. 2017-05-11 17:00:16,336 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  2014. 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"
  2015. 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"
  2016.  
  2017. 2017-05-11 17:00:16,513 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  2018. 2017-05-11 17:00:16,514 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  2019. 2017-05-11 17:00:16,514 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 16518ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  2020. 2017-05-11 17:00:17,694 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 826ms
  2021. 2017-05-11 17:00:18,008 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 1137ms
  2022. 2017-05-11 17:00:18,080 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  2023. 2017-05-11 17:00:18,081 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2024. 2017-05-11 17:00:18,081 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  2025. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  2026. service jboss.deployment.unit."xa-cms-wli.war".PARSE
  2027.  
  2028. 2017-05-11 17:00:53,757 INFO [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0236: Suspending server with no timeout.
  2029. 2017-05-11 17:00:53,838 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2030. 2017-05-11 17:00:53,951 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  2031. 2017-05-11 17:00:53,954 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  2032. 2017-05-11 17:00:54,083 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  2033. 2017-05-11 17:00:54,083 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: L'hôte default-host s'arrête
  2034. 2017-05-11 17:00:54,124 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  2035. 2017-05-11 17:00:54,193 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  2036. 2017-05-11 17:00:54,200 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  2037. 2017-05-11 17:00:54,239 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  2038. 2017-05-11 17:00:54,241 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  2039. 2017-05-11 17:00:54,242 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  2040. 2017-05-11 17:00:54,353 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 492ms
  2041. 2017-05-11 17:00:54,388 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 542ms
  2042. 2017-05-11 17:00:54,395 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 506ms
  2043. 2017-05-11 17:02:48,829 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2044. 2017-05-11 17:02:49,129 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2045. 2017-05-11 17:02:49,217 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  2046. 2017-05-11 17:02:49,219 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2047. awt.toolkit = sun.awt.windows.WToolkit
  2048. file.encoding = Cp1252
  2049. file.encoding.pkg = sun.io
  2050. file.separator = \
  2051. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2052. java.awt.headless = true
  2053. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2054. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2055. java.class.version = 52.0
  2056. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2057. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2058. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2059. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2060. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2061. java.net.preferIPv4Stack = true
  2062. java.runtime.name = Java(TM) SE Runtime Environment
  2063. java.runtime.version = 1.8.0_121-b13
  2064. java.specification.name = Java Platform API Specification
  2065. java.specification.vendor = Oracle Corporation
  2066. java.specification.version = 1.8
  2067. java.util.logging.manager = org.jboss.logmanager.LogManager
  2068. java.vendor = Oracle Corporation
  2069. java.vendor.url = http://java.oracle.com/
  2070. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2071. java.version = 1.8.0_121
  2072. java.vm.info = mixed mode
  2073. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2074. java.vm.specification.name = Java Virtual Machine Specification
  2075. java.vm.specification.vendor = Oracle Corporation
  2076. java.vm.specification.version = 1.8
  2077. java.vm.vendor = Oracle Corporation
  2078. java.vm.version = 25.121-b13
  2079. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2080. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2081. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2082. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2083. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2084. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2085. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2086. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2087. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2088. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2089. jboss.bind.address = localhost
  2090. jboss.bind.address.management = localhost
  2091. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2092. jboss.host.name = l82564
  2093. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2094. jboss.modules.system.pkgs = org.jboss.byteman
  2095. jboss.node.name = l82564
  2096. jboss.qualified.host.name = l82564
  2097. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2098. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2099. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2100. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2101. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2102. jboss.server.name = l82564
  2103. jboss.server.persist.config = true
  2104. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2105. line.separator =
  2106.  
  2107. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2108. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2109. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2110. org.jboss.logmanager.nocolor = true
  2111. org.jboss.resolver.warning = true
  2112. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2113. os.arch = amd64
  2114. os.name = Windows 7
  2115. os.version = 6.1
  2116. path.separator = ;
  2117. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2118. sun.arch.data.model = 64
  2119. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2120. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2121. sun.cpu.endian = little
  2122. sun.cpu.isalist = amd64
  2123. sun.desktop = windows
  2124. sun.io.unicode.encoding = UnicodeLittle
  2125. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2126. sun.java.launcher = SUN_STANDARD
  2127. sun.jnu.encoding = Cp1252
  2128. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2129. sun.os.patch.level = Service Pack 1
  2130. sun.rmi.dgc.client.gcInterval = 3600000
  2131. sun.rmi.dgc.server.gcInterval = 3600000
  2132. user.country = FR
  2133. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2134. user.home = C:\Utilisateurs\A665340
  2135. user.language = fr
  2136. user.name = A665340
  2137. user.script =
  2138. user.timezone = Europe/Paris
  2139. user.variant =
  2140. 2017-05-11 17:02:49,220 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2141. 2017-05-11 17:02:51,314 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 22) 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é.
  2142. 2017-05-11 17:02:51,387 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  2143. 2017-05-11 17:02:51,437 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  2144. 2017-05-11 17:02:51,457 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  2145. 2017-05-11 17:02:51,577 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)
  2146. 2017-05-11 17:02:51,616 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  2147. 2017-05-11 17:02:51,625 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.
  2148. 2017-05-11 17:02:51,648 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  2149. 2017-05-11 17:02:51,650 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  2150. 2017-05-11 17:02:51,654 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  2151. 2017-05-11 17:02:51,663 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
  2152. 2017-05-11 17:02:51,816 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  2153. 2017-05-11 17:02:51,841 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2154. 2017-05-11 17:02:51,843 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2155. 2017-05-11 17:02:51,847 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  2156. 2017-05-11 17:02:51,862 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  2157. 2017-05-11 17:02:51,864 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  2158. 2017-05-11 17:02:51,977 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Démarrage du service de nommage
  2159. 2017-05-11 17:02:51,978 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  2160. 2017-05-11 17:02:52,286 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  2161. 2017-05-11 17:02:52,286 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
  2162. 2017-05-11 17:02:52,317 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: '[]']
  2163. 2017-05-11 17:02:52,577 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: A démarré le serveur default-server.
  2164. 2017-05-11 17:02:52,579 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: L'hôte default-host démarre
  2165. 2017-05-11 17:02:52,610 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final-redhat-1
  2166. 2017-05-11 17:02:52,665 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  2167. 2017-05-11 17:02:53,061 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  2168. 2017-05-11 17:02:53,070 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2169. 2017-05-11 17:02:53,074 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2170. 2017-05-11 17:02:53,548 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  2171. 2017-05-11 17:02:53,691 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  2172. 2017-05-11 17:02:53,799 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  2173. 2017-05-11 17:02:54,759 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  2174. 2017-05-11 17:02:54,759 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  2175. 2017-05-11 17:02:54,840 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-5) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  2176. 2017-05-11 17:02:55,209 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  2177. 2017-05-11 17:02:55,209 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  2178. 2017-05-11 17:02:55,246 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.3 (redhat)
  2179. 2017-05-11 17:02:55,280 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  2180. 2017-05-11 17:02:55,280 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  2181. 2017-05-11 17:02:56,602 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 63) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  2182. 2017-05-11 17:02:56,623 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  2183. 2017-05-11 17:02:57,114 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  2184. 2017-05-11 17:02:57,144 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2185. 2017-05-11 17:02:57,145 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2186. 2017-05-11 17:02:57,331 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  2187. 2017-05-11 17:02:57,332 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  2188. 2017-05-11 17:02:57,333 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 8916ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  2189. 2017-05-11 17:05:54,359 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  2190. 2017-05-11 17:05:54,384 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2191. 2017-05-11 17:05:54,484 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  2192. 2017-05-11 17:05:54,510 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 70) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  2193. 2017-05-11 17:05:54,548 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: L'hôte default-host s'arrête
  2194. 2017-05-11 17:05:54,552 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  2195. 2017-05-11 17:05:54,558 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  2196. 2017-05-11 17:05:54,587 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  2197. 2017-05-11 17:05:54,591 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  2198. 2017-05-11 17:05:54,625 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  2199. 2017-05-11 17:05:54,628 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  2200. 2017-05-11 17:05:54,629 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  2201. 2017-05-11 17:05:54,674 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 248ms
  2202. 2017-05-11 17:05:54,694 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 264ms
  2203. 2017-05-11 17:05:54,710 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 281ms
  2204. 2017-05-11 17:05:56,830 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2205. 2017-05-11 17:05:57,126 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2206. 2017-05-11 17:05:57,215 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  2207. 2017-05-11 17:05:57,217 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2208. awt.toolkit = sun.awt.windows.WToolkit
  2209. file.encoding = Cp1252
  2210. file.encoding.pkg = sun.io
  2211. file.separator = \
  2212. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2213. java.awt.headless = true
  2214. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2215. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2216. java.class.version = 52.0
  2217. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2218. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2219. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2220. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2221. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2222. java.net.preferIPv4Stack = true
  2223. java.runtime.name = Java(TM) SE Runtime Environment
  2224. java.runtime.version = 1.8.0_121-b13
  2225. java.specification.name = Java Platform API Specification
  2226. java.specification.vendor = Oracle Corporation
  2227. java.specification.version = 1.8
  2228. java.util.logging.manager = org.jboss.logmanager.LogManager
  2229. java.vendor = Oracle Corporation
  2230. java.vendor.url = http://java.oracle.com/
  2231. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2232. java.version = 1.8.0_121
  2233. java.vm.info = mixed mode
  2234. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2235. java.vm.specification.name = Java Virtual Machine Specification
  2236. java.vm.specification.vendor = Oracle Corporation
  2237. java.vm.specification.version = 1.8
  2238. java.vm.vendor = Oracle Corporation
  2239. java.vm.version = 25.121-b13
  2240. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2241. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2242. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2243. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2244. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2245. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2246. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2247. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2248. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2249. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2250. jboss.bind.address = localhost
  2251. jboss.bind.address.management = localhost
  2252. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2253. jboss.host.name = l82564
  2254. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2255. jboss.modules.system.pkgs = org.jboss.byteman
  2256. jboss.node.name = l82564
  2257. jboss.qualified.host.name = l82564
  2258. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2259. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2260. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2261. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2262. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2263. jboss.server.name = l82564
  2264. jboss.server.persist.config = true
  2265. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2266. line.separator =
  2267.  
  2268. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2269. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2270. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2271. org.jboss.logmanager.nocolor = true
  2272. org.jboss.resolver.warning = true
  2273. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2274. os.arch = amd64
  2275. os.name = Windows 7
  2276. os.version = 6.1
  2277. path.separator = ;
  2278. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2279. sun.arch.data.model = 64
  2280. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2281. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2282. sun.cpu.endian = little
  2283. sun.cpu.isalist = amd64
  2284. sun.desktop = windows
  2285. sun.io.unicode.encoding = UnicodeLittle
  2286. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2287. sun.java.launcher = SUN_STANDARD
  2288. sun.jnu.encoding = Cp1252
  2289. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2290. sun.os.patch.level = Service Pack 1
  2291. sun.rmi.dgc.client.gcInterval = 3600000
  2292. sun.rmi.dgc.server.gcInterval = 3600000
  2293. user.country = FR
  2294. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2295. user.home = C:\Utilisateurs\A665340
  2296. user.language = fr
  2297. user.name = A665340
  2298. user.script =
  2299. user.timezone = Europe/Paris
  2300. user.variant =
  2301. 2017-05-11 17:05:57,218 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2302. 2017-05-11 17:05:59,106 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 27) 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é.
  2303. 2017-05-11 17:05:59,169 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  2304. 2017-05-11 17:05:59,191 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
  2305. 2017-05-11 17:05:59,200 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  2306. 2017-05-11 17:05:59,254 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.
  2307. 2017-05-11 17:05:59,265 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  2308. 2017-05-11 17:05:59,290 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  2309. 2017-05-11 17:05:59,355 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  2310. 2017-05-11 17:05:59,471 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  2311. 2017-05-11 17:05:59,471 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  2312. 2017-05-11 17:05:59,474 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
  2313. 2017-05-11 17:05:59,484 INFO [org.jboss.as.connector] (MSC service thread 1-8) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  2314. 2017-05-11 17:05:59,559 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2315. 2017-05-11 17:05:59,560 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2316. 2017-05-11 17:05:59,571 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)
  2317. 2017-05-11 17:05:59,581 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  2318. 2017-05-11 17:05:59,604 INFO [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  2319. 2017-05-11 17:05:59,650 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Démarrage du service de nommage
  2320. 2017-05-11 17:05:59,650 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  2321. 2017-05-11 17:05:59,815 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  2322. 2017-05-11 17:05:59,816 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.
  2323. 2017-05-11 17:05:59,995 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: '[]']
  2324. 2017-05-11 17:06:00,352 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.18.Final-redhat-1
  2325. 2017-05-11 17:06:00,366 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: A démarré le serveur default-server.
  2326. 2017-05-11 17:06:00,390 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: L'hôte default-host démarre
  2327. 2017-05-11 17:06:00,451 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  2328. 2017-05-11 17:06:00,788 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  2329. 2017-05-11 17:06:00,821 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2330. 2017-05-11 17:06:00,823 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2331. 2017-05-11 17:06:01,181 INFO [org.jboss.ws.common.management] (MSC service thread 1-8) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  2332. 2017-05-11 17:06:01,567 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  2333. 2017-05-11 17:06:01,776 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  2334. 2017-05-11 17:06:02,323 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  2335. 2017-05-11 17:06:02,439 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  2336. 2017-05-11 17:06:02,497 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  2337. 2017-05-11 17:06:02,854 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  2338. 2017-05-11 17:06:02,924 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.3.3 (redhat)
  2339. 2017-05-11 17:06:02,979 INFO [org.jboss.as.protocol] (management task-9) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 2,5,management-handler-thread]
  2340. 2017-05-11 17:06:03,045 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  2341. 2017-05-11 17:06:03,047 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  2342. 2017-05-11 17:06:03,057 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  2343. 2017-05-11 17:06:04,309 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  2344. 2017-05-11 17:06:04,325 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  2345. 2017-05-11 17:06:04,910 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  2346. 2017-05-11 17:06:04,954 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2347. 2017-05-11 17:06:04,954 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2348. 2017-05-11 17:06:05,130 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  2349. 2017-05-11 17:06:05,131 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  2350. 2017-05-11 17:06:05,131 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 8809ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  2351. 2017-05-11 17:06:23,549 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0236: Suspending server with no timeout.
  2352. 2017-05-11 17:06:23,574 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2353. 2017-05-11 17:06:23,642 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  2354. 2017-05-11 17:06:23,648 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 20) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  2355. 2017-05-11 17:06:23,662 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: L'hôte default-host s'arrête
  2356. 2017-05-11 17:06:23,670 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  2357. 2017-05-11 17:06:23,678 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  2358. 2017-05-11 17:06:23,752 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  2359. 2017-05-11 17:06:23,772 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  2360. 2017-05-11 17:06:23,816 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  2361. 2017-05-11 17:06:23,817 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  2362. 2017-05-11 17:06:23,820 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  2363. 2017-05-11 17:06:23,877 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 292ms
  2364. 2017-05-11 17:06:23,882 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 286ms
  2365. 2017-05-11 17:06:23,906 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 319ms
  2366. 2017-05-11 17:08:51,711 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2367. 2017-05-11 17:08:52,035 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2368. 2017-05-11 17:08:52,122 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  2369. 2017-05-11 17:08:52,123 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2370. awt.toolkit = sun.awt.windows.WToolkit
  2371. file.encoding = Cp1252
  2372. file.encoding.pkg = sun.io
  2373. file.separator = \
  2374. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2375. java.awt.headless = true
  2376. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2377. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2378. java.class.version = 52.0
  2379. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2380. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2381. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2382. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2383. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2384. java.net.preferIPv4Stack = true
  2385. java.runtime.name = Java(TM) SE Runtime Environment
  2386. java.runtime.version = 1.8.0_121-b13
  2387. java.specification.name = Java Platform API Specification
  2388. java.specification.vendor = Oracle Corporation
  2389. java.specification.version = 1.8
  2390. java.util.logging.manager = org.jboss.logmanager.LogManager
  2391. java.vendor = Oracle Corporation
  2392. java.vendor.url = http://java.oracle.com/
  2393. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2394. java.version = 1.8.0_121
  2395. java.vm.info = mixed mode
  2396. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2397. java.vm.specification.name = Java Virtual Machine Specification
  2398. java.vm.specification.vendor = Oracle Corporation
  2399. java.vm.specification.version = 1.8
  2400. java.vm.vendor = Oracle Corporation
  2401. java.vm.version = 25.121-b13
  2402. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2403. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2404. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2405. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2406. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2407. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2408. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2409. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2410. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2411. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2412. jboss.bind.address = localhost
  2413. jboss.bind.address.management = localhost
  2414. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2415. jboss.host.name = l82564
  2416. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2417. jboss.modules.system.pkgs = org.jboss.byteman
  2418. jboss.node.name = l82564
  2419. jboss.qualified.host.name = l82564
  2420. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2421. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2422. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2423. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2424. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2425. jboss.server.name = l82564
  2426. jboss.server.persist.config = true
  2427. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2428. line.separator =
  2429.  
  2430. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2431. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2432. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2433. org.jboss.logmanager.nocolor = true
  2434. org.jboss.resolver.warning = true
  2435. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2436. os.arch = amd64
  2437. os.name = Windows 7
  2438. os.version = 6.1
  2439. path.separator = ;
  2440. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2441. sun.arch.data.model = 64
  2442. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2443. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2444. sun.cpu.endian = little
  2445. sun.cpu.isalist = amd64
  2446. sun.desktop = windows
  2447. sun.io.unicode.encoding = UnicodeLittle
  2448. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2449. sun.java.launcher = SUN_STANDARD
  2450. sun.jnu.encoding = Cp1252
  2451. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2452. sun.os.patch.level = Service Pack 1
  2453. sun.rmi.dgc.client.gcInterval = 3600000
  2454. sun.rmi.dgc.server.gcInterval = 3600000
  2455. user.country = FR
  2456. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2457. user.home = C:\Utilisateurs\A665340
  2458. user.language = fr
  2459. user.name = A665340
  2460. user.script =
  2461. user.timezone = Europe/Paris
  2462. user.variant =
  2463. 2017-05-11 17:08:52,124 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2464. 2017-05-11 17:08:54,203 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 25) 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é.
  2465. 2017-05-11 17:08:54,493 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "jboss-helloworld.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"jboss-helloworld.war\")] en double"
  2466. 2017-05-11 17:08:54,499 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  2467. 2017-05-11 17:08:54,503 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2468. 2017-05-11 17:08:54,520 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 9ms
  2469. 2017-05-11 17:09:51,450 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2470. 2017-05-11 17:09:51,792 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2471. 2017-05-11 17:09:51,873 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  2472. 2017-05-11 17:09:51,874 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2473. awt.toolkit = sun.awt.windows.WToolkit
  2474. file.encoding = Cp1252
  2475. file.encoding.pkg = sun.io
  2476. file.separator = \
  2477. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2478. java.awt.headless = true
  2479. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2480. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2481. java.class.version = 52.0
  2482. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2483. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2484. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2485. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2486. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2487. java.net.preferIPv4Stack = true
  2488. java.runtime.name = Java(TM) SE Runtime Environment
  2489. java.runtime.version = 1.8.0_121-b13
  2490. java.specification.name = Java Platform API Specification
  2491. java.specification.vendor = Oracle Corporation
  2492. java.specification.version = 1.8
  2493. java.util.logging.manager = org.jboss.logmanager.LogManager
  2494. java.vendor = Oracle Corporation
  2495. java.vendor.url = http://java.oracle.com/
  2496. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2497. java.version = 1.8.0_121
  2498. java.vm.info = mixed mode
  2499. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2500. java.vm.specification.name = Java Virtual Machine Specification
  2501. java.vm.specification.vendor = Oracle Corporation
  2502. java.vm.specification.version = 1.8
  2503. java.vm.vendor = Oracle Corporation
  2504. java.vm.version = 25.121-b13
  2505. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2506. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2507. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2508. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2509. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2510. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2511. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2512. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2513. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2514. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2515. jboss.bind.address = localhost
  2516. jboss.bind.address.management = localhost
  2517. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2518. jboss.host.name = l82564
  2519. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2520. jboss.modules.system.pkgs = org.jboss.byteman
  2521. jboss.node.name = l82564
  2522. jboss.qualified.host.name = l82564
  2523. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2524. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2525. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2526. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2527. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2528. jboss.server.name = l82564
  2529. jboss.server.persist.config = true
  2530. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2531. line.separator =
  2532.  
  2533. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2534. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2535. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2536. org.jboss.logmanager.nocolor = true
  2537. org.jboss.resolver.warning = true
  2538. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2539. os.arch = amd64
  2540. os.name = Windows 7
  2541. os.version = 6.1
  2542. path.separator = ;
  2543. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2544. sun.arch.data.model = 64
  2545. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2546. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2547. sun.cpu.endian = little
  2548. sun.cpu.isalist = amd64
  2549. sun.desktop = windows
  2550. sun.io.unicode.encoding = UnicodeLittle
  2551. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2552. sun.java.launcher = SUN_STANDARD
  2553. sun.jnu.encoding = Cp1252
  2554. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2555. sun.os.patch.level = Service Pack 1
  2556. sun.rmi.dgc.client.gcInterval = 3600000
  2557. sun.rmi.dgc.server.gcInterval = 3600000
  2558. user.country = FR
  2559. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2560. user.home = C:\Utilisateurs\A665340
  2561. user.language = fr
  2562. user.name = A665340
  2563. user.script =
  2564. user.timezone = Europe/Paris
  2565. user.variant =
  2566. 2017-05-11 17:09:51,875 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2567. 2017-05-11 17:09:53,818 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 22) 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é.
  2568. 2017-05-11 17:09:54,081 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  2569. 2017-05-11 17:09:54,102 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.3.6.Final-redhat-1
  2570. 2017-05-11 17:09:54,110 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  2571. 2017-05-11 17:09:54,176 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  2572. 2017-05-11 17:09:54,188 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  2573. 2017-05-11 17:09:54,192 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.
  2574. 2017-05-11 17:09:54,204 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  2575. 2017-05-11 17:09:54,246 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  2576. 2017-05-11 17:09:54,250 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  2577. 2017-05-11 17:09:54,248 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  2578. 2017-05-11 17:09:54,272 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
  2579. 2017-05-11 17:09:54,341 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  2580. 2017-05-11 17:09:54,343 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)
  2581. 2017-05-11 17:09:54,470 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2582. 2017-05-11 17:09:54,475 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  2583. 2017-05-11 17:09:54,512 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  2584. 2017-05-11 17:09:54,534 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Démarrage du service de nommage
  2585. 2017-05-11 17:09:54,535 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  2586. 2017-05-11 17:09:54,801 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: '[]']
  2587. 2017-05-11 17:09:55,006 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.
  2588. 2017-05-11 17:09:55,009 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.
  2589. 2017-05-11 17:09:55,288 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: A démarré le serveur default-server.
  2590. 2017-05-11 17:09:55,296 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: L'hôte default-host démarre
  2591. 2017-05-11 17:09:55,321 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
  2592. 2017-05-11 17:09:55,421 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  2593. 2017-05-11 17:09:55,607 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  2594. 2017-05-11 17:09:55,630 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2595. 2017-05-11 17:09:55,632 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2596. 2017-05-11 17:09:55,633 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2597. 2017-05-11 17:09:55,634 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")
  2598. 2017-05-11 17:09:56,485 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)
  2599. 2017-05-11 17:09:56,951 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-7) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  2600. 2017-05-11 17:09:57,306 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  2601. 2017-05-11 17:09:58,237 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  2602. 2017-05-11 17:09:58,241 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  2603. 2017-05-11 17:09:58,549 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  2604. 2017-05-11 17:09:58,846 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  2605. 2017-05-11 17:09:58,846 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  2606. 2017-05-11 17:09:58,920 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.3.3 (redhat)
  2607. 2017-05-11 17:09:58,977 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  2608. 2017-05-11 17:09:58,979 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  2609. 2017-05-11 17:10:01,015 INFO [org.jboss.as.protocol] (management I/O-1) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 4,5,management-handler-thread]
  2610. 2017-05-11 17:10:01,015 INFO [org.jboss.as.protocol] (management I/O-2) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 3,5,management-handler-thread]
  2611. 2017-05-11 17:10:03,919 INFO [org.jboss.as.protocol] (management task-9) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 1,5,management-handler-thread]
  2612. 2017-05-11 17:10:05,731 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.
  2613. 2017-05-11 17:10:05,735 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.
  2614. 2017-05-11 17:10:05,736 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.
  2615. 2017-05-11 17:10:05,758 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.
  2616. 2017-05-11 17:10:05,969 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2617. 2017-05-11 17:10:05,976 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"
  2618. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2619. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2620. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2621. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2622. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2623. at java.lang.Thread.run(Thread.java:745)
  2624. 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
  2625. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2626. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2627. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2628. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2629. ... 5 more
  2630.  
  2631. 2017-05-11 17:10:06,806 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 62) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  2632. 2017-05-11 17:10:06,868 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  2633. 2017-05-11 17:10:07,677 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  2634. 2017-05-11 17:10:08,072 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-wli.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2635. 2017-05-11 17:10:08,073 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2636. 2017-05-11 17:10:08,074 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-wli.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2637. 2017-05-11 17:10:08,074 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-wli.war/WEB-INF/lib/jaxb-xjc-2.2.5.1.jar does not point to a valid jar for a Class-Path reference.
  2638. 2017-05-11 17:10:08,075 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2639. 2017-05-11 17:10:08,076 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2640. 2017-05-11 17:10:08,078 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2641. 2017-05-11 17:10:08,102 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-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  2642. 2017-05-11 17:10:08,115 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2643. 2017-05-11 17:10:08,141 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2644. 2017-05-11 17:10:08,141 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2645. 2017-05-11 17:10:08,141 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) 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.
  2646. 2017-05-11 17:10:08,225 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2647. 2017-05-11 17:10:08,228 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) 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"
  2648. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2649. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2650. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2651. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2652. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2653. at java.lang.Thread.run(Thread.java:745)
  2654. 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
  2655. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2656. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2657. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2658. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2659. ... 5 more
  2660.  
  2661. 2017-05-11 17:10:08,231 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\"
  2662. 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"}}
  2663. 2017-05-11 17:10:08,232 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\"
  2664. 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"}}
  2665. 2017-05-11 17:10:08,266 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  2666. 2017-05-11 17:10:08,266 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  2667. 2017-05-11 17:10:08,273 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  2668. 2017-05-11 17:10:08,274 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2669. 2017-05-11 17:10:08,295 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  2670. 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"
  2671. 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"
  2672.  
  2673. 2017-05-11 17:10:08,468 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  2674. 2017-05-11 17:10:08,468 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  2675. 2017-05-11 17:10:08,469 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 17554ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  2676. 2017-05-11 17:10:09,322 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 593ms
  2677. 2017-05-11 17:10:09,624 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 895ms
  2678. 2017-05-11 17:10:09,694 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  2679. 2017-05-11 17:10:09,695 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2680. 2017-05-11 17:10:09,695 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  2681. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  2682. service jboss.deployment.unit."xa-cms-admin.war".PARSE
  2683.  
  2684. 2017-05-11 17:15:16,939 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 67) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\43\9818c59f0cb0831424471e08ae954dcecda58c\content
  2685. 2017-05-11 17:15:16,991 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2686. 2017-05-11 17:15:20,997 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/bin/content/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.
  2687. 2017-05-11 17:15:20,998 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/bin/content/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.
  2688. 2017-05-11 17:15:20,998 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/bin/content/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.
  2689. 2017-05-11 17:15:21,012 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/bin/content/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.
  2690. 2017-05-11 17:15:21,058 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2691. 2017-05-11 17:15:21,059 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) 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"
  2692. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2693. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2694. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2695. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2696. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2697. at java.lang.Thread.run(Thread.java:745)
  2698. 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
  2699. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2700. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2701. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2702. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2703. ... 5 more
  2704.  
  2705. 2017-05-11 17:15:21,060 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 67) WFLYCTL0013: L'opération ("add") 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\"
  2706. 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"}}
  2707. 2017-05-11 17:15:21,061 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 67) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  2708. {"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\"
  2709. 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"}}
  2710. 2017-05-11 17:15:23,175 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 2113ms
  2711. 2017-05-11 17:15:23,176 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 67) WFLYCTL0183: Rapport de statut de service
  2712. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  2713.  
  2714. 2017-05-11 17:16:15,378 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin" (runtime-name: "xa-cms-admin.war")
  2715. 2017-05-11 17:16:19,203 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/bin/content/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.
  2716. 2017-05-11 17:16:19,204 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/bin/content/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.
  2717. 2017-05-11 17:16:19,205 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/bin/content/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.
  2718. 2017-05-11 17:16:19,218 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/bin/content/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.
  2719. 2017-05-11 17:16:19,263 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2720. 2017-05-11 17:16:19,264 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"
  2721. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2722. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2723. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2724. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2725. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2726. at java.lang.Thread.run(Thread.java:745)
  2727. 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
  2728. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2729. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2730. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2731. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2732. ... 5 more
  2733.  
  2734. 2017-05-11 17:16:19,270 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 68) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin")]) - 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\"
  2735. 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"}}
  2736. 2017-05-11 17:16:19,273 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 68) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  2737. {"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\"
  2738. 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"}}
  2739. 2017-05-11 17:16:20,216 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin (runtime-name: "xa-cms-admin.war") en 941ms
  2740. 2017-05-11 17:16:20,217 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 68) WFLYCTL0183: Rapport de statut de service
  2741. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  2742.  
  2743. 2017-05-11 17:16:30,852 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin" (runtime-name: "xa-cms-admin.war")
  2744. 2017-05-11 17:16:34,573 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/bin/content/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.
  2745. 2017-05-11 17:16:34,573 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/bin/content/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.
  2746. 2017-05-11 17:16:34,574 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/bin/content/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.
  2747. 2017-05-11 17:16:34,586 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/bin/content/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.
  2748. 2017-05-11 17:16:34,648 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2749. 2017-05-11 17:16:34,650 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"
  2750. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2751. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2752. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2753. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2754. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2755. at java.lang.Thread.run(Thread.java:745)
  2756. 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
  2757. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2758. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2759. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2760. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2761. ... 5 more
  2762.  
  2763. 2017-05-11 17:16:34,651 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 68) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin")]) - 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\"
  2764. 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"}}
  2765. 2017-05-11 17:16:34,652 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 68) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  2766. {"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\"
  2767. 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"}}
  2768. 2017-05-11 17:16:35,361 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin (runtime-name: "xa-cms-admin.war") en 706ms
  2769. 2017-05-11 17:16:35,362 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 68) WFLYCTL0183: Rapport de statut de service
  2770. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  2771.  
  2772. 2017-05-11 17:16:47,587 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  2773. 2017-05-11 17:16:47,819 INFO [org.jboss.as.server] (ServerService Thread Pool -- 68) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  2774. 2017-05-11 17:18:15,988 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 71) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\63\ff486db2e98aecfd536d61095b1803a1cf7bc5\content
  2775. 2017-05-11 17:18:15,994 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")
  2776. 2017-05-11 17:18:16,197 INFO [org.jboss.as.server] (ServerService Thread Pool -- 71) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli")
  2777. 2017-05-11 17:18:36,272 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  2778. 2017-05-11 17:18:36,291 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2779. 2017-05-11 17:18:36,321 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  2780. 2017-05-11 17:18:36,322 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  2781. 2017-05-11 17:18:36,377 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  2782. 2017-05-11 17:18:36,455 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: L'hôte default-host s'arrête
  2783. 2017-05-11 17:18:36,532 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin") en 226ms
  2784. 2017-05-11 17:18:36,540 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli") en 240ms
  2785. 2017-05-11 17:18:36,541 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  2786. 2017-05-11 17:18:36,670 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  2787. 2017-05-11 17:18:36,695 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  2788. 2017-05-11 17:18:36,698 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  2789. 2017-05-11 17:18:36,703 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  2790. 2017-05-11 17:18:36,705 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  2791. 2017-05-11 17:18:36,747 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 442ms
  2792. 2017-05-11 17:18:36,766 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 458ms
  2793. 2017-05-11 17:18:36,828 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 518ms
  2794. 2017-05-11 17:18:58,512 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2795. 2017-05-11 17:18:58,845 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2796. 2017-05-11 17:18:58,954 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
  2797. 2017-05-11 17:18:58,956 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Propriétés de système configurées :
  2798. awt.toolkit = sun.awt.windows.WToolkit
  2799. file.encoding = Cp1252
  2800. file.encoding.pkg = sun.io
  2801. file.separator = \
  2802. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2803. java.awt.headless = true
  2804. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2805. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2806. java.class.version = 52.0
  2807. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2808. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2809. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2810. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2811. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2812. java.net.preferIPv4Stack = true
  2813. java.runtime.name = Java(TM) SE Runtime Environment
  2814. java.runtime.version = 1.8.0_121-b13
  2815. java.specification.name = Java Platform API Specification
  2816. java.specification.vendor = Oracle Corporation
  2817. java.specification.version = 1.8
  2818. java.util.logging.manager = org.jboss.logmanager.LogManager
  2819. java.vendor = Oracle Corporation
  2820. java.vendor.url = http://java.oracle.com/
  2821. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2822. java.version = 1.8.0_121
  2823. java.vm.info = mixed mode
  2824. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2825. java.vm.specification.name = Java Virtual Machine Specification
  2826. java.vm.specification.vendor = Oracle Corporation
  2827. java.vm.specification.version = 1.8
  2828. java.vm.vendor = Oracle Corporation
  2829. java.vm.version = 25.121-b13
  2830. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2831. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2832. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2833. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2834. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2835. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2836. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2837. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2838. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2839. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2840. jboss.bind.address = localhost
  2841. jboss.bind.address.management = localhost
  2842. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2843. jboss.host.name = l82564
  2844. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2845. jboss.modules.system.pkgs = org.jboss.byteman
  2846. jboss.node.name = l82564
  2847. jboss.qualified.host.name = l82564
  2848. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2849. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2850. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2851. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2852. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2853. jboss.server.name = l82564
  2854. jboss.server.persist.config = true
  2855. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2856. line.separator =
  2857.  
  2858. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2859. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2860. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2861. org.jboss.logmanager.nocolor = true
  2862. org.jboss.resolver.warning = true
  2863. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2864. os.arch = amd64
  2865. os.name = Windows 7
  2866. os.version = 6.1
  2867. path.separator = ;
  2868. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2869. sun.arch.data.model = 64
  2870. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2871. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2872. sun.cpu.endian = little
  2873. sun.cpu.isalist = amd64
  2874. sun.desktop = windows
  2875. sun.io.unicode.encoding = UnicodeLittle
  2876. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2877. sun.java.launcher = SUN_STANDARD
  2878. sun.jnu.encoding = Cp1252
  2879. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2880. sun.os.patch.level = Service Pack 1
  2881. sun.rmi.dgc.client.gcInterval = 3600000
  2882. sun.rmi.dgc.server.gcInterval = 3600000
  2883. user.country = FR
  2884. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2885. user.home = C:\Utilisateurs\A665340
  2886. user.language = fr
  2887. user.name = A665340
  2888. user.script =
  2889. user.timezone = Europe/Paris
  2890. user.variant =
  2891. 2017-05-11 17:18:58,957 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2892. 2017-05-11 17:19:01,136 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 19) 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é.
  2893. 2017-05-11 17:19:01,390 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "jboss-helloworld.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"jboss-helloworld.war\")] en double"
  2894. 2017-05-11 17:19:01,405 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  2895. 2017-05-11 17:19:01,407 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2896. 2017-05-11 17:19:01,422 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 6ms
  2897. 2017-05-11 17:22:20,429 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2898. 2017-05-11 17:22:20,720 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2899. 2017-05-11 17:22:20,802 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  2900. 2017-05-11 17:22:20,803 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2901. awt.toolkit = sun.awt.windows.WToolkit
  2902. file.encoding = Cp1252
  2903. file.encoding.pkg = sun.io
  2904. file.separator = \
  2905. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2906. java.awt.headless = true
  2907. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2908. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2909. java.class.version = 52.0
  2910. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2911. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2912. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2913. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2914. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  2915. java.net.preferIPv4Stack = true
  2916. java.runtime.name = Java(TM) SE Runtime Environment
  2917. java.runtime.version = 1.8.0_121-b13
  2918. java.specification.name = Java Platform API Specification
  2919. java.specification.vendor = Oracle Corporation
  2920. java.specification.version = 1.8
  2921. java.util.logging.manager = org.jboss.logmanager.LogManager
  2922. java.vendor = Oracle Corporation
  2923. java.vendor.url = http://java.oracle.com/
  2924. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2925. java.version = 1.8.0_121
  2926. java.vm.info = mixed mode
  2927. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2928. java.vm.specification.name = Java Virtual Machine Specification
  2929. java.vm.specification.vendor = Oracle Corporation
  2930. java.vm.specification.version = 1.8
  2931. java.vm.vendor = Oracle Corporation
  2932. java.vm.version = 25.121-b13
  2933. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2934. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2935. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2936. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2937. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2938. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2939. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2940. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2941. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2942. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2943. jboss.bind.address = localhost
  2944. jboss.bind.address.management = localhost
  2945. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2946. jboss.host.name = l82564
  2947. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2948. jboss.modules.system.pkgs = org.jboss.byteman
  2949. jboss.node.name = l82564
  2950. jboss.qualified.host.name = l82564
  2951. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2952. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2953. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2954. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2955. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2956. jboss.server.name = l82564
  2957. jboss.server.persist.config = true
  2958. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2959. line.separator =
  2960.  
  2961. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2962. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2963. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2964. org.jboss.logmanager.nocolor = true
  2965. org.jboss.resolver.warning = true
  2966. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2967. os.arch = amd64
  2968. os.name = Windows 7
  2969. os.version = 6.1
  2970. path.separator = ;
  2971. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2972. sun.arch.data.model = 64
  2973. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  2974. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2975. sun.cpu.endian = little
  2976. sun.cpu.isalist = amd64
  2977. sun.desktop = windows
  2978. sun.io.unicode.encoding = UnicodeLittle
  2979. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2980. sun.java.launcher = SUN_STANDARD
  2981. sun.jnu.encoding = Cp1252
  2982. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2983. sun.os.patch.level = Service Pack 1
  2984. sun.rmi.dgc.client.gcInterval = 3600000
  2985. sun.rmi.dgc.server.gcInterval = 3600000
  2986. user.country = FR
  2987. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2988. user.home = C:\Utilisateurs\A665340
  2989. user.language = fr
  2990. user.name = A665340
  2991. user.script =
  2992. user.timezone = Europe/Paris
  2993. user.variant =
  2994. 2017-05-11 17:22:20,804 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  2995. 2017-05-11 17:22:22,898 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 18) 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é.
  2996. 2017-05-11 17:22:23,191 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin.war")]) - description de l'échec : "WFLYCTL0212: Ressource [(\"deployment\" => \"xa-cms-admin.war\")] en double"
  2997. 2017-05-11 17:22:23,195 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: La phase de démarrage (boot) du serveur a échoué de façon irréversible; sortie. Voir les messages précédents pour obtenir davantage d'informations.
  2998. 2017-05-11 17:22:23,198 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2999. 2017-05-11 17:22:23,211 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 4ms
  3000. 2017-05-11 17:22:43,696 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  3001. 2017-05-11 17:22:44,029 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  3002. 2017-05-11 17:22:44,122 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
  3003. 2017-05-11 17:22:44,124 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Propriétés de système configurées :
  3004. awt.toolkit = sun.awt.windows.WToolkit
  3005. file.encoding = Cp1252
  3006. file.encoding.pkg = sun.io
  3007. file.separator = \
  3008. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  3009. java.awt.headless = true
  3010. java.awt.printerjob = sun.awt.windows.WPrinterJob
  3011. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  3012. java.class.version = 52.0
  3013. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  3014. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  3015. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  3016. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  3017. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  3018. java.net.preferIPv4Stack = true
  3019. java.runtime.name = Java(TM) SE Runtime Environment
  3020. java.runtime.version = 1.8.0_121-b13
  3021. java.specification.name = Java Platform API Specification
  3022. java.specification.vendor = Oracle Corporation
  3023. java.specification.version = 1.8
  3024. java.util.logging.manager = org.jboss.logmanager.LogManager
  3025. java.vendor = Oracle Corporation
  3026. java.vendor.url = http://java.oracle.com/
  3027. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  3028. java.version = 1.8.0_121
  3029. java.vm.info = mixed mode
  3030. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  3031. java.vm.specification.name = Java Virtual Machine Specification
  3032. java.vm.specification.vendor = Oracle Corporation
  3033. java.vm.specification.version = 1.8
  3034. java.vm.vendor = Oracle Corporation
  3035. java.vm.version = 25.121-b13
  3036. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  3037. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  3038. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  3039. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  3040. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  3041. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  3042. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  3043. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  3044. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  3045. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  3046. jboss.bind.address = localhost
  3047. jboss.bind.address.management = localhost
  3048. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  3049. jboss.host.name = l82564
  3050. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  3051. jboss.modules.system.pkgs = org.jboss.byteman
  3052. jboss.node.name = l82564
  3053. jboss.qualified.host.name = l82564
  3054. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3055. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  3056. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  3057. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  3058. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  3059. jboss.server.name = l82564
  3060. jboss.server.persist.config = true
  3061. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  3062. line.separator =
  3063.  
  3064. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  3065. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  3066. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  3067. org.jboss.logmanager.nocolor = true
  3068. org.jboss.resolver.warning = true
  3069. org.xml.sax.driver = __redirected.__XMLReaderFactory
  3070. os.arch = amd64
  3071. os.name = Windows 7
  3072. os.version = 6.1
  3073. path.separator = ;
  3074. program.name = JBossTools: Red Hat JBoss EAP 7.x
  3075. sun.arch.data.model = 64
  3076. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  3077. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  3078. sun.cpu.endian = little
  3079. sun.cpu.isalist = amd64
  3080. sun.desktop = windows
  3081. sun.io.unicode.encoding = UnicodeLittle
  3082. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3083. sun.java.launcher = SUN_STANDARD
  3084. sun.jnu.encoding = Cp1252
  3085. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  3086. sun.os.patch.level = Service Pack 1
  3087. sun.rmi.dgc.client.gcInterval = 3600000
  3088. sun.rmi.dgc.server.gcInterval = 3600000
  3089. user.country = FR
  3090. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  3091. user.home = C:\Utilisateurs\A665340
  3092. user.language = fr
  3093. user.name = A665340
  3094. user.script =
  3095. user.timezone = Europe/Paris
  3096. user.variant =
  3097. 2017-05-11 17:22:44,125 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  3098. 2017-05-11 17:22:46,150 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 23) 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é.
  3099. 2017-05-11 17:22:46,251 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  3100. 2017-05-11 17:22:46,283 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
  3101. 2017-05-11 17:22:46,295 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  3102. 2017-05-11 17:22:46,410 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.
  3103. 2017-05-11 17:22:46,426 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  3104. 2017-05-11 17:22:46,458 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  3105. 2017-05-11 17:22:46,457 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  3106. 2017-05-11 17:22:46,609 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
  3107. 2017-05-11 17:22:46,619 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Démarrage du service de nommage
  3108. 2017-05-11 17:22:46,620 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  3109. 2017-05-11 17:22:46,627 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  3110. 2017-05-11 17:22:46,649 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  3111. 2017-05-11 17:22:46,669 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3112. 2017-05-11 17:22:46,670 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3113. 2017-05-11 17:22:46,671 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)
  3114. 2017-05-11 17:22:46,689 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  3115. 2017-05-11 17:22:46,690 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
  3116. 2017-05-11 17:22:46,721 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  3117. 2017-05-11 17:22:46,955 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.
  3118. 2017-05-11 17:22:47,013 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
  3119. 2017-05-11 17:22:47,020 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: A démarré le serveur default-server.
  3120. 2017-05-11 17:22:47,021 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: L'hôte default-host démarre
  3121. 2017-05-11 17:22:47,023 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: '[]']
  3122. 2017-05-11 17:22:47,092 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.18.Final-redhat-1
  3123. 2017-05-11 17:22:47,528 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  3124. 2017-05-11 17:22:47,745 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")
  3125. 2017-05-11 17:22:47,748 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")
  3126. 2017-05-11 17:22:47,773 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  3127. 2017-05-11 17:22:47,775 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  3128. 2017-05-11 17:22:47,796 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3129. 2017-05-11 17:22:48,297 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  3130. 2017-05-11 17:22:48,454 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  3131. 2017-05-11 17:22:48,985 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  3132. 2017-05-11 17:22:49,850 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  3133. 2017-05-11 17:22:49,857 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  3134. 2017-05-11 17:22:49,955 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-6) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  3135. 2017-05-11 17:22:50,207 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  3136. 2017-05-11 17:22:50,207 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  3137. 2017-05-11 17:22:50,255 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.3 (redhat)
  3138. 2017-05-11 17:22:50,292 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  3139. 2017-05-11 17:22:50,292 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  3140. 2017-05-11 17:22:51,594 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  3141. 2017-05-11 17:22:51,616 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  3142. 2017-05-11 17:22:52,178 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  3143. 2017-05-11 17:22:52,211 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli")
  3144. 2017-05-11 17:22:52,212 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3145. 2017-05-11 17:22:52,212 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  3146. 2017-05-11 17:22:52,213 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3147. 2017-05-11 17:22:52,407 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  3148. 2017-05-11 17:22:52,408 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  3149. 2017-05-11 17:22:52,408 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 9253ms - 527 sur 834 services ont démarré (409 services sont passifs ou à la demande)
  3150. 2017-05-11 17:34:15,103 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  3151. 2017-05-11 17:34:15,134 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  3152. 2017-05-11 17:34:15,235 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  3153. 2017-05-11 17:34:15,266 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  3154. 2017-05-11 17:34:15,278 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") en 131ms
  3155. 2017-05-11 17:34:15,350 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: L'hôte default-host s'arrête
  3156. 2017-05-11 17:34:15,366 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli") en 221ms
  3157. 2017-05-11 17:34:15,370 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  3158. 2017-05-11 17:34:15,374 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  3159. 2017-05-11 17:34:15,409 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  3160. 2017-05-11 17:34:15,417 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  3161. 2017-05-11 17:34:15,420 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  3162. 2017-05-11 17:34:15,420 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  3163. 2017-05-11 17:34:15,422 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  3164. 2017-05-11 17:34:15,481 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 334ms
  3165. 2017-05-11 17:34:15,502 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 342ms
  3166. 2017-05-11 17:34:15,512 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 332ms
  3167. 2017-05-11 17:46:23,824 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  3168. 2017-05-11 17:46:24,210 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  3169. 2017-05-11 17:46:24,302 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  3170. 2017-05-11 17:46:24,304 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  3171. awt.toolkit = sun.awt.windows.WToolkit
  3172. file.encoding = Cp1252
  3173. file.encoding.pkg = sun.io
  3174. file.separator = \
  3175. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  3176. java.awt.headless = true
  3177. java.awt.printerjob = sun.awt.windows.WPrinterJob
  3178. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  3179. java.class.version = 52.0
  3180. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  3181. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  3182. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  3183. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  3184. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  3185. java.net.preferIPv4Stack = true
  3186. java.runtime.name = Java(TM) SE Runtime Environment
  3187. java.runtime.version = 1.8.0_121-b13
  3188. java.specification.name = Java Platform API Specification
  3189. java.specification.vendor = Oracle Corporation
  3190. java.specification.version = 1.8
  3191. java.util.logging.manager = org.jboss.logmanager.LogManager
  3192. java.vendor = Oracle Corporation
  3193. java.vendor.url = http://java.oracle.com/
  3194. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  3195. java.version = 1.8.0_121
  3196. java.vm.info = mixed mode
  3197. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  3198. java.vm.specification.name = Java Virtual Machine Specification
  3199. java.vm.specification.vendor = Oracle Corporation
  3200. java.vm.specification.version = 1.8
  3201. java.vm.vendor = Oracle Corporation
  3202. java.vm.version = 25.121-b13
  3203. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  3204. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  3205. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  3206. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  3207. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  3208. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  3209. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  3210. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  3211. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  3212. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  3213. jboss.bind.address = localhost
  3214. jboss.bind.address.management = localhost
  3215. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  3216. jboss.host.name = l82564
  3217. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  3218. jboss.modules.system.pkgs = org.jboss.byteman
  3219. jboss.node.name = l82564
  3220. jboss.qualified.host.name = l82564
  3221. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3222. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  3223. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  3224. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  3225. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  3226. jboss.server.name = l82564
  3227. jboss.server.persist.config = true
  3228. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  3229. line.separator =
  3230.  
  3231. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  3232. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  3233. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  3234. org.jboss.logmanager.nocolor = true
  3235. org.jboss.resolver.warning = true
  3236. org.xml.sax.driver = __redirected.__XMLReaderFactory
  3237. os.arch = amd64
  3238. os.name = Windows 7
  3239. os.version = 6.1
  3240. path.separator = ;
  3241. program.name = JBossTools: Red Hat JBoss EAP 7.x
  3242. sun.arch.data.model = 64
  3243. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  3244. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  3245. sun.cpu.endian = little
  3246. sun.cpu.isalist = amd64
  3247. sun.desktop = windows
  3248. sun.io.unicode.encoding = UnicodeLittle
  3249. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3250. sun.java.launcher = SUN_STANDARD
  3251. sun.jnu.encoding = Cp1252
  3252. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  3253. sun.os.patch.level = Service Pack 1
  3254. sun.rmi.dgc.client.gcInterval = 3600000
  3255. sun.rmi.dgc.server.gcInterval = 3600000
  3256. user.country = FR
  3257. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  3258. user.home = C:\Utilisateurs\A665340
  3259. user.language = fr
  3260. user.name = A665340
  3261. user.script =
  3262. user.timezone = Europe/Paris
  3263. user.variant =
  3264. 2017-05-11 17:46:24,305 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  3265. 2017-05-11 17:46:26,391 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 12) 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é.
  3266. 2017-05-11 17:46:26,595 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  3267. 2017-05-11 17:46:27,143 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.3.6.Final-redhat-1
  3268. 2017-05-11 17:46:27,207 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  3269. 2017-05-11 17:46:27,449 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.
  3270. 2017-05-11 17:46:27,449 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
  3271. 2017-05-11 17:46:27,562 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  3272. 2017-05-11 17:46:27,576 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  3273. 2017-05-11 17:46:27,579 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  3274. 2017-05-11 17:46:27,579 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  3275. 2017-05-11 17:46:27,595 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  3276. 2017-05-11 17:46:27,712 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  3277. 2017-05-11 17:46:28,624 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  3278. 2017-05-11 17:46:28,755 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3279. 2017-05-11 17:46:28,779 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3280. 2017-05-11 17:46:29,904 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: '[]']
  3281. 2017-05-11 17:46:30,959 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)
  3282. 2017-05-11 17:46:30,964 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  3283. 2017-05-11 17:46:31,808 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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.
  3284. 2017-05-11 17:46:31,808 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) 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.
  3285. 2017-05-11 17:46:32,110 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Démarrage du service de nommage
  3286. 2017-05-11 17:46:32,112 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  3287. 2017-05-11 17:46:32,184 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
  3288. 2017-05-11 17:46:32,208 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: A démarré le serveur default-server.
  3289. 2017-05-11 17:46:32,209 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: L'hôte default-host démarre
  3290. 2017-05-11 17:46:32,824 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  3291. 2017-05-11 17:46:32,864 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  3292. 2017-05-11 17:46:32,904 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")
  3293. 2017-05-11 17:46:32,904 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli")
  3294. 2017-05-11 17:46:32,904 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  3295. 2017-05-11 17:46:32,904 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3296. 2017-05-11 17:46:35,667 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  3297. 2017-05-11 17:46:36,422 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  3298. 2017-05-11 17:46:39,702 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  3299. 2017-05-11 17:46:43,539 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  3300. 2017-05-11 17:46:43,540 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  3301. 2017-05-11 17:46:45,062 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  3302. 2017-05-11 17:46:46,430 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  3303. 2017-05-11 17:46:46,430 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  3304. 2017-05-11 17:46:46,691 INFO [org.jboss.weld.Version] (MSC service thread 1-4) WELD-000900: 2.3.3 (redhat)
  3305. 2017-05-11 17:46:46,765 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  3306. 2017-05-11 17:46:46,765 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  3307. 2017-05-11 17:46:48,682 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  3308. 2017-05-11 17:46:48,805 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  3309. 2017-05-11 17:46:49,566 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  3310. 2017-05-11 17:46:49,695 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli")
  3311. 2017-05-11 17:46:49,695 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3312. 2017-05-11 17:46:49,695 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  3313. 2017-05-11 17:46:49,696 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3314. 2017-05-11 17:46:50,025 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  3315. 2017-05-11 17:46:50,026 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  3316. 2017-05-11 17:46:50,029 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 26805ms - 527 sur 834 services ont démarré (409 services sont passifs ou à la demande)
  3317. 2017-05-11 17:48:03,458 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")
  3318. 2017-05-11 17:48:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli") en 34ms
  3319. 2017-05-11 17:48:03,915 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0021: Contexte web enregistré : /xa-cms-wli
  3320. 2017-05-11 17:48:04,067 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Le déploiement "xa-cms-wli" a été remplacé par le déploiement "xa-cms-wli.war"
  3321. 2017-05-11 17:48:04,081 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Contenu supprimé de la location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\63\ff486db2e98aecfd536d61095b1803a1cf7bc5\content
  3322. 2017-05-11 18:14:54,809 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin") en 64ms
  3323. 2017-05-11 18:14:54,895 INFO [org.jboss.as.server] (ServerService Thread Pool -- 82) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3324. 2017-05-11 18:14:54,910 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 82) WFLYDR0002: Contenu supprimé de la location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\43\9818c59f0cb0831424471e08ae954dcecda58c\content
  3325. 2017-05-11 18:15:49,097 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 84) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\43\9818c59f0cb0831424471e08ae954dcecda58c\content
  3326. 2017-05-11 18:15:49,106 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  3327. 2017-05-11 18:15:56,714 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/bin/content/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.
  3328. 2017-05-11 18:15:56,715 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/bin/content/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.
  3329. 2017-05-11 18:15:56,716 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/bin/content/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.
  3330. 2017-05-11 18:15:56,733 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/bin/content/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.
  3331. 2017-05-11 18:15:56,991 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3332. 2017-05-11 18:15:56,995 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"
  3333. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3334. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3335. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3336. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3337. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3338. at java.lang.Thread.run(Thread.java:745)
  3339. 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
  3340. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3341. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3342. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3343. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3344. ... 5 more
  3345.  
  3346. 2017-05-11 18:15:56,997 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 84) WFLYCTL0013: L'opération ("add") 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\"
  3347. 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"}}
  3348. 2017-05-11 18:15:56,999 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 84) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3349. {"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\"
  3350. 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"}}
  3351. 2017-05-11 18:15:57,691 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 689ms
  3352. 2017-05-11 18:15:57,692 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 84) WFLYCTL0183: Rapport de statut de service
  3353. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3354.  
  3355. 2017-05-11 18:16:50,425 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin" (runtime-name: "xa-cms-admin.war")
  3356. 2017-05-11 18:16:54,122 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/bin/content/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.
  3357. 2017-05-11 18:16:54,123 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/bin/content/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.
  3358. 2017-05-11 18:16:54,123 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/bin/content/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.
  3359. 2017-05-11 18:16:54,135 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/bin/content/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.
  3360. 2017-05-11 18:16:54,188 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3361. 2017-05-11 18:16:54,190 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) 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"
  3362. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3363. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3364. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3365. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3366. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3367. at java.lang.Thread.run(Thread.java:745)
  3368. 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
  3369. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3370. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3371. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3372. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3373. ... 5 more
  3374.  
  3375. 2017-05-11 18:16:54,191 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 85) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin")]) - 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\"
  3376. 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"}}
  3377. 2017-05-11 18:16:54,192 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 85) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3378. {"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\"
  3379. 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"}}
  3380. 2017-05-11 18:16:55,043 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin (runtime-name: "xa-cms-admin.war") en 851ms
  3381. 2017-05-11 18:16:55,044 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 85) WFLYCTL0183: Rapport de statut de service
  3382. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3383.  
  3384. 2017-05-11 18:17:03,491 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  3385. 2017-05-11 18:17:07,033 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3386. 2017-05-11 18:17:07,034 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3387. 2017-05-11 18:17:07,034 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3388. 2017-05-11 18:17:07,047 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3389. 2017-05-11 18:17:07,108 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3390. 2017-05-11 18:17:07,110 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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"
  3391. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3392. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3393. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3394. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3395. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3396. at java.lang.Thread.run(Thread.java:745)
  3397. 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
  3398. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3399. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3400. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3401. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3402. ... 5 more
  3403.  
  3404. 2017-05-11 18:17:07,110 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 85) WFLYCTL0013: L'opération ("add") 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\"
  3405. 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"}}
  3406. 2017-05-11 18:17:07,111 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 85) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3407. {"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\"
  3408. 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"}}
  3409. 2017-05-11 18:17:08,158 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 1046ms
  3410. 2017-05-11 18:17:08,158 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 85) WFLYCTL0183: Rapport de statut de service
  3411. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3412.  
  3413. 2017-05-11 18:17:47,267 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin" (runtime-name: "xa-cms-admin.war")
  3414. 2017-05-11 18:17:51,619 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3415. 2017-05-11 18:17:51,621 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3416. 2017-05-11 18:17:51,621 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3417. 2017-05-11 18:17:51,634 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  3418. 2017-05-11 18:17:51,709 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3419. 2017-05-11 18:17:51,710 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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"
  3420. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3421. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3422. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3423. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3424. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3425. at java.lang.Thread.run(Thread.java:745)
  3426. 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
  3427. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3428. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3429. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3430. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3431. ... 5 more
  3432.  
  3433. 2017-05-11 18:17:51,713 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 86) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin")]) - 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\"
  3434. 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"}}
  3435. 2017-05-11 18:17:51,714 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 86) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3436. {"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\"
  3437. 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"}}
  3438. 2017-05-11 18:17:52,453 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin (runtime-name: "xa-cms-admin.war") en 738ms
  3439. 2017-05-11 18:17:52,453 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 86) WFLYCTL0183: Rapport de statut de service
  3440. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3441.  
  3442. 2017-05-11 18:18:02,685 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3443. 2017-05-11 18:18:02,793 INFO [org.jboss.as.server] (ServerService Thread Pool -- 86) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3444. 2017-05-11 18:18:17,896 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin") en 61ms
  3445. 2017-05-11 18:18:17,945 INFO [org.jboss.as.server] (ServerService Thread Pool -- 87) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3446. 2017-05-11 18:18:17,956 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 87) WFLYDR0002: Contenu supprimé de la location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\43\9818c59f0cb0831424471e08ae954dcecda58c\content
  3447. 2017-05-11 18:18:35,096 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 87) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\43\9818c59f0cb0831424471e08ae954dcecda58c\content
  3448. 2017-05-11 18:18:35,101 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  3449. 2017-05-11 18:18:40,529 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/bin/content/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.
  3450. 2017-05-11 18:18:40,530 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/bin/content/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.
  3451. 2017-05-11 18:18:40,530 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/bin/content/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.
  3452. 2017-05-11 18:18:40,543 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/bin/content/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.
  3453. 2017-05-11 18:18:40,595 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3454. 2017-05-11 18:18:40,597 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) 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"
  3455. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3456. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3457. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3458. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3459. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3460. at java.lang.Thread.run(Thread.java:745)
  3461. 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
  3462. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3463. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3464. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3465. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3466. ... 5 more
  3467.  
  3468. 2017-05-11 18:18:40,598 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 87) WFLYCTL0013: L'opération ("add") 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\"
  3469. 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"}}
  3470. 2017-05-11 18:18:40,599 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 87) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3471. {"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\"
  3472. 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"}}
  3473. 2017-05-11 18:18:41,312 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 712ms
  3474. 2017-05-11 18:18:41,313 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 87) WFLYCTL0183: Rapport de statut de service
  3475. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3476.  
  3477. 2017-05-11 18:19:10,674 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin" (runtime-name: "xa-cms-admin.war")
  3478. 2017-05-11 18:19:13,908 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/bin/content/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.
  3479. 2017-05-11 18:19:13,909 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/bin/content/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.
  3480. 2017-05-11 18:19:13,910 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/bin/content/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.
  3481. 2017-05-11 18:19:13,943 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/bin/content/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.
  3482. 2017-05-11 18:19:13,990 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  3483. 2017-05-11 18:19:13,991 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) 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"
  3484. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  3485. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  3486. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  3487. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  3488. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  3489. at java.lang.Thread.run(Thread.java:745)
  3490. 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
  3491. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  3492. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  3493. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  3494. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  3495. ... 5 more
  3496.  
  3497. 2017-05-11 18:19:13,992 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 88) WFLYCTL0013: L'opération ("add") a échoué - adresse : ([("deployment" => "xa-cms-admin")]) - 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\"
  3498. 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"}}
  3499. 2017-05-11 18:19:13,993 ERROR [org.jboss.as.server] (ServerService Thread Pool -- 88) WFLYSRV0021: Le déploiement "xa-cms-admin.war" a été annulé avec le message d'échec
  3500. {"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\"
  3501. 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"}}
  3502. 2017-05-11 18:19:14,676 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin (runtime-name: "xa-cms-admin.war") en 683ms
  3503. 2017-05-11 18:19:14,677 INFO [org.jboss.as.controller] (ServerService Thread Pool -- 88) WFLYCTL0183: Rapport de statut de service
  3504. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  3505.  
  3506. 2017-05-11 18:19:24,593 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")
  3507. 2017-05-11 18:19:24,697 INFO [org.jboss.as.server] (ServerService Thread Pool -- 88) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3508. 2017-05-11 18:59:15,266 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  3509. 2017-05-11 18:59:15,276 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  3510. 2017-05-11 18:59:15,369 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 93) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  3511. 2017-05-11 18:59:15,370 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 97) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  3512. 2017-05-11 18:59:15,372 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 96) WFLYUT0022: Contexte web désenregistré : /xa-cms-wli
  3513. 2017-05-11 18:59:15,473 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  3514. 2017-05-11 18:59:15,483 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0019: L'hôte default-host s'arrête
  3515. 2017-05-11 18:59:15,482 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin") en 195ms
  3516. 2017-05-11 18:59:15,484 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  3517. 2017-05-11 18:59:15,495 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Arrêt du déploiement de xa-cms-wli.war (runtime-name: "xa-cms-wli.war") en 210ms
  3518. 2017-05-11 18:59:15,528 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  3519. 2017-05-11 18:59:15,585 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  3520. 2017-05-11 18:59:15,590 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  3521. 2017-05-11 18:59:15,591 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  3522. 2017-05-11 18:59:15,592 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  3523. 2017-05-11 18:59:15,623 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 336ms
  3524. 2017-05-11 18:59:15,626 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 341ms
  3525. 2017-05-11 18:59:15,639 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 343ms
  3526. 2017-05-11 18:59:26,167 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  3527. 2017-05-11 18:59:26,479 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  3528. 2017-05-11 18:59:26,603 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) démarre
  3529. 2017-05-11 18:59:26,605 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Propriétés de système configurées :
  3530. awt.toolkit = sun.awt.windows.WToolkit
  3531. file.encoding = Cp1252
  3532. file.encoding.pkg = sun.io
  3533. file.separator = \
  3534. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  3535. java.awt.headless = true
  3536. java.awt.printerjob = sun.awt.windows.WPrinterJob
  3537. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  3538. java.class.version = 52.0
  3539. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  3540. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  3541. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  3542. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  3543. java.library.path = C:\Program Files\Java\jdk1.8.0_121\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;native;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\Program Files\Haskell\bin;C:\Program Files\Haskell Platform\8.0.2\lib\extralibs\bin;C:\Program Files\Haskell Platform\8.0.2\bin;C:\Program Files (x86)\RSA SecurID Token Common;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\WIDCOMM\Bluetooth Software\;C:\Program Files\WIDCOMM\Bluetooth Software\syswow64;C:\Program Files (x86)\PuTTY\;C:\Program Files\Haskell Platform\8.0.2\mingw\bin;C:\Program Files\Git\cmd;C:\Utilisateurs\A665340\AppData\Roaming\cabal\bin;C:\Utilisateurs\A665340\AppData\Roaming\local\bin;C:\Utilisateurs\A665340\neon\eclipse-java-neon-3-win32-x86_64\eclipse;;.
  3544. java.net.preferIPv4Stack = true
  3545. java.runtime.name = Java(TM) SE Runtime Environment
  3546. java.runtime.version = 1.8.0_121-b13
  3547. java.specification.name = Java Platform API Specification
  3548. java.specification.vendor = Oracle Corporation
  3549. java.specification.version = 1.8
  3550. java.util.logging.manager = org.jboss.logmanager.LogManager
  3551. java.vendor = Oracle Corporation
  3552. java.vendor.url = http://java.oracle.com/
  3553. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  3554. java.version = 1.8.0_121
  3555. java.vm.info = mixed mode
  3556. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  3557. java.vm.specification.name = Java Virtual Machine Specification
  3558. java.vm.specification.vendor = Oracle Corporation
  3559. java.vm.specification.version = 1.8
  3560. java.vm.vendor = Oracle Corporation
  3561. java.vm.version = 25.121-b13
  3562. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  3563. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  3564. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  3565. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  3566. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  3567. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  3568. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  3569. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  3570. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  3571. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  3572. jboss.bind.address = localhost
  3573. jboss.bind.address.management = localhost
  3574. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  3575. jboss.host.name = l82564
  3576. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  3577. jboss.modules.system.pkgs = org.jboss.byteman
  3578. jboss.node.name = l82564
  3579. jboss.qualified.host.name = l82564
  3580. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3581. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  3582. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  3583. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  3584. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  3585. jboss.server.name = l82564
  3586. jboss.server.persist.config = true
  3587. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  3588. line.separator =
  3589.  
  3590. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  3591. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  3592. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  3593. org.jboss.logmanager.nocolor = true
  3594. org.jboss.resolver.warning = true
  3595. org.xml.sax.driver = __redirected.__XMLReaderFactory
  3596. os.arch = amd64
  3597. os.name = Windows 7
  3598. os.version = 6.1
  3599. path.separator = ;
  3600. program.name = JBossTools: Red Hat JBoss EAP 7.x
  3601. sun.arch.data.model = 64
  3602. sun.boot.class.path = C:\Program Files\Java\jdk1.8.0_121\jre\lib\resources.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\rt.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jce.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.8.0_121\jre\lib\jfr.jar;C:\Program Files\Java\jdk1.8.0_121\jre\classes
  3603. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  3604. sun.cpu.endian = little
  3605. sun.cpu.isalist = amd64
  3606. sun.desktop = windows
  3607. sun.io.unicode.encoding = UnicodeLittle
  3608. sun.java.command = org.jboss.modules.Main -mp C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules org.jboss.as.standalone -b localhost --server-config=standalone.xml -Djboss.server.base.dir=C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  3609. sun.java.launcher = SUN_STANDARD
  3610. sun.jnu.encoding = Cp1252
  3611. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  3612. sun.os.patch.level = Service Pack 1
  3613. sun.rmi.dgc.client.gcInterval = 3600000
  3614. sun.rmi.dgc.server.gcInterval = 3600000
  3615. user.country = FR
  3616. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  3617. user.home = C:\Utilisateurs\A665340
  3618. user.language = fr
  3619. user.name = A665340
  3620. user.script =
  3621. user.timezone = Europe/Paris
  3622. user.variant =
  3623. 2017-05-11 18:59:26,608 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Arguments MV : -Dprogram.name=JBossTools: Red Hat JBoss EAP 7.x -Xms64m -Xmx512m -Dorg.jboss.resolver.warning=true -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log -Dlogging.configuration=file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties -Djboss.home.dir=C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0 -Dorg.jboss.logmanager.nocolor=true -Djboss.bind.address.management=localhost -Dfile.encoding=Cp1252
  3624. 2017-05-11 18:59:28,593 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 17) 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é.
  3625. 2017-05-11 18:59:28,806 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  3626. 2017-05-11 18:59:28,836 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  3627. 2017-05-11 18:59:28,847 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  3628. 2017-05-11 18:59:28,923 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  3629. 2017-05-11 18:59:28,944 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  3630. 2017-05-11 18:59:28,950 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  3631. 2017-05-11 18:59:28,956 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.
  3632. 2017-05-11 18:59:28,956 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  3633. 2017-05-11 18:59:28,962 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
  3634. 2017-05-11 18:59:28,985 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  3635. 2017-05-11 18:59:29,194 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Démarrage du sous-système JCA (WildFly/IronJacamar 1.3.3.Final-redhat-1)
  3636. 2017-05-11 18:59:29,202 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  3637. 2017-05-11 18:59:29,218 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Démarrage du service de nommage
  3638. 2017-05-11 18:59:29,220 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  3639. 2017-05-11 18:59:29,293 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3640. 2017-05-11 18:59:29,294 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  3641. 2017-05-11 18:59:29,360 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)
  3642. 2017-05-11 18:59:29,368 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  3643. 2017-05-11 18:59:29,457 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) 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.
  3644. 2017-05-11 18:59:29,465 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.
  3645. 2017-05-11 18:59:29,561 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: '[]']
  3646. 2017-05-11 18:59:29,916 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.18.Final-redhat-1
  3647. 2017-05-11 18:59:29,947 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: A démarré le serveur default-server.
  3648. 2017-05-11 18:59:29,948 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0018: L'hôte default-host démarre
  3649. 2017-05-11 18:59:30,002 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  3650. 2017-05-11 18:59:30,392 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3651. 2017-05-11 18:59:30,392 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")
  3652. 2017-05-11 18:59:30,397 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")
  3653. 2017-05-11 18:59:30,400 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")
  3654. 2017-05-11 18:59:30,404 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  3655. 2017-05-11 18:59:30,875 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  3656. 2017-05-11 18:59:31,050 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  3657. 2017-05-11 18:59:31,217 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
  3658. 2017-05-11 18:59:32,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  3659. 2017-05-11 18:59:32,338 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  3660. 2017-05-11 18:59:32,487 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  3661. 2017-05-11 18:59:32,731 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  3662. 2017-05-11 18:59:32,733 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  3663. 2017-05-11 18:59:32,769 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.3 (redhat)
  3664. 2017-05-11 18:59:32,802 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  3665. 2017-05-11 18:59:32,805 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  3666. 2017-05-11 18:59:33,176 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /xa-cms-wli
  3667. 2017-05-11 18:59:34,064 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 59) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  3668. 2017-05-11 18:59:34,067 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  3669. 2017-05-11 18:59:34,624 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  3670. 2017-05-11 18:59:34,656 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin")
  3671. 2017-05-11 18:59:34,657 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  3672. 2017-05-11 18:59:34,657 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  3673. 2017-05-11 18:59:34,670 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  3674. 2017-05-11 18:59:34,874 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  3675. 2017-05-11 18:59:34,874 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  3676. 2017-05-11 18:59:34,875 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) a démarré en 9076ms - 559 sur 866 services ont démarré (412 services sont passifs ou à la demande)
  3677. 2017-05-11 18:59:47,018 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0236: Suspending server with no timeout.
  3678. 2017-05-11 18:59:47,089 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  3679. 2017-05-11 18:59:47,105 INFO [org.jboss.as.protocol] (management I/O-1) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 2,5,management-handler-thread]
  3680. 2017-05-11 18:59:47,242 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 17) WFLYUT0022: Contexte web désenregistré : /xa-cms-wli
  3681. 2017-05-11 18:59:47,265 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 5) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  3682. 2017-05-11 18:59:47,267 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 6) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  3683. 2017-05-11 18:59:47,510 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin") en 406ms
  3684. 2017-05-11 18:59:47,524 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 412ms
  3685. 2017-05-11 18:59:47,533 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0019: L'hôte default-host s'arrête
  3686. 2017-05-11 18:59:47,535 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  3687. 2017-05-11 18:59:47,557 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  3688. 2017-05-11 18:59:47,580 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  3689. 2017-05-11 18:59:47,613 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  3690. 2017-05-11 18:59:47,616 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  3691. 2017-05-11 18:59:47,620 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0007: Undertow HTTP écouteur default s'est arrêté, était lié à 127.0.0.1:8080
  3692. 2017-05-11 18:59:47,622 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  3693. 2017-05-11 18:59:47,642 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Arrêt du déploiement de jboss-helloworld.war (runtime-name: "jboss-helloworld.war") en 537ms
  3694. 2017-05-11 18:59:47,645 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Arrêt du déploiement de jboss-numberguess.war (runtime-name: "jboss-numberguess.war") en 532ms
  3695. 2017-05-11 18:59:47,652 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) arrêté en 542ms
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!