API tools faq
paste
Guest User

antoine_serverlog_part1

a guest
May 12th, 2017
271
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 282.89 KB | None | 0 0
raw download clone embed print report
  1. 2017-05-11 10:46:50,488 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2. 2017-05-11 10:46:54,018 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  3. 2017-05-11 10:46:54,269 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 10:46:54,271 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 10:46:54,272 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 10:47:03,319 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é.
  100. 2017-05-11 10:47:03,755 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"
  101. 2017-05-11 10:47:03,796 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.
  102. 2017-05-11 10:47:03,799 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  103. 2017-05-11 10:47:03,833 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 12ms
  104. 2017-05-11 10:48:12,010 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  105. 2017-05-11 10:48:12,408 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  106. 2017-05-11 10:48:12,500 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
  107. 2017-05-11 10:48:12,503 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  108. awt.toolkit = sun.awt.windows.WToolkit
  109. file.encoding = Cp1252
  110. file.encoding.pkg = sun.io
  111. file.separator = \
  112. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  113. java.awt.headless = true
  114. java.awt.printerjob = sun.awt.windows.WPrinterJob
  115. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  116. java.class.version = 52.0
  117. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  118. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  119. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  120. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  121. 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;;.
  122. java.net.preferIPv4Stack = true
  123. java.runtime.name = Java(TM) SE Runtime Environment
  124. java.runtime.version = 1.8.0_121-b13
  125. java.specification.name = Java Platform API Specification
  126. java.specification.vendor = Oracle Corporation
  127. java.specification.version = 1.8
  128. java.util.logging.manager = org.jboss.logmanager.LogManager
  129. java.vendor = Oracle Corporation
  130. java.vendor.url = http://java.oracle.com/
  131. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  132. java.version = 1.8.0_121
  133. java.vm.info = mixed mode
  134. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  135. java.vm.specification.name = Java Virtual Machine Specification
  136. java.vm.specification.vendor = Oracle Corporation
  137. java.vm.specification.version = 1.8
  138. java.vm.vendor = Oracle Corporation
  139. java.vm.version = 25.121-b13
  140. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  141. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  142. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  143. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  144. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  145. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  146. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  147. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  148. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  149. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  150. jboss.bind.address = localhost
  151. jboss.bind.address.management = localhost
  152. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  153. jboss.host.name = l82564
  154. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  155. jboss.modules.system.pkgs = org.jboss.byteman
  156. jboss.node.name = l82564
  157. jboss.qualified.host.name = l82564
  158. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  159. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  160. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  161. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  162. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  163. jboss.server.name = l82564
  164. jboss.server.persist.config = true
  165. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  166. line.separator =
  167.  
  168. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  169. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  170. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  171. org.jboss.logmanager.nocolor = true
  172. org.jboss.resolver.warning = true
  173. org.xml.sax.driver = __redirected.__XMLReaderFactory
  174. os.arch = amd64
  175. os.name = Windows 7
  176. os.version = 6.1
  177. path.separator = ;
  178. program.name = JBossTools: Red Hat JBoss EAP 7.x
  179. sun.arch.data.model = 64
  180. 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
  181. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  182. sun.cpu.endian = little
  183. sun.cpu.isalist = amd64
  184. sun.desktop = windows
  185. sun.io.unicode.encoding = UnicodeLittle
  186. 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
  187. sun.java.launcher = SUN_STANDARD
  188. sun.jnu.encoding = Cp1252
  189. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  190. sun.os.patch.level = Service Pack 1
  191. sun.rmi.dgc.client.gcInterval = 3600000
  192. sun.rmi.dgc.server.gcInterval = 3600000
  193. user.country = FR
  194. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  195. user.home = C:\Utilisateurs\A665340
  196. user.language = fr
  197. user.name = A665340
  198. user.script =
  199. user.timezone = Europe/Paris
  200. user.variant =
  201. 2017-05-11 10:48:12,505 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
  202. 2017-05-11 10:48:14,839 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é.
  203. 2017-05-11 10:48:14,991 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-admin.war n'a pas abouti
  204. 2017-05-11 10:48:15,243 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-wli.war n'a pas abouti
  205. 2017-05-11 10:48:15,396 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  206. 2017-05-11 10:48:15,538 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.3.6.Final-redhat-1
  207. 2017-05-11 10:48:15,545 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  208. 2017-05-11 10:48:15,767 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.
  209. 2017-05-11 10:48:15,791 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  210. 2017-05-11 10:48:15,829 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
  211. 2017-05-11 10:48:15,938 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  212. 2017-05-11 10:48:15,943 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  213. 2017-05-11 10:48:16,002 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)
  214. 2017-05-11 10:48:16,022 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  215. 2017-05-11 10:48:16,030 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  216. 2017-05-11 10:48:16,371 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  217. 2017-05-11 10:48:16,631 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  218. 2017-05-11 10:48:16,631 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  219. 2017-05-11 10:48:16,862 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: '[]']
  220. 2017-05-11 10:48:17,900 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)
  221. 2017-05-11 10:48:17,903 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
  222. 2017-05-11 10:48:18,254 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Démarrage du service de nommage
  223. 2017-05-11 10:48:18,255 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  224. 2017-05-11 10:48:18,331 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.
  225. 2017-05-11 10:48:18,330 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) 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.
  226. 2017-05-11 10:48:18,450 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: A démarré le serveur default-server.
  227. 2017-05-11 10:48:18,453 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: L'hôte default-host démarre
  228. 2017-05-11 10:48:18,475 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.18.Final-redhat-1
  229. 2017-05-11 10:48:18,768 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  230. 2017-05-11 10:48:19,643 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")
  231. 2017-05-11 10:48:19,688 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")
  232. 2017-05-11 10:48:19,689 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")
  233. 2017-05-11 10:48:19,698 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
  234. 2017-05-11 10:48:19,700 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  235. 2017-05-11 10:48:20,747 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  236. 2017-05-11 10:48:23,871 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)
  237. 2017-05-11 10:48:23,883 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  238. 2017-05-11 10:48:27,802 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-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  239. 2017-05-11 10:48:27,804 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  240. 2017-05-11 10:48:27,805 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  241. 2017-05-11 10:48:27,826 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-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  242. 2017-05-11 10:48:29,592 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  243. 2017-05-11 10:48:29,600 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"
  244. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  245. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  246. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  247. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  248. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  249. at java.lang.Thread.run(Thread.java:745)
  250. 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
  251. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  252. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  253. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  254. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  255. ... 5 more
  256.  
  257. 2017-05-11 10:48:30,058 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.
  258. 2017-05-11 10:48:30,060 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.
  259. 2017-05-11 10:48:30,061 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.
  260. 2017-05-11 10:48:30,071 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.
  261. 2017-05-11 10:48:30,071 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.
  262. 2017-05-11 10:48:30,072 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.
  263. 2017-05-11 10:48:30,077 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.
  264. 2017-05-11 10:48:30,106 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.
  265. 2017-05-11 10:48:30,127 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.
  266. 2017-05-11 10:48:30,171 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.
  267. 2017-05-11 10:48:30,171 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.
  268. 2017-05-11 10:48:30,172 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.
  269. 2017-05-11 10:48:30,231 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  270. 2017-05-11 10:48:30,263 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  271. 2017-05-11 10:48:30,343 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  272. 2017-05-11 10:48:30,359 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"
  273. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  274. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  275. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  276. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  277. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  278. at java.lang.Thread.run(Thread.java:745)
  279. 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
  280. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  281. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  282. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  283. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  284. ... 5 more
  285.  
  286. 2017-05-11 10:48:31,191 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  287. 2017-05-11 10:48:31,735 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  288. 2017-05-11 10:48:31,736 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  289. 2017-05-11 10:48:31,822 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.3 (redhat)
  290. 2017-05-11 10:48:31,903 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  291. 2017-05-11 10:48:31,902 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  292. 2017-05-11 10:48:34,022 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 60) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  293. 2017-05-11 10:48:34,115 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  294. 2017-05-11 10:48:35,212 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  295. 2017-05-11 10:48:35,215 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\"
  296. 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"}}
  297. 2017-05-11 10:48:35,216 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\"
  298. 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"}}
  299. 2017-05-11 10:48:35,288 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  300. 2017-05-11 10:48:35,288 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  301. 2017-05-11 10:48:35,289 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  302. 2017-05-11 10:48:35,289 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  303. 2017-05-11 10:48:35,292 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  304. 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"
  305. 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"
  306.  
  307. 2017-05-11 10:48:35,631 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  308. 2017-05-11 10:48:35,631 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  309. 2017-05-11 10:48:35,632 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 24058ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  310. 2017-05-11 10:48:36,628 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.war") en 783ms
  311. 2017-05-11 10:48:37,388 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 1545ms
  312. 2017-05-11 10:48:37,617 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  313. 2017-05-11 10:48:37,618 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  314. 2017-05-11 10:48:37,618 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  315. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  316. service jboss.deployment.unit."xa-cms-wli.war".PARSE
  317.  
  318. 2017-05-11 12:12:53,904 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")
  319. 2017-05-11 12:13:03,055 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.
  320. 2017-05-11 12:13:03,056 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.
  321. 2017-05-11 12:13:03,056 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.
  322. 2017-05-11 12:13:03,069 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.
  323. 2017-05-11 12:13:03,245 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  324. 2017-05-11 12:13:03,248 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"
  325. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  326. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  327. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  328. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  329. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  330. at java.lang.Thread.run(Thread.java:745)
  331. 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
  332. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  333. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  334. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  335. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  336. ... 5 more
  337.  
  338. 2017-05-11 12:13:03,250 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\"
  339. 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"}}
  340. 2017-05-11 12:13:03,313 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  341. 2017-05-11 12:13:03,313 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  342. 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"
  343.  
  344. 2017-05-11 12:13:25,539 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 587ms
  345. 2017-05-11 12:13:25,541 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")
  346. 2017-05-11 12:13:28,863 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  347. 2017-05-11 12:13:28,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  348. 2017-05-11 12:13:28,864 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  349. 2017-05-11 12:13:28,876 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  350. 2017-05-11 12:13:28,978 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  351. 2017-05-11 12:13:28,980 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"
  352. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  353. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  354. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  355. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  356. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  357. at java.lang.Thread.run(Thread.java:745)
  358. 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
  359. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  360. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  361. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  362. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  363. ... 5 more
  364.  
  365. 2017-05-11 12:13:28,981 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"
  366. 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"}}
  367. 2017-05-11 12:13:29,086 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Le déploiement "xa-cms-admin.war" a été remplacé par le déploiement "xa-cms-admin.war"
  368. 2017-05-11 12:13:29,087 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  369. 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"
  370. service jboss.deployment.unit."xa-cms-admin.war".PARSE
  371.  
  372. 2017-05-11 12:14:23,080 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.war") en 750ms
  373. 2017-05-11 12:14:23,081 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")
  374. 2017-05-11 12:14:26,380 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.
  375. 2017-05-11 12:14:26,380 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.
  376. 2017-05-11 12:14:26,381 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.
  377. 2017-05-11 12:14:26,394 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.
  378. 2017-05-11 12:14:26,472 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  379. 2017-05-11 12:14:26,474 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"
  380. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  381. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  382. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  383. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  384. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  385. at java.lang.Thread.run(Thread.java:745)
  386. 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
  387. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  388. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  389. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  390. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  391. ... 5 more
  392.  
  393. 2017-05-11 12:14:26,480 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"
  394. 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"}}
  395. 2017-05-11 12:14:26,540 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Le déploiement "xa-cms-admin.war" a été remplacé par le déploiement "xa-cms-admin.war"
  396. 2017-05-11 12:14:26,540 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  397. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  398. 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"
  399.  
  400. 2017-05-11 14:57:26,775 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  401. 2017-05-11 14:57:29,061 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  402. 2017-05-11 14:57:30,035 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
  403. 2017-05-11 14:57:30,061 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  404. awt.toolkit = sun.awt.windows.WToolkit
  405. file.encoding = Cp1252
  406. file.encoding.pkg = sun.io
  407. file.separator = \
  408. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  409. java.awt.headless = true
  410. java.awt.printerjob = sun.awt.windows.WPrinterJob
  411. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  412. java.class.version = 52.0
  413. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  414. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  415. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  416. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  417. 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;;.
  418. java.net.preferIPv4Stack = true
  419. java.runtime.name = Java(TM) SE Runtime Environment
  420. java.runtime.version = 1.8.0_121-b13
  421. java.specification.name = Java Platform API Specification
  422. java.specification.vendor = Oracle Corporation
  423. java.specification.version = 1.8
  424. java.util.logging.manager = org.jboss.logmanager.LogManager
  425. java.vendor = Oracle Corporation
  426. java.vendor.url = http://java.oracle.com/
  427. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  428. java.version = 1.8.0_121
  429. java.vm.info = mixed mode
  430. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  431. java.vm.specification.name = Java Virtual Machine Specification
  432. java.vm.specification.vendor = Oracle Corporation
  433. java.vm.specification.version = 1.8
  434. java.vm.vendor = Oracle Corporation
  435. java.vm.version = 25.121-b13
  436. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  437. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  438. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  439. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  440. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  441. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  442. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  443. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  444. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  445. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  446. jboss.bind.address = localhost
  447. jboss.bind.address.management = localhost
  448. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  449. jboss.host.name = l82564
  450. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  451. jboss.modules.system.pkgs = org.jboss.byteman
  452. jboss.node.name = l82564
  453. jboss.qualified.host.name = l82564
  454. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  455. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  456. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  457. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  458. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  459. jboss.server.name = l82564
  460. jboss.server.persist.config = true
  461. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  462. line.separator =
  463.  
  464. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  465. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  466. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  467. org.jboss.logmanager.nocolor = true
  468. org.jboss.resolver.warning = true
  469. org.xml.sax.driver = __redirected.__XMLReaderFactory
  470. os.arch = amd64
  471. os.name = Windows 7
  472. os.version = 6.1
  473. path.separator = ;
  474. program.name = JBossTools: Red Hat JBoss EAP 7.x
  475. sun.arch.data.model = 64
  476. 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
  477. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  478. sun.cpu.endian = little
  479. sun.cpu.isalist = amd64
  480. sun.desktop = windows
  481. sun.io.unicode.encoding = UnicodeLittle
  482. 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
  483. sun.java.launcher = SUN_STANDARD
  484. sun.jnu.encoding = Cp1252
  485. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  486. sun.os.patch.level = Service Pack 1
  487. sun.rmi.dgc.client.gcInterval = 3600000
  488. sun.rmi.dgc.server.gcInterval = 3600000
  489. user.country = FR
  490. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  491. user.home = C:\Utilisateurs\A665340
  492. user.language = fr
  493. user.name = A665340
  494. user.script =
  495. user.timezone = Europe/Paris
  496. user.variant =
  497. 2017-05-11 14:57:30,063 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
  498. 2017-05-11 14:57:34,404 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é.
  499. 2017-05-11 14:57:34,673 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-admin.war n'a pas abouti
  500. 2017-05-11 14:57:35,075 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-wli.war n'a pas abouti
  501. 2017-05-11 14:57:35,443 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  502. 2017-05-11 14:57:35,525 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.3.6.Final-redhat-1
  503. 2017-05-11 14:57:35,535 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  504. 2017-05-11 14:57:35,716 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.
  505. 2017-05-11 14:57:35,778 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  506. 2017-05-11 14:57:35,785 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  507. 2017-05-11 14:57:35,803 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  508. 2017-05-11 14:57:35,804 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  509. 2017-05-11 14:57:35,838 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
  510. 2017-05-11 14:57:35,843 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  511. 2017-05-11 14:57:35,847 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  512. 2017-05-11 14:57:35,877 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)
  513. 2017-05-11 14:57:36,166 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  514. 2017-05-11 14:57:36,168 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  515. 2017-05-11 14:57:36,359 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)
  516. 2017-05-11 14:57:36,447 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
  517. 2017-05-11 14:57:36,684 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Démarrage du service de nommage
  518. 2017-05-11 14:57:36,691 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  519. 2017-05-11 14:57:36,696 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: '[]']
  520. 2017-05-11 14:57:36,797 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.
  521. 2017-05-11 14:57:36,798 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.
  522. 2017-05-11 14:57:37,741 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.18.Final-redhat-1
  523. 2017-05-11 14:57:37,857 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: A démarré le serveur default-server.
  524. 2017-05-11 14:57:37,860 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: L'hôte default-host démarre
  525. 2017-05-11 14:57:38,206 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: FileSystemDeploymentService démarré pour le répertoire C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments
  526. 2017-05-11 14:57:38,261 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  527. 2017-05-11 14:57:38,273 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")
  528. 2017-05-11 14:57:38,332 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")
  529. 2017-05-11 14:57:38,332 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")
  530. 2017-05-11 14:57:38,332 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")
  531. 2017-05-11 14:57:38,946 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  532. 2017-05-11 14:57:43,411 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  533. 2017-05-11 14:57:45,858 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)
  534. 2017-05-11 14:57:51,002 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  535. 2017-05-11 14:57:51,004 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  536. 2017-05-11 14:57:52,094 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-1) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  537. 2017-05-11 14:57:55,182 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  538. 2017-05-11 14:57:55,182 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  539. 2017-05-11 14:57:55,672 INFO [org.jboss.weld.Version] (MSC service thread 1-6) WELD-000900: 2.3.3 (redhat)
  540. 2017-05-11 14:57:56,090 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  541. 2017-05-11 14:57:56,091 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  542. 2017-05-11 14:58:03,410 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 62) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  543. 2017-05-11 14:58:04,071 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  544. 2017-05-11 14:58:09,936 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  545. 2017-05-11 14:58:11,101 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-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  546. 2017-05-11 14:58:11,102 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  547. 2017-05-11 14:58:11,102 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  548. 2017-05-11 14:58:11,121 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-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  549. 2017-05-11 14:58:11,745 INFO [org.jboss.as.jpa] (MSC service thread 1-2) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  550. 2017-05-11 14:58:11,748 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"
  551. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  552. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  553. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  554. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  555. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  556. at java.lang.Thread.run(Thread.java:745)
  557. 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
  558. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  559. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  560. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  561. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  562. ... 5 more
  563.  
  564. 2017-05-11 14:58:26,715 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.
  565. 2017-05-11 14:58:26,716 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.
  566. 2017-05-11 14:58:26,716 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.
  567. 2017-05-11 14:58:26,717 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.
  568. 2017-05-11 14:58:26,718 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.
  569. 2017-05-11 14:58:26,720 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.
  570. 2017-05-11 14:58:26,721 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.
  571. 2017-05-11 14:58:26,765 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.
  572. 2017-05-11 14:58:26,788 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.
  573. 2017-05-11 14:58:26,827 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.
  574. 2017-05-11 14:58:26,827 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.
  575. 2017-05-11 14:58:26,828 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.
  576. 2017-05-11 14:58:27,003 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  577. 2017-05-11 14:58:27,030 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"
  578. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  579. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  580. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  581. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  582. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  583. at java.lang.Thread.run(Thread.java:745)
  584. 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
  585. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  586. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  587. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  588. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  589. ... 5 more
  590.  
  591. 2017-05-11 14:58:27,034 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\"
  592. 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"}}
  593. 2017-05-11 14:58:27,037 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\"
  594. 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"}}
  595. 2017-05-11 14:58:27,196 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  596. 2017-05-11 14:58:27,197 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  597. 2017-05-11 14:58:27,199 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  598. 2017-05-11 14:58:27,199 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  599. 2017-05-11 14:58:27,201 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  600. 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"
  601. 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"
  602.  
  603. 2017-05-11 14:58:27,504 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  604. 2017-05-11 14:58:27,505 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  605. 2017-05-11 14:58:27,505 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 62345ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  606. 2017-05-11 14:58:28,726 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 909ms
  607. 2017-05-11 14:58:29,073 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 1255ms
  608. 2017-05-11 14:58:29,338 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  609. 2017-05-11 14:58:29,339 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  610. 2017-05-11 14:58:29,339 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  611. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  612. service jboss.deployment.unit."xa-cms-wli.war".PARSE
  613.  
  614. 2017-05-11 15:18:44,511 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")
  615. 2017-05-11 15:18:47,185 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.
  616. 2017-05-11 15:18:47,186 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.
  617. 2017-05-11 15:18:47,186 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.
  618. 2017-05-11 15:18:47,198 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.
  619. 2017-05-11 15:18:47,261 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  620. 2017-05-11 15:18:47,263 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"
  621. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  622. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  623. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  624. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  625. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  626. at java.lang.Thread.run(Thread.java:745)
  627. 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
  628. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  629. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  630. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  631. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  632. ... 5 more
  633.  
  634. 2017-05-11 15:18:47,269 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: L'opération ("deploy") a échoué - adresse : ([("deployment" => "xa-cms-admin.war")]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-admin.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-admin.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-admin.war\"
  635. 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"}}
  636. 2017-05-11 15:18:47,309 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  637. 2017-05-11 15:18:47,310 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  638. 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"
  639.  
  640. 2017-05-11 15:19:29,748 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")
  641. 2017-05-11 15:19:35,862 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.
  642. 2017-05-11 15:19:35,863 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.
  643. 2017-05-11 15:19:35,863 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.
  644. 2017-05-11 15:19:35,864 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.
  645. 2017-05-11 15:19:35,864 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.
  646. 2017-05-11 15:19:35,864 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.
  647. 2017-05-11 15:19:35,865 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.
  648. 2017-05-11 15:19:35,881 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-wli.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  649. 2017-05-11 15:19:35,893 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.
  650. 2017-05-11 15:19:35,917 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.
  651. 2017-05-11 15:19:35,917 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.
  652. 2017-05-11 15:19:35,918 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.
  653. 2017-05-11 15:19:35,967 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  654. 2017-05-11 15:19:35,970 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"
  655. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  656. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  657. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  658. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  659. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  660. at java.lang.Thread.run(Thread.java:745)
  661. 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
  662. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  663. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  664. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  665. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  666. ... 5 more
  667.  
  668. 2017-05-11 15:19:35,973 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\"
  669. 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"}}
  670. 2017-05-11 15:19:36,015 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  671. 2017-05-11 15:19:36,016 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  672. 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"
  673. 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"
  674.  
  675. 2017-05-11 15:21:32,317 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 753ms
  676. 2017-05-11 15:21:32,320 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  677. 2017-05-11 15:21:37,157 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.
  678. 2017-05-11 15:21:37,158 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.
  679. 2017-05-11 15:21:37,158 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.
  680. 2017-05-11 15:21:37,159 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.
  681. 2017-05-11 15:21:37,159 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.
  682. 2017-05-11 15:21:37,160 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.
  683. 2017-05-11 15:21:37,160 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.
  684. 2017-05-11 15:21:37,193 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.
  685. 2017-05-11 15:21:37,204 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.
  686. 2017-05-11 15:21:37,228 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.
  687. 2017-05-11 15:21:37,229 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.
  688. 2017-05-11 15:21:37,229 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.
  689. 2017-05-11 15:21:37,238 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"
  690. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  691. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  692. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  693. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  694. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  695. at java.lang.Thread.run(Thread.java:745)
  696. Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Échec de l'analyse du descripteur XML "/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/jboss-web.xml" sur [1,38]
  697. at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:87)
  698. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  699. ... 5 more
  700. Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character (CTRL-CHAR, code 13); expected "?>" end marker
  701. at [row,col,system-id]: [1,38,"N/A"]
  702. at com.ctc.wstx.io.InputBootstrapper.reportUnexpectedChar(InputBootstrapper.java:507)
  703. at com.ctc.wstx.io.InputBootstrapper.readXmlDecl(InputBootstrapper.java:306)
  704. at com.ctc.wstx.io.StreamBootstrapper.bootstrapInput(StreamBootstrapper.java:170)
  705. at com.ctc.wstx.stax.WstxInputFactory.doCreateSR(WstxInputFactory.java:545)
  706. at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:605)
  707. at com.ctc.wstx.stax.WstxInputFactory.createSR(WstxInputFactory.java:618)
  708. at com.ctc.wstx.stax.WstxInputFactory.createXMLStreamReader(WstxInputFactory.java:324)
  709. at __redirected.__XMLInputFactory.createXMLStreamReader(__XMLInputFactory.java:134)
  710. at org.wildfly.extension.undertow.deployment.JBossWebParsingDeploymentProcessor.deploy(JBossWebParsingDeploymentProcessor.java:72)
  711. ... 6 more
  712.  
  713. 2017-05-11 15:21:37,240 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"
  714. Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYUT0027: Échec de l'analyse du descripteur XML \"/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/deployments/xa-cms-wli.war/WEB-INF/jboss-web.xml\" sur [1,38]
  715. Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character (CTRL-CHAR, code 13); expected \"?>\" end marker
  716. at [row,col,system-id]: [1,38,\"N/A\"]"}}
  717. 2017-05-11 15:21:37,286 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"
  718. 2017-05-11 15:21:37,286 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  719. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  720. 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"
  721. 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"
  722.  
  723. 2017-05-11 15:21:43,512 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 810ms
  724. 2017-05-11 15:21:43,513 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")
  725. 2017-05-11 15:21:49,224 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.
  726. 2017-05-11 15:21:49,225 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.
  727. 2017-05-11 15:21:49,226 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.
  728. 2017-05-11 15:21:49,226 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.
  729. 2017-05-11 15:21:49,227 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.
  730. 2017-05-11 15:21:49,227 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.
  731. 2017-05-11 15:21:49,227 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.
  732. 2017-05-11 15:21:49,247 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.
  733. 2017-05-11 15:21:49,261 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.
  734. 2017-05-11 15:21:49,292 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.
  735. 2017-05-11 15:21:49,292 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.
  736. 2017-05-11 15:21:49,293 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.
  737. 2017-05-11 15:21:49,335 INFO [org.jboss.as.jpa] (MSC service thread 1-5) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  738. 2017-05-11 15:21:49,337 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"
  739. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  740. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  741. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  742. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  743. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  744. at java.lang.Thread.run(Thread.java:745)
  745. Caused by: java.lang.IllegalArgumentException: WFLYEJB0059: La méthode AroundTimeout, sur la classe org.apache.openejb.monitoring.StatsInterceptor, annotée par @javax.interceptor.AroundTimeout doit renvoyer un type Objet
  746. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  747. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  748. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  749. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  750. ... 5 more
  751.  
  752. 2017-05-11 15:21:49,338 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: L'opération ("full-replace-deployment") a échoué - adresse : ([]) - description de l'échec : {"WFLYCTL0080: Les services ont échoué" => {"jboss.deployment.unit.\"xa-cms-wli.war\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"xa-cms-wli.war\".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment \"xa-cms-wli.war\"
  753. 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"}}
  754. 2017-05-11 15:21:49,366 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"
  755. 2017-05-11 15:21:49,367 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  756. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-wli.war".PARSE
  757. 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"
  758. 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"
  759.  
  760. 2017-05-11 15:23:08,291 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  761. 2017-05-11 15:23:08,303 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  762. 2017-05-11 15:23:08,588 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 72) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  763. 2017-05-11 15:23:08,596 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  764. 2017-05-11 15:23:09,264 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  765. 2017-05-11 15:23:09,504 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  766. 2017-05-11 15:23:09,504 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0019: L'hôte default-host s'arrête
  767. 2017-05-11 15:23:09,708 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 1396ms
  768. 2017-05-11 15:23:09,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  769. 2017-05-11 15:23:09,754 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  770. 2017-05-11 15:23:09,763 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  771. 2017-05-11 15:23:09,764 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
  772. 2017-05-11 15:23:09,767 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  773. 2017-05-11 15:23:09,864 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 1555ms
  774. 2017-05-11 15:23:09,880 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 1567ms
  775. 2017-05-11 15:23:10,088 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 1775ms
  776. 2017-05-11 15:23:10,094 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 1777ms
  777. 2017-05-11 15:23:13,818 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  778. 2017-05-11 15:23:14,104 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  779. 2017-05-11 15:23:14,190 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
  780. 2017-05-11 15:23:14,192 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  781. awt.toolkit = sun.awt.windows.WToolkit
  782. file.encoding = Cp1252
  783. file.encoding.pkg = sun.io
  784. file.separator = \
  785. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  786. java.awt.headless = true
  787. java.awt.printerjob = sun.awt.windows.WPrinterJob
  788. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  789. java.class.version = 52.0
  790. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  791. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  792. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  793. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  794. 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;;.
  795. java.net.preferIPv4Stack = true
  796. java.runtime.name = Java(TM) SE Runtime Environment
  797. java.runtime.version = 1.8.0_121-b13
  798. java.specification.name = Java Platform API Specification
  799. java.specification.vendor = Oracle Corporation
  800. java.specification.version = 1.8
  801. java.util.logging.manager = org.jboss.logmanager.LogManager
  802. java.vendor = Oracle Corporation
  803. java.vendor.url = http://java.oracle.com/
  804. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  805. java.version = 1.8.0_121
  806. java.vm.info = mixed mode
  807. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  808. java.vm.specification.name = Java Virtual Machine Specification
  809. java.vm.specification.vendor = Oracle Corporation
  810. java.vm.specification.version = 1.8
  811. java.vm.vendor = Oracle Corporation
  812. java.vm.version = 25.121-b13
  813. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  814. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  815. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  816. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  817. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  818. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  819. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  820. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  821. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  822. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  823. jboss.bind.address = localhost
  824. jboss.bind.address.management = localhost
  825. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  826. jboss.host.name = l82564
  827. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  828. jboss.modules.system.pkgs = org.jboss.byteman
  829. jboss.node.name = l82564
  830. jboss.qualified.host.name = l82564
  831. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  832. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  833. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  834. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  835. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  836. jboss.server.name = l82564
  837. jboss.server.persist.config = true
  838. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  839. line.separator =
  840.  
  841. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  842. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  843. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  844. org.jboss.logmanager.nocolor = true
  845. org.jboss.resolver.warning = true
  846. org.xml.sax.driver = __redirected.__XMLReaderFactory
  847. os.arch = amd64
  848. os.name = Windows 7
  849. os.version = 6.1
  850. path.separator = ;
  851. program.name = JBossTools: Red Hat JBoss EAP 7.x
  852. sun.arch.data.model = 64
  853. 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
  854. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  855. sun.cpu.endian = little
  856. sun.cpu.isalist = amd64
  857. sun.desktop = windows
  858. sun.io.unicode.encoding = UnicodeLittle
  859. 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
  860. sun.java.launcher = SUN_STANDARD
  861. sun.jnu.encoding = Cp1252
  862. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  863. sun.os.patch.level = Service Pack 1
  864. sun.rmi.dgc.client.gcInterval = 3600000
  865. sun.rmi.dgc.server.gcInterval = 3600000
  866. user.country = FR
  867. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  868. user.home = C:\Utilisateurs\A665340
  869. user.language = fr
  870. user.name = A665340
  871. user.script =
  872. user.timezone = Europe/Paris
  873. user.variant =
  874. 2017-05-11 15:23:14,193 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
  875. 2017-05-11 15:23:16,246 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 2) 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é.
  876. 2017-05-11 15:23:16,341 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-admin.war n'a pas abouti
  877. 2017-05-11 15:23:16,544 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-wli.war n'a pas abouti
  878. 2017-05-11 15:23:16,714 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  879. 2017-05-11 15:23:16,733 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  880. 2017-05-11 15:23:16,742 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  881. 2017-05-11 15:23:16,806 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)
  882. 2017-05-11 15:23:16,816 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.
  883. 2017-05-11 15:23:16,838 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  884. 2017-05-11 15:23:16,845 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  885. 2017-05-11 15:23:16,849 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  886. 2017-05-11 15:23:16,868 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  887. 2017-05-11 15:23:16,900 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  888. 2017-05-11 15:23:17,037 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)
  889. 2017-05-11 15:23:17,049 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  890. 2017-05-11 15:23:17,054 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
  891. 2017-05-11 15:23:17,069 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
  892. 2017-05-11 15:23:17,133 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  893. 2017-05-11 15:23:17,135 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  894. 2017-05-11 15:23:17,243 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Démarrage du service de nommage
  895. 2017-05-11 15:23:17,350 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  896. 2017-05-11 15:23:17,589 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.
  897. 2017-05-11 15:23:17,586 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) 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.
  898. 2017-05-11 15:23:17,599 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: '[]']
  899. 2017-05-11 15:23:17,974 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.18.Final-redhat-1
  900. 2017-05-11 15:23:18,075 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: A démarré le serveur default-server.
  901. 2017-05-11 15:23:18,167 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: L'hôte default-host démarre
  902. 2017-05-11 15:23:18,256 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  903. 2017-05-11 15:23:18,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  904. 2017-05-11 15:23:18,264 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")
  905. 2017-05-11 15:23:18,299 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
  906. 2017-05-11 15:23:18,318 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")
  907. 2017-05-11 15:23:18,320 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")
  908. 2017-05-11 15:23:19,056 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)
  909. 2017-05-11 15:23:19,444 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  910. 2017-05-11 15:23:19,775 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  911. 2017-05-11 15:23:20,801 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  912. 2017-05-11 15:23:20,803 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  913. 2017-05-11 15:23:21,411 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  914. 2017-05-11 15:23:21,449 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]
  915. 2017-05-11 15:23:22,219 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  916. 2017-05-11 15:23:22,451 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900: 2.3.3 (redhat)
  917. 2017-05-11 15:23:22,606 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  918. 2017-05-11 15:23:22,679 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  919. 2017-05-11 15:23:22,691 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  920. 2017-05-11 15:23:27,086 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]
  921. 2017-05-11 15:23:29,395 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.
  922. 2017-05-11 15:23:29,396 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.
  923. 2017-05-11 15:23:29,397 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.
  924. 2017-05-11 15:23:29,428 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.
  925. 2017-05-11 15:23:29,724 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  926. 2017-05-11 15:23:29,731 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"
  927. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  928. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  929. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  930. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  931. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  932. at java.lang.Thread.run(Thread.java:745)
  933. 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
  934. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  935. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  936. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  937. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  938. ... 5 more
  939.  
  940. 2017-05-11 15:23:30,803 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 62) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  941. 2017-05-11 15:23:30,828 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  942. 2017-05-11 15:23:32,246 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/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.
  943. 2017-05-11 15:23:32,248 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/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.
  944. 2017-05-11 15:23:32,248 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/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.
  945. 2017-05-11 15:23:32,249 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/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.
  946. 2017-05-11 15:23:32,250 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  947. 2017-05-11 15:23:32,251 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  948. 2017-05-11 15:23:32,252 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  949. 2017-05-11 15:23:32,274 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/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.
  950. 2017-05-11 15:23:32,288 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  951. 2017-05-11 15:23:32,321 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  952. 2017-05-11 15:23:32,321 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  953. 2017-05-11 15:23:32,322 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) 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.
  954. 2017-05-11 15:23:32,385 INFO [org.jboss.as.jpa] (MSC service thread 1-3) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  955. 2017-05-11 15:23:32,387 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."xa-cms-wli.war".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."xa-cms-wli.war".PARSE: WFLYSRV0153: N'a pas pu traiter la phase PARSE de deployment "xa-cms-wli.war"
  956. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  957. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  958. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  959. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  960. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  961. at java.lang.Thread.run(Thread.java:745)
  962. 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
  963. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  964. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  965. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  966. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  967. ... 5 more
  968.  
  969. 2017-05-11 15:23:32,841 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 62) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  970. 2017-05-11 15:23:32,843 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\"
  971. 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"}}
  972. 2017-05-11 15:23:32,844 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\"
  973. 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"}}
  974. 2017-05-11 15:23:32,880 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  975. 2017-05-11 15:23:32,880 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  976. 2017-05-11 15:23:32,884 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  977. 2017-05-11 15:23:32,885 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  978. 2017-05-11 15:23:32,889 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  979. 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"
  980. 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"
  981.  
  982. 2017-05-11 15:23:33,121 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  983. 2017-05-11 15:23:33,121 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  984. 2017-05-11 15:23:33,122 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 19952ms - 461 des services 758 démarré(s) (2 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  985. 2017-05-11 15:23:33,973 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 645ms
  986. 2017-05-11 15:23:34,257 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 929ms
  987. 2017-05-11 15:23:34,327 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  988. 2017-05-11 15:23:34,328 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  989. 2017-05-11 15:23:34,328 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  990. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  991. service jboss.deployment.unit."xa-cms-wli.war".PARSE
  992.  
  993. 2017-05-11 15:27:27,441 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0010: Le scanneur a détecté un contenu de fichier partiellement copié pour le déploiement C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments\xa-cms-admin.war. Les changements de déploiement ne seront pas traités avant la fin du contenu.
  994. 2017-05-11 15:27:29,589 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\98\86f494a4065f662063c12ce1919ec08975be6f\content
  995. 2017-05-11 15:27:29,594 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  996. 2017-05-11 15:27:36,000 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/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.
  997. 2017-05-11 15:27:36,001 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/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.
  998. 2017-05-11 15:27:36,001 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/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.
  999. 2017-05-11 15:27:36,018 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/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.
  1000. 2017-05-11 15:27:36,075 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1001. 2017-05-11 15:27:36,077 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"
  1002. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1003. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1004. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1005. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1006. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1007. at java.lang.Thread.run(Thread.java:745)
  1008. 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
  1009. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1010. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1011. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1012. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1013. ... 5 more
  1014.  
  1015. 2017-05-11 15:27:36,078 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\"
  1016. 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"}}
  1017. 2017-05-11 15:27:36,122 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1018. 2017-05-11 15:27:36,122 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1019. 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"
  1020.  
  1021. 2017-05-11 15:32:06,980 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0010: Le scanneur a détecté un contenu de fichier partiellement copié pour le déploiement C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\deployments\xa-cms-wli.war. Les changements de déploiement ne seront pas traités avant la fin du contenu.
  1022. 2017-05-11 15:32:11,817 INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Contenu ajouté dans location C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content\29\ccc50ca4944c117563c9358cc23c5cf0d1be66\content
  1023. 2017-05-11 15:32:11,823 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")
  1024. 2017-05-11 15:32:19,730 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1025. 2017-05-11 15:32:19,731 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1026. 2017-05-11 15:32:19,732 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-core.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1027. 2017-05-11 15:32:19,732 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1028. 2017-05-11 15:32:19,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jaxb-impl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1029. 2017-05-11 15:32:19,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1030. 2017-05-11 15:32:19,733 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry activation.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1031. 2017-05-11 15:32:19,750 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry openejb-client-4.7.3.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/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.
  1032. 2017-05-11 15:32:19,762 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/xa-cms-wli.war/WEB-INF/lib/serializer-2.7.1.jar does not point to a valid jar for a Class-Path reference.
  1033. 2017-05-11 15:32:19,796 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
  1034. 2017-05-11 15:32:19,797 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
  1035. 2017-05-11 15:32:19,797 WARN [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0059: Class Path entry serializer.jar in /C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/bin/content/xa-cms-wli.war/WEB-INF/lib/xalan-2.7.1.jar does not point to a valid jar for a Class-Path reference.
  1036. 2017-05-11 15:32:19,872 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1037. 2017-05-11 15:32:19,873 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) 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"
  1038. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1039. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1040. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1041. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1042. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1043. at java.lang.Thread.run(Thread.java:745)
  1044. 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
  1045. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1046. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1047. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1048. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1049. ... 5 more
  1050.  
  1051. 2017-05-11 15:32:19,874 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\"
  1052. 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"}}
  1053. 2017-05-11 15:32:19,934 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1054. 2017-05-11 15:32:19,935 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1055. 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"
  1056. 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"
  1057.  
  1058. 2017-05-11 15:48:03,621 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1059. 2017-05-11 15:48:03,634 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1060. 2017-05-11 15:48:03,713 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1061. 2017-05-11 15:48:03,740 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1062. 2017-05-11 15:48:04,030 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0019: L'hôte default-host s'arrête
  1063. 2017-05-11 15:48:04,067 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1064. 2017-05-11 15:48:04,079 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1065. 2017-05-11 15:48:04,488 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1066. 2017-05-11 15:48:04,513 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
  1067. 2017-05-11 15:48:04,523 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1068. 2017-05-11 15:48:04,525 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
  1069. 2017-05-11 15:48:04,527 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1070. 2017-05-11 15:48:04,563 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 918ms
  1071. 2017-05-11 15:48:04,610 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 964ms
  1072. 2017-05-11 15:48:04,990 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.war") en 1345ms
  1073. 2017-05-11 15:48:06,123 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 2478ms
  1074. 2017-05-11 15:48:06,400 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 2660ms
  1075. 2017-05-11 15:48:48,408 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1076. 2017-05-11 15:48:48,734 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1077. 2017-05-11 15:48:48,818 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
  1078. 2017-05-11 15:48:48,820 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  1079. awt.toolkit = sun.awt.windows.WToolkit
  1080. file.encoding = Cp1252
  1081. file.encoding.pkg = sun.io
  1082. file.separator = \
  1083. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1084. java.awt.headless = true
  1085. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1086. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1087. java.class.version = 52.0
  1088. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1089. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1090. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1091. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1092. 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;;.
  1093. java.net.preferIPv4Stack = true
  1094. java.runtime.name = Java(TM) SE Runtime Environment
  1095. java.runtime.version = 1.8.0_121-b13
  1096. java.specification.name = Java Platform API Specification
  1097. java.specification.vendor = Oracle Corporation
  1098. java.specification.version = 1.8
  1099. java.util.logging.manager = org.jboss.logmanager.LogManager
  1100. java.vendor = Oracle Corporation
  1101. java.vendor.url = http://java.oracle.com/
  1102. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1103. java.version = 1.8.0_121
  1104. java.vm.info = mixed mode
  1105. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1106. java.vm.specification.name = Java Virtual Machine Specification
  1107. java.vm.specification.vendor = Oracle Corporation
  1108. java.vm.specification.version = 1.8
  1109. java.vm.vendor = Oracle Corporation
  1110. java.vm.version = 25.121-b13
  1111. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1112. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1113. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1114. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1115. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1116. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1117. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1118. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1119. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1120. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1121. jboss.bind.address = localhost
  1122. jboss.bind.address.management = localhost
  1123. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1124. jboss.host.name = l82564
  1125. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1126. jboss.modules.system.pkgs = org.jboss.byteman
  1127. jboss.node.name = l82564
  1128. jboss.qualified.host.name = l82564
  1129. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1130. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1131. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1132. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1133. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1134. jboss.server.name = l82564
  1135. jboss.server.persist.config = true
  1136. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1137. line.separator =
  1138.  
  1139. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1140. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1141. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1142. org.jboss.logmanager.nocolor = true
  1143. org.jboss.resolver.warning = true
  1144. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1145. os.arch = amd64
  1146. os.name = Windows 7
  1147. os.version = 6.1
  1148. path.separator = ;
  1149. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1150. sun.arch.data.model = 64
  1151. 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
  1152. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1153. sun.cpu.endian = little
  1154. sun.cpu.isalist = amd64
  1155. sun.desktop = windows
  1156. sun.io.unicode.encoding = UnicodeLittle
  1157. 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
  1158. sun.java.launcher = SUN_STANDARD
  1159. sun.jnu.encoding = Cp1252
  1160. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1161. sun.os.patch.level = Service Pack 1
  1162. sun.rmi.dgc.client.gcInterval = 3600000
  1163. sun.rmi.dgc.server.gcInterval = 3600000
  1164. user.country = FR
  1165. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1166. user.home = C:\Utilisateurs\A665340
  1167. user.language = fr
  1168. user.name = A665340
  1169. user.script =
  1170. user.timezone = Europe/Paris
  1171. user.variant =
  1172. 2017-05-11 15:48:48,821 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
  1173. 2017-05-11 15:48:50,819 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é.
  1174. 2017-05-11 15:48:50,906 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1175. 2017-05-11 15:48:50,927 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.3.6.Final-redhat-1
  1176. 2017-05-11 15:48:50,937 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1177. 2017-05-11 15:48:51,007 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.
  1178. 2017-05-11 15:48:51,020 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
  1179. 2017-05-11 15:48:51,023 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1180. 2017-05-11 15:48:51,023 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1181. 2017-05-11 15:48:51,026 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1182. 2017-05-11 15:48:51,060 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1183. 2017-05-11 15:48:51,120 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1184. 2017-05-11 15:48:51,288 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)
  1185. 2017-05-11 15:48:51,289 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1186. 2017-05-11 15:48:51,337 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)
  1187. 2017-05-11 15:48:51,362 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Démarrage du service de pilote avec le nom de pilote = h2
  1188. 2017-05-11 15:48:51,406 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Démarrage du service de nommage
  1189. 2017-05-11 15:48:51,407 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1190. 2017-05-11 15:48:51,477 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1191. 2017-05-11 15:48:51,492 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1192. 2017-05-11 15:48:51,766 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
  1193. 2017-05-11 15:48:51,767 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) 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.
  1194. 2017-05-11 15:48:52,078 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: '[]']
  1195. 2017-05-11 15:48:52,439 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.18.Final-redhat-1
  1196. 2017-05-11 15:48:52,503 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: A démarré le serveur default-server.
  1197. 2017-05-11 15:48:52,531 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: L'hôte default-host démarre
  1198. 2017-05-11 15:48:52,625 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1199. 2017-05-11 15:48:52,747 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")
  1200. 2017-05-11 15:48:52,762 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
  1201. 2017-05-11 15:48:52,762 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")
  1202. 2017-05-11 15:48:52,765 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Lancement du déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1203. 2017-05-11 15:48:52,769 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")
  1204. 2017-05-11 15:48:53,409 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1205. 2017-05-11 15:48:53,461 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)
  1206. 2017-05-11 15:48:53,838 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1207. 2017-05-11 15:48:53,888 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1208. 2017-05-11 15:48:54,026 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1209. 2017-05-11 15:48:54,644 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1210. 2017-05-11 15:48:54,645 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1211. 2017-05-11 15:48:54,760 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1212. 2017-05-11 15:48:54,958 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1213. 2017-05-11 15:48:54,958 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1214. 2017-05-11 15:48:54,989 INFO [org.jboss.weld.Version] (MSC service thread 1-5) WELD-000900: 2.3.3 (redhat)
  1215. 2017-05-11 15:48:55,000 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1216. 2017-05-11 15:48:55,004 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1217. 2017-05-11 15:48:56,112 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 58) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1218. 2017-05-11 15:48:56,133 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1219. 2017-05-11 15:48:56,643 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1220. 2017-05-11 15:48:56,647 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 : {"WFLYCTL0180: Services avec des dépendances manquantes/non disponibles" => [
  1221. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\" [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant",
  1222. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\".__FIRST_PHASE__ [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant"
  1223. ]}
  1224. 2017-05-11 15:48:56,650 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 : {"WFLYCTL0180: Services avec des dépendances manquantes/non disponibles" => [
  1225. "jboss.persistenceunit.\"xa-cms-wli.war#xa-cms\".__FIRST_PHASE__ [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant",
  1226. "jboss.persistenceunit.\"xa-cms-wli.war#xa-cms\" [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant"
  1227. ]}
  1228. 2017-05-11 15:48:56,677 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1229. 2017-05-11 15:48:56,677 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1230. 2017-05-11 15:48:56,681 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1231. 2017-05-11 15:48:56,681 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1232. 2017-05-11 15:48:56,682 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  1233. WFLYCTL0184: Nouvelles dépendances manquantes/non complétées :
  1234. Dépendances service jboss.naming.context.java.jdbc."net.atos.wli.web.cms.xa.DB" (manquantes) : [service jboss.persistenceunit."xa-cms-admin.war#xa-cms", service jboss.persistenceunit."xa-cms-admin.war#xa-cms".__FIRST_PHASE__, service jboss.persistenceunit."xa-cms-wli.war#xa-cms", service jboss.persistenceunit."xa-cms-wli.war#xa-cms".__FIRST_PHASE__]
  1235.  
  1236. 2017-05-11 15:48:56,898 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1237. 2017-05-11 15:48:56,899 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1238. 2017-05-11 15:48:56,900 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 8977ms - 575 des services 902 démarré(s) (18 services ont échoué ou manquent de dépendances, 415 services sont lents, passifs ou à la demande)
  1239. 2017-05-11 15:48:57,142 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 146ms
  1240. 2017-05-11 15:48:57,145 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 148ms
  1241. 2017-05-11 15:48:57,256 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1242. 2017-05-11 15:48:57,258 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1243. 2017-05-11 15:48:57,267 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1244. WFLYCTL0184: Nouvelles dépendances manquantes/non complétées :
  1245. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START]
  1246. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1247. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START]
  1248. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1249. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  1250. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1251. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  1252. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1253. Dépendances service jboss.deployment.unit."xa-cms-admin.war".ee.ComponentRegistry (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1254. Dépendances service jboss.deployment.unit."xa-cms-admin.war".jndiDependencyService (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START]
  1255. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START]
  1256. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1257. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  1258. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1259. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  1260. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1261. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  1262. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1263. Dépendances service jboss.deployment.unit."xa-cms-wli.war".ee.ComponentRegistry (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1264. Dépendances service jboss.deployment.unit."xa-cms-wli.war".jndiDependencyService (manquantes) : [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."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  1265. Dépendances service jboss.persistenceunit."xa-cms-admin.war#xa-cms" (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, WFLYCTL0208: ... and 4 more ]
  1266. Dépendances service jboss.persistenceunit."xa-cms-wli.war#xa-cms" (manquantes) : [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.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, WFLYCTL0208: ... and 4 more ]
  1267. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService]
  1268. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin]
  1269. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.codec (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1270. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.session (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1271. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService]
  1272. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1273. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.codec (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1274. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.session (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1275. Dépendances service org.wildfly.request-controller.control-point."xa-cms-admin.war".undertow (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1276. Dépendances service org.wildfly.request-controller.control-point."xa-cms-wli.war".undertow (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1277.  
  1278. 2017-05-11 15:58:01,219 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")
  1279. 2017-05-11 15:58:01,271 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1280. 2017-05-11 15:58:01,434 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 : {"WFLYCTL0180: Services avec des dépendances manquantes/non disponibles" => [
  1281. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\" [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant",
  1282. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\".__FIRST_PHASE__ [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant"
  1283. ]}
  1284. 2017-05-11 15:58:01,511 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1285. 2017-05-11 15:58:01,514 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1286. WFLYCTL0185: Services nouvellement modifiés :
  1287. service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".CREATE (nouvellement disponible)
  1288. service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START (nouvellement disponible)
  1289. service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".CREATE (nouvellement disponible)
  1290. service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START (nouvellement disponible)
  1291. service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (nouvellement disponible)
  1292. service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (nouvellement disponible)
  1293. service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (nouvellement disponible)
  1294. service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (nouvellement disponible)
  1295. service jboss.deployment.unit."xa-cms-admin.war".ee.ComponentRegistry (nouvellement disponible)
  1296. service jboss.deployment.unit."xa-cms-admin.war".jndiDependencyService (nouvellement disponible)
  1297. service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".CREATE (plus requis actuellement)
  1298. service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START (plus requis actuellement)
  1299. service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".CREATE (plus requis actuellement)
  1300. service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START (plus requis actuellement)
  1301. service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (plus requis actuellement)
  1302. service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (plus requis actuellement)
  1303. service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (plus requis actuellement)
  1304. service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (plus requis actuellement)
  1305. service jboss.deployment.unit."xa-cms-wli.war".ee.ComponentRegistry (plus requis actuellement)
  1306. service jboss.deployment.unit."xa-cms-wli.war".jndiDependencyService (plus requis actuellement)
  1307. service jboss.persistenceunit."xa-cms-admin.war#xa-cms" (nouvellement disponible)
  1308. service jboss.persistenceunit."xa-cms-wli.war#xa-cms" (plus requis actuellement)
  1309. service jboss.undertow.deployment.default-server.default-host./xa-cms-admin (nouvellement disponible)
  1310. service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService (nouvellement disponible)
  1311. service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.codec (nouvellement disponible)
  1312. service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.session (nouvellement disponible)
  1313. service jboss.undertow.deployment.default-server.default-host./xa-cms-wli (plus requis actuellement)
  1314. service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService (plus requis actuellement)
  1315. service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.codec (plus requis actuellement)
  1316. service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.session (plus requis actuellement)
  1317. service org.wildfly.request-controller.control-point."xa-cms-admin.war".undertow (nouvellement disponible)
  1318. service org.wildfly.request-controller.control-point."xa-cms-wli.war".undertow (plus requis actuellement)
  1319.  
  1320. 2017-05-11 15:58:29,913 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1321. 2017-05-11 15:58:29,921 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1322. 2017-05-11 15:58:29,988 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1323. 2017-05-11 15:58:29,989 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1324. 2017-05-11 15:58:30,014 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0019: L'hôte default-host s'arrête
  1325. 2017-05-11 15:58:30,018 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1326. 2017-05-11 15:58:30,022 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1327. 2017-05-11 15:58:30,022 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 88ms
  1328. 2017-05-11 15:58:30,082 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1329. 2017-05-11 15:58:30,111 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1330. 2017-05-11 15:58:30,112 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
  1331. 2017-05-11 15:58:30,114 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1332. 2017-05-11 15:58:30,126 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
  1333. 2017-05-11 15:58:30,198 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 270ms
  1334. 2017-05-11 15:58:30,224 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 283ms
  1335. 2017-05-11 15:58:30,236 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 297ms
  1336. 2017-05-11 15:58:32,617 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1337. 2017-05-11 15:58:32,912 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1338. 2017-05-11 15:58:33,050 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
  1339. 2017-05-11 15:58:33,052 DEBUG [org.jboss.as.config] (MSC service thread 1-8) Propriétés de système configurées :
  1340. awt.toolkit = sun.awt.windows.WToolkit
  1341. file.encoding = Cp1252
  1342. file.encoding.pkg = sun.io
  1343. file.separator = \
  1344. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1345. java.awt.headless = true
  1346. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1347. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1348. java.class.version = 52.0
  1349. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1350. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1351. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1352. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1353. 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;;.
  1354. java.net.preferIPv4Stack = true
  1355. java.runtime.name = Java(TM) SE Runtime Environment
  1356. java.runtime.version = 1.8.0_121-b13
  1357. java.specification.name = Java Platform API Specification
  1358. java.specification.vendor = Oracle Corporation
  1359. java.specification.version = 1.8
  1360. java.util.logging.manager = org.jboss.logmanager.LogManager
  1361. java.vendor = Oracle Corporation
  1362. java.vendor.url = http://java.oracle.com/
  1363. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1364. java.version = 1.8.0_121
  1365. java.vm.info = mixed mode
  1366. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1367. java.vm.specification.name = Java Virtual Machine Specification
  1368. java.vm.specification.vendor = Oracle Corporation
  1369. java.vm.specification.version = 1.8
  1370. java.vm.vendor = Oracle Corporation
  1371. java.vm.version = 25.121-b13
  1372. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1373. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1374. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1375. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1376. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1377. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1378. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1379. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1380. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1381. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1382. jboss.bind.address = localhost
  1383. jboss.bind.address.management = localhost
  1384. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1385. jboss.host.name = l82564
  1386. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1387. jboss.modules.system.pkgs = org.jboss.byteman
  1388. jboss.node.name = l82564
  1389. jboss.qualified.host.name = l82564
  1390. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1391. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1392. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1393. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1394. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1395. jboss.server.name = l82564
  1396. jboss.server.persist.config = true
  1397. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1398. line.separator =
  1399.  
  1400. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1401. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1402. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1403. org.jboss.logmanager.nocolor = true
  1404. org.jboss.resolver.warning = true
  1405. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1406. os.arch = amd64
  1407. os.name = Windows 7
  1408. os.version = 6.1
  1409. path.separator = ;
  1410. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1411. sun.arch.data.model = 64
  1412. 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
  1413. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1414. sun.cpu.endian = little
  1415. sun.cpu.isalist = amd64
  1416. sun.desktop = windows
  1417. sun.io.unicode.encoding = UnicodeLittle
  1418. 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
  1419. sun.java.launcher = SUN_STANDARD
  1420. sun.jnu.encoding = Cp1252
  1421. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1422. sun.os.patch.level = Service Pack 1
  1423. sun.rmi.dgc.client.gcInterval = 3600000
  1424. sun.rmi.dgc.server.gcInterval = 3600000
  1425. user.country = FR
  1426. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1427. user.home = C:\Utilisateurs\A665340
  1428. user.language = fr
  1429. user.name = A665340
  1430. user.script =
  1431. user.timezone = Europe/Paris
  1432. user.variant =
  1433. 2017-05-11 15:58:33,054 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
  1434. 2017-05-11 15:58:36,151 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é.
  1435. 2017-05-11 15:58:36,181 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-admin.war n'a pas abouti
  1436. 2017-05-11 15:58:36,209 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: La nouvelle tentative de déploiement xa-cms-wli.war n'a pas abouti
  1437. 2017-05-11 15:58:36,262 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1438. 2017-05-11 15:58:36,285 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.3.6.Final-redhat-1
  1439. 2017-05-11 15:58:36,292 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1440. 2017-05-11 15:58:36,376 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1441. 2017-05-11 15:58:36,392 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
  1442. 2017-05-11 15:58:36,399 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.
  1443. 2017-05-11 15:58:36,401 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1444. 2017-05-11 15:58:36,408 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1445. 2017-05-11 15:58:36,425 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1446. 2017-05-11 15:58:36,473 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1447. 2017-05-11 15:58:36,515 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1448. 2017-05-11 15:58:36,680 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1449. 2017-05-11 15:58:36,681 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1450. 2017-05-11 15:58:36,683 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)
  1451. 2017-05-11 15:58:36,742 INFO [org.jboss.as.naming] (MSC service thread 1-3) WFLYNAM0003: Démarrage du service de nommage
  1452. 2017-05-11 15:58:36,763 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1453. 2017-05-11 15:58:36,801 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)
  1454. 2017-05-11 15:58:36,804 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
  1455. 2017-05-11 15:58:36,882 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: '[]']
  1456. 2017-05-11 15:58:36,947 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: A démarré le serveur default-server.
  1457. 2017-05-11 15:58:36,993 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: L'hôte default-host démarre
  1458. 2017-05-11 15:58:37,049 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final-redhat-1
  1459. 2017-05-11 15:58:37,251 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1460. 2017-05-11 15:58:37,280 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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.
  1461. 2017-05-11 15:58:37,291 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.
  1462. 2017-05-11 15:58:37,895 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1463. 2017-05-11 15:58:38,097 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Lancement du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1464. 2017-05-11 15:58:38,104 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")
  1465. 2017-05-11 15:58:38,106 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")
  1466. 2017-05-11 15:58:38,109 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")
  1467. 2017-05-11 15:58:38,134 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
  1468. 2017-05-11 15:58:38,915 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1469. 2017-05-11 15:58:39,032 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)
  1470. 2017-05-11 15:58:39,189 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1471. 2017-05-11 15:58:39,186 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1472. 2017-05-11 15:58:39,919 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1473. 2017-05-11 15:58:39,918 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1474. 2017-05-11 15:58:39,983 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1475. 2017-05-11 15:58:40,179 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1476. 2017-05-11 15:58:40,194 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1477. 2017-05-11 15:58:40,218 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 2.3.3 (redhat)
  1478. 2017-05-11 15:58:40,234 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1479. 2017-05-11 15:58:40,237 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1480. 2017-05-11 15:58:40,953 INFO [org.jboss.as.protocol] (management task-7) WFLYPRT0057: tâches annulées en interrompant la chaîne Thread[management-handler-thread - 3,5,management-handler-thread]
  1481. 2017-05-11 15:58:41,515 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 58) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1482. 2017-05-11 15:58:41,532 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1483. 2017-05-11 15:58:42,051 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1484. 2017-05-11 15:58:42,056 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 : {"WFLYCTL0180: Services avec des dépendances manquantes/non disponibles" => [
  1485. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\" [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant",
  1486. "jboss.persistenceunit.\"xa-cms-admin.war#xa-cms\".__FIRST_PHASE__ [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant"
  1487. ]}
  1488. 2017-05-11 15:58:42,058 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 : {"WFLYCTL0180: Services avec des dépendances manquantes/non disponibles" => [
  1489. "jboss.persistenceunit.\"xa-cms-wli.war#xa-cms\" [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant",
  1490. "jboss.persistenceunit.\"xa-cms-wli.war#xa-cms\".__FIRST_PHASE__ [jboss.naming.context.java.jdbc.\"net.atos.wli.web.cms.xa.DB\"] est manquant"
  1491. ]}
  1492. 2017-05-11 15:58:42,086 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1493. 2017-05-11 15:58:42,086 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1494. 2017-05-11 15:58:42,087 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1495. 2017-05-11 15:58:42,088 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1496. 2017-05-11 15:58:42,091 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  1497. WFLYCTL0184: Nouvelles dépendances manquantes/non complétées :
  1498. Dépendances service jboss.naming.context.java.jdbc."net.atos.wli.web.cms.xa.DB" (manquantes) : [service jboss.persistenceunit."xa-cms-admin.war#xa-cms", service jboss.persistenceunit."xa-cms-admin.war#xa-cms".__FIRST_PHASE__, service jboss.persistenceunit."xa-cms-wli.war#xa-cms", service jboss.persistenceunit."xa-cms-wli.war#xa-cms".__FIRST_PHASE__]
  1499.  
  1500. 2017-05-11 15:58:42,314 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1501. 2017-05-11 15:58:42,315 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1502. 2017-05-11 15:58:42,315 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 10443ms - 575 des services 902 démarré(s) (18 services ont échoué ou manquent de dépendances, 415 services sont lents, passifs ou à la demande)
  1503. 2017-05-11 15:58:42,468 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 68ms
  1504. 2017-05-11 15:58:42,471 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 71ms
  1505. 2017-05-11 15:58:42,582 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Annulation du déploiement de "xa-cms-wli.war" (runtime-name: "xa-cms-wli.war")
  1506. 2017-05-11 15:58:42,582 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1507. 2017-05-11 15:58:42,585 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  1508. WFLYCTL0184: Nouvelles dépendances manquantes/non complétées :
  1509. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START]
  1510. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1511. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START]
  1512. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1513. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  1514. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1515. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  1516. Dépendances service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin, service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1517. Dépendances service jboss.deployment.unit."xa-cms-admin.war".ee.ComponentRegistry (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1518. Dépendances service jboss.deployment.unit."xa-cms-admin.war".jndiDependencyService (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."com.sun.faces.config.ConfigureListener".START]
  1519. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START]
  1520. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."com.sun.faces.config.ConfigureListener".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1521. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  1522. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1523. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
  1524. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1525. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
  1526. Dépendances service jboss.deployment.unit."xa-cms-wli.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1527. Dépendances service jboss.deployment.unit."xa-cms-wli.war".ee.ComponentRegistry (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1528. Dépendances service jboss.deployment.unit."xa-cms-wli.war".jndiDependencyService (manquantes) : [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."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-wli.war".component."javax.faces.webapp.FacetTag".START]
  1529. Dépendances service jboss.persistenceunit."xa-cms-admin.war#xa-cms" (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.faces.webapp.FacetTag".START, service jboss.deployment.unit."xa-cms-admin.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START, service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService, WFLYCTL0208: ... and 4 more ]
  1530. Dépendances service jboss.persistenceunit."xa-cms-wli.war#xa-cms" (manquantes) : [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.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService, service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService, WFLYCTL0208: ... and 4 more ]
  1531. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin (manquantes) : [service jboss.deployment.unit."xa-cms-admin.war".deploymentCompleteService]
  1532. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin]
  1533. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.codec (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1534. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.session (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1535. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli (manquantes) : [service jboss.deployment.unit."xa-cms-wli.war".deploymentCompleteService]
  1536. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli]
  1537. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.codec (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1538. Dépendances service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.session (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1539. Dépendances service org.wildfly.request-controller.control-point."xa-cms-admin.war".undertow (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-admin.UndertowDeploymentInfoService]
  1540. Dépendances service org.wildfly.request-controller.control-point."xa-cms-wli.war".undertow (manquantes) : [service jboss.undertow.deployment.default-server.default-host./xa-cms-wli.UndertowDeploymentInfoService]
  1541.  
  1542. 2017-05-11 15:59:04,565 INFO [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0236: Suspending server with no timeout.
  1543. 2017-05-11 15:59:04,574 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1544. 2017-05-11 15:59:04,624 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1545. 2017-05-11 15:59:04,625 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1546. 2017-05-11 15:59:04,679 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0019: L'hôte default-host s'arrête
  1547. 2017-05-11 15:59:04,682 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1548. 2017-05-11 15:59:05,225 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1549. 2017-05-11 15:59:05,284 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1550. 2017-05-11 15:59:05,373 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 780ms
  1551. 2017-05-11 15:59:05,389 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 802ms
  1552. 2017-05-11 15:59:05,392 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1553. 2017-05-11 15:59:05,396 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
  1554. 2017-05-11 15:59:05,398 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1555. 2017-05-11 15:59:05,408 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0019: Arrêt du service de pilote avec le nom de pilote = h2
  1556. 2017-05-11 15:59:05,450 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 849ms
  1557. 2017-05-11 16:00:15,211 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1558. 2017-05-11 16:00:15,545 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1559. 2017-05-11 16:00:15,630 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
  1560. 2017-05-11 16:00:15,632 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  1561. awt.toolkit = sun.awt.windows.WToolkit
  1562. file.encoding = Cp1252
  1563. file.encoding.pkg = sun.io
  1564. file.separator = \
  1565. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1566. java.awt.headless = true
  1567. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1568. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1569. java.class.version = 52.0
  1570. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1571. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1572. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1573. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1574. 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;;.
  1575. java.net.preferIPv4Stack = true
  1576. java.runtime.name = Java(TM) SE Runtime Environment
  1577. java.runtime.version = 1.8.0_121-b13
  1578. java.specification.name = Java Platform API Specification
  1579. java.specification.vendor = Oracle Corporation
  1580. java.specification.version = 1.8
  1581. java.util.logging.manager = org.jboss.logmanager.LogManager
  1582. java.vendor = Oracle Corporation
  1583. java.vendor.url = http://java.oracle.com/
  1584. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1585. java.version = 1.8.0_121
  1586. java.vm.info = mixed mode
  1587. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1588. java.vm.specification.name = Java Virtual Machine Specification
  1589. java.vm.specification.vendor = Oracle Corporation
  1590. java.vm.specification.version = 1.8
  1591. java.vm.vendor = Oracle Corporation
  1592. java.vm.version = 25.121-b13
  1593. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1594. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1595. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1596. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1597. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1598. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1599. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1600. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1601. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1602. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1603. jboss.bind.address = localhost
  1604. jboss.bind.address.management = localhost
  1605. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1606. jboss.host.name = l82564
  1607. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1608. jboss.modules.system.pkgs = org.jboss.byteman
  1609. jboss.node.name = l82564
  1610. jboss.qualified.host.name = l82564
  1611. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1612. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1613. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1614. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1615. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1616. jboss.server.name = l82564
  1617. jboss.server.persist.config = true
  1618. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1619. line.separator =
  1620.  
  1621. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1622. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1623. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1624. org.jboss.logmanager.nocolor = true
  1625. org.jboss.resolver.warning = true
  1626. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1627. os.arch = amd64
  1628. os.name = Windows 7
  1629. os.version = 6.1
  1630. path.separator = ;
  1631. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1632. sun.arch.data.model = 64
  1633. 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
  1634. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1635. sun.cpu.endian = little
  1636. sun.cpu.isalist = amd64
  1637. sun.desktop = windows
  1638. sun.io.unicode.encoding = UnicodeLittle
  1639. 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
  1640. sun.java.launcher = SUN_STANDARD
  1641. sun.jnu.encoding = Cp1252
  1642. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1643. sun.os.patch.level = Service Pack 1
  1644. sun.rmi.dgc.client.gcInterval = 3600000
  1645. sun.rmi.dgc.server.gcInterval = 3600000
  1646. user.country = FR
  1647. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1648. user.home = C:\Utilisateurs\A665340
  1649. user.language = fr
  1650. user.name = A665340
  1651. user.script =
  1652. user.timezone = Europe/Paris
  1653. user.variant =
  1654. 2017-05-11 16:00:15,632 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
  1655. 2017-05-11 16:00:17,614 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 15) 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é.
  1656. 2017-05-11 16:00:17,879 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"
  1657. 2017-05-11 16:00:17,885 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.
  1658. 2017-05-11 16:00:17,888 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1659. 2017-05-11 16:00:17,905 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 10ms
  1660. 2017-05-11 16:01:08,639 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1661. 2017-05-11 16:01:09,028 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1662. 2017-05-11 16:01:09,117 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
  1663. 2017-05-11 16:01:09,118 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  1664. awt.toolkit = sun.awt.windows.WToolkit
  1665. file.encoding = Cp1252
  1666. file.encoding.pkg = sun.io
  1667. file.separator = \
  1668. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1669. java.awt.headless = true
  1670. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1671. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1672. java.class.version = 52.0
  1673. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1674. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1675. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1676. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1677. 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;;.
  1678. java.net.preferIPv4Stack = true
  1679. java.runtime.name = Java(TM) SE Runtime Environment
  1680. java.runtime.version = 1.8.0_121-b13
  1681. java.specification.name = Java Platform API Specification
  1682. java.specification.vendor = Oracle Corporation
  1683. java.specification.version = 1.8
  1684. java.util.logging.manager = org.jboss.logmanager.LogManager
  1685. java.vendor = Oracle Corporation
  1686. java.vendor.url = http://java.oracle.com/
  1687. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1688. java.version = 1.8.0_121
  1689. java.vm.info = mixed mode
  1690. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1691. java.vm.specification.name = Java Virtual Machine Specification
  1692. java.vm.specification.vendor = Oracle Corporation
  1693. java.vm.specification.version = 1.8
  1694. java.vm.vendor = Oracle Corporation
  1695. java.vm.version = 25.121-b13
  1696. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1697. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1698. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1699. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1700. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1701. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1702. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1703. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1704. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1705. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1706. jboss.bind.address = localhost
  1707. jboss.bind.address.management = localhost
  1708. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1709. jboss.host.name = l82564
  1710. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1711. jboss.modules.system.pkgs = org.jboss.byteman
  1712. jboss.node.name = l82564
  1713. jboss.qualified.host.name = l82564
  1714. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1715. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1716. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1717. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1718. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1719. jboss.server.name = l82564
  1720. jboss.server.persist.config = true
  1721. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1722. line.separator =
  1723.  
  1724. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1725. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1726. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1727. org.jboss.logmanager.nocolor = true
  1728. org.jboss.resolver.warning = true
  1729. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1730. os.arch = amd64
  1731. os.name = Windows 7
  1732. os.version = 6.1
  1733. path.separator = ;
  1734. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1735. sun.arch.data.model = 64
  1736. 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
  1737. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1738. sun.cpu.endian = little
  1739. sun.cpu.isalist = amd64
  1740. sun.desktop = windows
  1741. sun.io.unicode.encoding = UnicodeLittle
  1742. 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
  1743. sun.java.launcher = SUN_STANDARD
  1744. sun.jnu.encoding = Cp1252
  1745. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1746. sun.os.patch.level = Service Pack 1
  1747. sun.rmi.dgc.client.gcInterval = 3600000
  1748. sun.rmi.dgc.server.gcInterval = 3600000
  1749. user.country = FR
  1750. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1751. user.home = C:\Utilisateurs\A665340
  1752. user.language = fr
  1753. user.name = A665340
  1754. user.script =
  1755. user.timezone = Europe/Paris
  1756. user.variant =
  1757. 2017-05-11 16:01:09,119 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
  1758. 2017-05-11 16:01:11,175 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é.
  1759. 2017-05-11 16:01:11,217 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1760. 2017-05-11 16:01:11,250 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
  1761. 2017-05-11 16:01:11,261 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1762. 2017-05-11 16:01:11,353 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1763. 2017-05-11 16:01:11,373 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.
  1764. 2017-05-11 16:01:11,380 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
  1765. 2017-05-11 16:01:11,387 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1766. 2017-05-11 16:01:11,419 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1767. 2017-05-11 16:01:11,422 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1768. 2017-05-11 16:01:11,437 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1769. 2017-05-11 16:01:11,438 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1770. 2017-05-11 16:01:11,600 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)
  1771. 2017-05-11 16:01:11,638 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)
  1772. 2017-05-11 16:01:11,644 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Démarrage du service de nommage
  1773. 2017-05-11 16:01:11,650 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1774. 2017-05-11 16:01:11,650 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1775. 2017-05-11 16:01:11,653 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
  1776. 2017-05-11 16:01:11,655 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1777. 2017-05-11 16:01:11,913 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: '[]']
  1778. 2017-05-11 16:01:12,008 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.
  1779. 2017-05-11 16:01:12,008 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.
  1780. 2017-05-11 16:01:12,314 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final-redhat-1
  1781. 2017-05-11 16:01:12,326 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: A démarré le serveur default-server.
  1782. 2017-05-11 16:01:12,378 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0018: L'hôte default-host démarre
  1783. 2017-05-11 16:01:12,492 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1784. 2017-05-11 16:01:12,695 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")
  1785. 2017-05-11 16:01:12,700 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
  1786. 2017-05-11 16:01:12,701 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")
  1787. 2017-05-11 16:01:13,390 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)
  1788. 2017-05-11 16:01:13,507 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1789. 2017-05-11 16:01:13,587 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1790. 2017-05-11 16:01:14,359 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1791. 2017-05-11 16:01:14,359 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1792. 2017-05-11 16:01:14,453 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1793. 2017-05-11 16:01:14,698 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1794. 2017-05-11 16:01:14,707 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1795. 2017-05-11 16:01:14,744 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.3 (redhat)
  1796. 2017-05-11 16:01:14,789 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1797. 2017-05-11 16:01:14,792 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1798. 2017-05-11 16:01:15,988 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 60) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1799. 2017-05-11 16:01:16,005 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 59) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1800. 2017-05-11 16:01:16,527 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1801. 2017-05-11 16:01:16,563 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1802. 2017-05-11 16:01:16,564 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1803. 2017-05-11 16:01:16,733 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1804. 2017-05-11 16:01:16,733 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1805. 2017-05-11 16:01:16,734 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 8814ms - 455 sur 750 services ont démarré (393 services sont passifs ou à la demande)
  1806. 2017-05-11 16:02:50,541 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  1807. 2017-05-11 16:02:50,563 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  1808. 2017-05-11 16:02:50,746 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  1809. 2017-05-11 16:02:50,751 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  1810. 2017-05-11 16:02:50,798 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0019: L'hôte default-host s'arrête
  1811. 2017-05-11 16:02:50,800 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  1812. 2017-05-11 16:02:50,827 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  1813. 2017-05-11 16:02:50,874 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  1814. 2017-05-11 16:02:50,880 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
  1815. 2017-05-11 16:02:50,951 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 373ms
  1816. 2017-05-11 16:02:50,986 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 404ms
  1817. 2017-05-11 16:02:50,992 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  1818. 2017-05-11 16:02:50,998 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
  1819. 2017-05-11 16:02:51,000 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  1820. 2017-05-11 16:02:51,028 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 448ms
  1821. 2017-05-11 16:03:28,408 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  1822. 2017-05-11 16:03:28,740 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  1823. 2017-05-11 16:03:28,825 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
  1824. 2017-05-11 16:03:28,827 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Propriétés de système configurées :
  1825. awt.toolkit = sun.awt.windows.WToolkit
  1826. file.encoding = Cp1252
  1827. file.encoding.pkg = sun.io
  1828. file.separator = \
  1829. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  1830. java.awt.headless = true
  1831. java.awt.printerjob = sun.awt.windows.WPrinterJob
  1832. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  1833. java.class.version = 52.0
  1834. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  1835. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  1836. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  1837. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  1838. 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;;.
  1839. java.net.preferIPv4Stack = true
  1840. java.runtime.name = Java(TM) SE Runtime Environment
  1841. java.runtime.version = 1.8.0_121-b13
  1842. java.specification.name = Java Platform API Specification
  1843. java.specification.vendor = Oracle Corporation
  1844. java.specification.version = 1.8
  1845. java.util.logging.manager = org.jboss.logmanager.LogManager
  1846. java.vendor = Oracle Corporation
  1847. java.vendor.url = http://java.oracle.com/
  1848. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  1849. java.version = 1.8.0_121
  1850. java.vm.info = mixed mode
  1851. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  1852. java.vm.specification.name = Java Virtual Machine Specification
  1853. java.vm.specification.vendor = Oracle Corporation
  1854. java.vm.specification.version = 1.8
  1855. java.vm.vendor = Oracle Corporation
  1856. java.vm.version = 25.121-b13
  1857. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  1858. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  1859. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  1860. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  1861. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  1862. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  1863. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  1864. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  1865. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  1866. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  1867. jboss.bind.address = localhost
  1868. jboss.bind.address.management = localhost
  1869. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  1870. jboss.host.name = l82564
  1871. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  1872. jboss.modules.system.pkgs = org.jboss.byteman
  1873. jboss.node.name = l82564
  1874. jboss.qualified.host.name = l82564
  1875. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  1876. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  1877. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  1878. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  1879. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  1880. jboss.server.name = l82564
  1881. jboss.server.persist.config = true
  1882. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  1883. line.separator =
  1884.  
  1885. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  1886. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  1887. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  1888. org.jboss.logmanager.nocolor = true
  1889. org.jboss.resolver.warning = true
  1890. org.xml.sax.driver = __redirected.__XMLReaderFactory
  1891. os.arch = amd64
  1892. os.name = Windows 7
  1893. os.version = 6.1
  1894. path.separator = ;
  1895. program.name = JBossTools: Red Hat JBoss EAP 7.x
  1896. sun.arch.data.model = 64
  1897. 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
  1898. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  1899. sun.cpu.endian = little
  1900. sun.cpu.isalist = amd64
  1901. sun.desktop = windows
  1902. sun.io.unicode.encoding = UnicodeLittle
  1903. 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
  1904. sun.java.launcher = SUN_STANDARD
  1905. sun.jnu.encoding = Cp1252
  1906. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  1907. sun.os.patch.level = Service Pack 1
  1908. sun.rmi.dgc.client.gcInterval = 3600000
  1909. sun.rmi.dgc.server.gcInterval = 3600000
  1910. user.country = FR
  1911. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  1912. user.home = C:\Utilisateurs\A665340
  1913. user.language = fr
  1914. user.name = A665340
  1915. user.script =
  1916. user.timezone = Europe/Paris
  1917. user.variant =
  1918. 2017-05-11 16:03:28,828 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
  1919. 2017-05-11 16:03:30,905 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é.
  1920. 2017-05-11 16:03:31,066 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Création d'un service de gestion http à l'aide de socket-binding (management-http)
  1921. 2017-05-11 16:03:31,084 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.3.6.Final-redhat-1
  1922. 2017-05-11 16:03:31,091 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
  1923. 2017-05-11 16:03:31,171 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Démarrage du sous-système de nommage
  1924. 2017-05-11 16:03:31,206 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: A activé les implémentations JSF suivantes : [main]
  1925. 2017-05-11 16:03:31,225 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activation de l'extension WebServices
  1926. 2017-05-11 16:03:31,226 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activation du sous-système Infinispan
  1927. 2017-05-11 16:03:31,235 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activation du sous-système de sécurité
  1928. 2017-05-11 16:03:31,250 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.
  1929. 2017-05-11 16:03:31,252 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
  1930. 2017-05-11 16:03:31,269 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Session mail liée [java:jboss/mail/Default]
  1931. 2017-05-11 16:03:31,270 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Démarrage du service de nommage
  1932. 2017-05-11 16:03:31,275 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Version PicketBox actuelle=4.9.6.Final-redhat-1
  1933. 2017-05-11 16:03:31,412 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1934. 2017-05-11 16:03:31,414 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Démarrage 1.3.21.Final-redhat-1 d'Undertow
  1935. 2017-05-11 16:03:31,417 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)
  1936. 2017-05-11 16:03:31,452 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)
  1937. 2017-05-11 16:03:31,473 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
  1938. 2017-05-11 16:03:31,622 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: '[]']
  1939. 2017-05-11 16:03:31,829 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.
  1940. 2017-05-11 16:03:31,830 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.
  1941. 2017-05-11 16:03:32,287 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.18.Final-redhat-1
  1942. 2017-05-11 16:03:32,308 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: A démarré le serveur default-server.
  1943. 2017-05-11 16:03:32,311 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: L'hôte default-host démarre
  1944. 2017-05-11 16:03:32,384 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP écouteur default écoutant sur 127.0.0.1:8080
  1945. 2017-05-11 16:03:32,645 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")
  1946. 2017-05-11 16:03:32,657 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
  1947. 2017-05-11 16:03:32,684 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")
  1948. 2017-05-11 16:03:32,831 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")
  1949. 2017-05-11 16:03:33,361 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)
  1950. 2017-05-11 16:03:33,507 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Source de données liée [java:jboss/datasources/ExampleDS]
  1951. 2017-05-11 16:03:33,761 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
  1952. 2017-05-11 16:03:34,791 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0003: Traitement du déploiement Weld jboss-numberguess.war
  1953. 2017-05-11 16:03:34,846 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Traitement du déploiement Weld jboss-helloworld.war
  1954. 2017-05-11 16:03:34,971 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.4.Final-redhat-1
  1955. 2017-05-11 16:03:35,255 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-helloworld.war
  1956. 2017-05-11 16:03:35,360 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) WFLYWELD0006: Démarrage des services pour le déploiement CDI : jboss-numberguess.war
  1957. 2017-05-11 16:03:35,365 INFO [org.jboss.weld.Version] (MSC service thread 1-8) WELD-000900: 2.3.3 (redhat)
  1958. 2017-05-11 16:03:35,494 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-helloworld.war
  1959. 2017-05-11 16:03:35,495 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Lancement du service Weld pour le déploiement jboss-numberguess.war
  1960. 2017-05-11 16:03:38,054 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 58) Initialisation de Mojarra 2.2.12-jbossorg-2 pour le contexte «/jboss-numberguess»
  1961. 2017-05-11 16:03:39,171 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Contexte web enregistré : /jboss-numberguess
  1962. 2017-05-11 16:03:39,212 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 60) WFLYUT0021: Contexte web enregistré : /jboss-helloworld
  1963. 2017-05-11 16:03:39,870 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.
  1964. 2017-05-11 16:03:39,871 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.
  1965. 2017-05-11 16:03:39,872 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.
  1966. 2017-05-11 16:03:39,889 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.
  1967. 2017-05-11 16:03:40,003 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  1968. 2017-05-11 16:03:40,007 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"
  1969. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  1970. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  1971. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  1972. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  1973. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  1974. at java.lang.Thread.run(Thread.java:745)
  1975. 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
  1976. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  1977. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  1978. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  1979. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  1980. ... 5 more
  1981.  
  1982. 2017-05-11 16:03:40,009 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\"
  1983. 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"}}
  1984. 2017-05-11 16:03:40,044 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-numberguess.war" (runtime-name: "jboss-numberguess.war")
  1985. 2017-05-11 16:03:40,044 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Déploiement de "jboss-helloworld.war" (runtime-name: "jboss-helloworld.war")
  1986. 2017-05-11 16:03:40,073 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1987. 2017-05-11 16:03:40,085 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Rapport de statut de service
  1988. 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"
  1989.  
  1990. 2017-05-11 16:03:40,247 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: L'interface de gestion http écoute sur http://127.0.0.1:9990/management
  1991. 2017-05-11 16:03:40,248 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: La console d'administration écoute sur http://127.0.0.1:9990
  1992. 2017-05-11 16:03:40,248 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 12399ms - 458 des services 754 démarré(s) (1 services ont échoué ou manquent de dépendances, 393 services sont lents, passifs ou à la demande)
  1993. 2017-05-11 16:03:40,971 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Arrêt du déploiement de xa-cms-admin.war (runtime-name: "xa-cms-admin.war") en 563ms
  1994. 2017-05-11 16:03:41,077 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Annulation du déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  1995. 2017-05-11 16:03:41,078 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Rapport de statut de service
  1996. WFLYCTL0186: Services qui n'ont pas pu démarrer : service jboss.deployment.unit."xa-cms-admin.war".PARSE
  1997.  
  1998. 2017-05-11 16:04:26,416 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")
  1999. 2017-05-11 16:04:32,947 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-admin.war/WEB-INF/lib/jaxb-core-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2000. 2017-05-11 16:04:32,949 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2001. 2017-05-11 16:04:32,949 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-admin.war/WEB-INF/lib/jaxb-impl-2.2.7.jar does not point to a valid jar for a Class-Path reference.
  2002. 2017-05-11 16:04:32,969 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-admin.war/WEB-INF/lib/openejb-core-4.7.3.jar does not point to a valid jar for a Class-Path reference.
  2003. 2017-05-11 16:04:33,085 INFO [org.jboss.as.jpa] (MSC service thread 1-1) WFLYJPA0002: Lecture de persistence.xml de xa-cms
  2004. 2017-05-11 16:04:33,088 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"
  2005. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
  2006. at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
  2007. at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
  2008. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  2009. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  2010. at java.lang.Thread.run(Thread.java:745)
  2011. 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
  2012. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.validateArgumentType(AroundTimeoutAnnotationParsingProcessor.java:106)
  2013. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.processAroundInvoke(AroundTimeoutAnnotationParsingProcessor.java:86)
  2014. at org.jboss.as.ejb3.deployment.processors.AroundTimeoutAnnotationParsingProcessor.deploy(AroundTimeoutAnnotationParsingProcessor.java:71)
  2015. at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
  2016. ... 5 more
  2017.  
  2018. 2017-05-11 16:04:33,115 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\"
  2019. 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"}}
  2020. 2017-05-11 16:04:33,327 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Déploiement de "xa-cms-admin.war" (runtime-name: "xa-cms-admin.war")
  2021. 2017-05-11 16:04:33,328 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Rapport de statut de service
  2022. 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"
  2023.  
  2024. 2017-05-11 16:04:54,831 INFO [org.jboss.as.server] (management-handler-thread - 6) WFLYSRV0236: Suspending server with no timeout.
  2025. 2017-05-11 16:04:54,843 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2026. 2017-05-11 16:04:54,908 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 67) WFLYUT0022: Contexte web désenregistré : /jboss-numberguess
  2027. 2017-05-11 16:04:54,921 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0022: Contexte web désenregistré : /jboss-helloworld
  2028. 2017-05-11 16:04:55,261 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-numberguess.war
  2029. 2017-05-11 16:04:55,274 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0019: L'hôte default-host s'arrête
  2030. 2017-05-11 16:04:55,468 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) WFLYWELD0010: Arrêt du service Weld pour le déploiement jboss-helloworld.war
  2031. 2017-05-11 16:04:55,757 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Source de données non liée [java:jboss/datasources/ExampleDS]
  2032. 2017-05-11 16:04:55,792 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
  2033. 2017-05-11 16:04:55,808 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0008: Undertow HTTP écouteur default en cours de suspension
  2034. 2017-05-11 16:04:55,809 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
  2035. 2017-05-11 16:04:55,812 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0004: Arrêt 1.3.21.Final-redhat-1 d'Undertow
  2036. 2017-05-11 16:04:55,852 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 985ms
  2037. 2017-05-11 16:04:55,881 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 1007ms
  2038. 2017-05-11 16:04:55,947 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 1079ms
  2039. 2017-05-11 16:04:55,953 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 1079ms
  2040. 2017-05-11 16:05:20,966 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
  2041. 2017-05-11 16:05:21,316 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
  2042. 2017-05-11 16:05:21,415 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
  2043. 2017-05-11 16:05:21,417 DEBUG [org.jboss.as.config] (MSC service thread 1-6) Propriétés de système configurées :
  2044. awt.toolkit = sun.awt.windows.WToolkit
  2045. file.encoding = Cp1252
  2046. file.encoding.pkg = sun.io
  2047. file.separator = \
  2048. java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
  2049. java.awt.headless = true
  2050. java.awt.printerjob = sun.awt.windows.WPrinterJob
  2051. java.class.path = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\jboss-modules.jar
  2052. java.class.version = 52.0
  2053. java.endorsed.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\endorsed
  2054. java.ext.dirs = C:\Program Files\Java\jdk1.8.0_121\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext
  2055. java.home = C:\Program Files\Java\jdk1.8.0_121\jre
  2056. java.io.tmpdir = C:\Utilisateurs\A665340\AppData\Local\Temp\
  2057. 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;;.
  2058. java.net.preferIPv4Stack = true
  2059. java.runtime.name = Java(TM) SE Runtime Environment
  2060. java.runtime.version = 1.8.0_121-b13
  2061. java.specification.name = Java Platform API Specification
  2062. java.specification.vendor = Oracle Corporation
  2063. java.specification.version = 1.8
  2064. java.util.logging.manager = org.jboss.logmanager.LogManager
  2065. java.vendor = Oracle Corporation
  2066. java.vendor.url = http://java.oracle.com/
  2067. java.vendor.url.bug = http://bugreport.sun.com/bugreport/
  2068. java.version = 1.8.0_121
  2069. java.vm.info = mixed mode
  2070. java.vm.name = Java HotSpot(TM) 64-Bit Server VM
  2071. java.vm.specification.name = Java Virtual Machine Specification
  2072. java.vm.specification.vendor = Oracle Corporation
  2073. java.vm.specification.version = 1.8
  2074. java.vm.vendor = Oracle Corporation
  2075. java.vm.version = 25.121-b13
  2076. javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
  2077. javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
  2078. javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
  2079. javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
  2080. javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
  2081. javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
  2082. javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
  2083. javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
  2084. javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
  2085. javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
  2086. jboss.bind.address = localhost
  2087. jboss.bind.address.management = localhost
  2088. jboss.home.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0
  2089. jboss.host.name = l82564
  2090. jboss.modules.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\modules
  2091. jboss.modules.system.pkgs = org.jboss.byteman
  2092. jboss.node.name = l82564
  2093. jboss.qualified.host.name = l82564
  2094. jboss.server.base.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone
  2095. jboss.server.config.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\configuration
  2096. jboss.server.data.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data
  2097. jboss.server.deploy.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\data\content
  2098. jboss.server.log.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\log
  2099. jboss.server.name = l82564
  2100. jboss.server.persist.config = true
  2101. jboss.server.temp.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\standalone\tmp
  2102. line.separator =
  2103.  
  2104. logging.configuration = file:/C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/configuration/logging.properties
  2105. module.path = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/modules
  2106. org.jboss.boot.log.file = C:/Utilisateurs/A665340/jboss_eap/jboss-eap-7.0/standalone/log/boot.log
  2107. org.jboss.logmanager.nocolor = true
  2108. org.jboss.resolver.warning = true
  2109. org.xml.sax.driver = __redirected.__XMLReaderFactory
  2110. os.arch = amd64
  2111. os.name = Windows 7
  2112. os.version = 6.1
  2113. path.separator = ;
  2114. program.name = JBossTools: Red Hat JBoss EAP 7.x
  2115. sun.arch.data.model = 64
  2116. 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
  2117. sun.boot.library.path = C:\Program Files\Java\jdk1.8.0_121\jre\bin
  2118. sun.cpu.endian = little
  2119. sun.cpu.isalist = amd64
  2120. sun.desktop = windows
  2121. sun.io.unicode.encoding = UnicodeLittle
  2122. 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
  2123. sun.java.launcher = SUN_STANDARD
  2124. sun.jnu.encoding = Cp1252
  2125. sun.management.compiler = HotSpot 64-Bit Tiered Compilers
  2126. sun.os.patch.level = Service Pack 1
  2127. sun.rmi.dgc.client.gcInterval = 3600000
  2128. sun.rmi.dgc.server.gcInterval = 3600000
  2129. user.country = FR
  2130. user.dir = C:\Utilisateurs\A665340\jboss_eap\jboss-eap-7.0\bin
  2131. user.home = C:\Utilisateurs\A665340
  2132. user.language = fr
  2133. user.name = A665340
  2134. user.script =
  2135. user.timezone = Europe/Paris
  2136. user.variant =
  2137. 2017-05-11 16:05:21,418 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
  2138. 2017-05-11 16:05:23,577 WARN [org.jboss.as.server.deployment.scanner] (ServerService Thread Pool -- 5) 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é.
  2139. 2017-05-11 16:05:23,830 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"
  2140. 2017-05-11 16:05:23,844 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.
  2141. 2017-05-11 16:05:23,846 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: La fermeture du serveur à été demandée.
  2142. 2017-05-11 16:05:23,861 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 10ms
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!