Wildfly 12 и 13 дублируют файл standalone.xml и регистрируют его как бесконечный цикл - PullRequest
Новая
       4

Wildfly 12 и 13 дублируют файл standalone.xml и регистрируют его как бесконечный цикл

0 голосов
/ 27 июня 2018

Сегодня я испытываю что-то любопытное с Wildfly 13, а вчера не испытывал (впервые установил и использовал). Когда я запускаю сервер, все выглядит нормально, и Wildfly загружает и запускает мой собственный файл standalone.xml: 

2018-06-27 14:32:35,560 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")

Но затем он загружает и регистрирует все остальные версии автономных XML-файлов, которые он находит, в папку конфигурации: 

2018-06-27 14:32:35,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "standalone-full-ha.xml" (runtime-name: "standalone-full-ha.xml")
2018-06-27 14:32:35,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "standalone-ha.xml" (runtime-name: "standalone-ha.xml")
2018-06-27 14:32:35,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone-full.xml" (runtime-name: "standalone-full.xml")
2018-06-27 14:32:35,560 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone-load-balancer.xml" (runtime-name: "standalone-load-balancer.xml")
2018-06-27 14:32:35,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.v1.xml" (runtime-name: "remmedia-standalone.v1.xml")
2018-06-27 14:32:35,560 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "standalone-ee8.xml" (runtime-name: "standalone-ee8.xml")
2018-06-27 14:32:35,561 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")

А затем карусель, похоже, перезапускается как бесконечный цикл, даже если мой файл remmedia-standalone.xml переместился в подпапку standalone-xml-history. 

2018-06-27 14:32:35,564 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "remmedia-standalone.initial.xml" (runtime-name: "remmedia-standalone.initial.xml")
2018-06-27 14:32:35,564 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.boot.xml" (runtime-name: "remmedia-standalone.boot.xml")
2018-06-27 14:32:35,565 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:32:37,214 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Gaina' 9.2.4.Final
2018-06-27 14:32:37,698 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
2018-06-27 14:32:37,933 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.last.xml" (runtime-name : "remmedia-standalone.last.xml")
2018-06-27 14:32:37,933 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.initial.xml" (runtime-name : "remmedia-standalone.initial.xml")
2018-06-27 14:32:37,933 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.boot.xml" (runtime-name : "remmedia-standalone.boot.xml")
2018-06-27 14:32:37,933 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v1.xml" (runtime-name : "remmedia-standalone.v1.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-load-balancer.xml" (runtime-name : "standalone-load-balancer.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-ha.xml" (runtime-name : "standalone-ha.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-full.xml" (runtime-name : "standalone-full.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-full-ha.xml" (runtime-name : "standalone-full-ha.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone-ee8.xml" (runtime-name : "standalone-ee8.xml")
2018-06-27 14:32:37,934 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.xml" (runtime-name : "remmedia-standalone.xml")
2018-06-27 14:32:43,076 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 35ms
2018-06-27 14:32:43,081 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:32:43,082 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "remmedia-standalone.v2.xml" (runtime-name: "remmedia-standalone.v2.xml")
2018-06-27 14:32:43,091 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 8ms
2018-06-27 14:32:43,092 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:32:43,135 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:32:43,136 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v2.xml" (runtime-name : "remmedia-standalone.v2.xml")
2018-06-27 14:32:43,136 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.xml" with deployment "remmedia-standalone.xml"
2018-06-27 14:32:48,202 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 10ms
2018-06-27 14:32:48,204 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:32:48,207 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.v3.xml" (runtime-name: "remmedia-standalone.v3.xml")
2018-06-27 14:32:48,247 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 43ms
2018-06-27 14:32:48,250 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:32:48,294 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:32:48,294 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v3.xml" (runtime-name : "remmedia-standalone.v3.xml")
2018-06-27 14:32:48,295 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.xml" with deployment "remmedia-standalone.xml"
2018-06-27 14:32:53,366 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 15ms
2018-06-27 14:32:53,369 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:32:53,370 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "remmedia-standalone.v4.xml" (runtime-name: "remmedia-standalone.v4.xml")
2018-06-27 14:32:53,385 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 16ms
2018-06-27 14:32:53,386 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:32:53,418 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:32:53,418 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v4.xml" (runtime-name : "remmedia-standalone.v4.xml")
2018-06-27 14:32:53,418 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.xml" with deployment "remmedia-standalone.xml"
2018-06-27 14:32:58,569 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 6ms
2018-06-27 14:32:58,572 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:32:58,573 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "remmedia-standalone.v5.xml" (runtime-name: "remmedia-standalone.v5.xml")
2018-06-27 14:32:58,615 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 44ms
2018-06-27 14:32:58,620 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:32:58,698 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:32:58,699 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v5.xml" (runtime-name : "remmedia-standalone.v5.xml")
2018-06-27 14:32:58,699 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.xml" with deployment "remmedia-standalone.xml"
2018-06-27 14:33:03,759 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 8ms
2018-06-27 14:33:03,761 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:33:03,763 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "remmedia-standalone.v6.xml" (runtime-name: "remmedia-standalone.v6.xml")
2018-06-27 14:33:03,780 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 20ms
2018-06-27 14:33:03,783 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:33:03,816 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:33:03,816 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "remmedia-standalone.v6.xml" (runtime-name : "remmedia-standalone.v6.xml")
2018-06-27 14:33:03,816 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "remmedia-standalone.xml" with deployment "remmedia-standalone.xml"
2018-06-27 14:33:08,892 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment remmedia-standalone.xml (runtime-name: remmedia-standalone.xml) in 6ms
2018-06-27 14:33:08,899 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "remmedia-standalone.v7.xml" (runtime-name: "remmedia-standalone.v7.xml")
2018-06-27 14:33:08,899 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "remmedia-standalone.xml" (runtime-name: "remmedia-standalone.xml")
2018-06-27 14:33:08,906 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment remmedia-standalone.last.xml (runtime-name: remmedia-standalone.last.xml) in 8ms
2018-06-27 14:33:08,907 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "remmedia-standalone.last.xml" (runtime-name: "remmedia-standalone.last.xml")
2018-06-27 14:33:08,941 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "remmedia-standalone.last.xml" with deployment "remmedia-standalone.last.xml"
2018-06-27 14:33:08,941 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "remmedia-standalone.v7.xml" (runtime-name : "remmedia-standalone.v7.xml")

Это поведение новое. И я получил то же самое, когда попытался запустить экземпляр Wildfly 12 вместо Wildfly 13. И я не испытывал этого вчера. Что не так? Обратите внимание, что я управляю экземпляром Wildfly из Eclipse Oxygen.3a с помощью плагина JBoss Tools 4.5.3.Final.

Ответы [ 2 ]

0 голосов
/ 17 июня 2019

Я нашел ответ по этой ссылке https://issues.jboss.org/browse/WFLY-10629

Вот выдержка из этой темы, которая помогла решить эту проблему

У меня была такая же проблема со мной сегодня. После просмотра standalone.xml я заметил второй сканер развертывания, который был добавлен jboss-tools: 

<deployment-scanner name="jbosstoolsscanner1" path="C:\dev\appserver\wildfly\wildfly-10.1.0.Final\user_projects\domains\myDomain" scan-interval="5000" deployment-timeout="600"/>

После удаления сканера, который сканирует каталог домена, wildfly перестанет пытаться развернуть файл standalone.xml. Я заметил параметр в обзоре сервера jboss-tools под сканерами развертывания: есть два флажка

  1. Добавление отсутствующих сканеров развертывания после запуска сервера
  2. Удалите добавленные сканеры развертывания перед выключением

После снятия этих отметок второй сканер развертывания больше не добавлялся в мой файл standalone.xml.

0 голосов
/ 27 июня 2018

ОК, наконец-то я решил проблему. Wildfly - не причина, а плагин JBoss Tools.

Чтобы исправить эту проблему, я внес следующие изменения на странице обзора сервера, которую я использовал для более старых версий Wildfly:

  • Снимите флажок "Предоставить порт управления в качестве имени хоста сервера
  • Состояние сервера Детекторы: автозагрузка = служба управления
  • Состояние сервера Детекторы: опрос при выключении = процесс завершен
...