Wildfly 12和13复制了standalone.xml文件，并将其记录为无限循环

时间：2018-06-27 14:20:12

标签： java wildfly

我今天对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时，我得到了相同的结果。昨天我没有遇到这种情况。怎么了？请注意，我使用JBoss Tools 4.5.3.Final插件从Eclipse Oxygen.3a管理Wildfly实例。

2 个答案:

答案 0 :(得分：0)

我在此链接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.   
  2. 在关机前删除添加的部署扫描程序
    3.   
     

取消选中这些选项后，不再将第二个部署扫描程序添加到我的standalone.xml文件中。

答案 1 :(得分：-1)

好的，终于我解决了这个问题。不是Wildfly，而是JBoss Tools插件。

为解决此问题，我在服务器的概述页面上进行了以下更改，就像我以前为Wildfly的旧版本设置的那样： -取消选中“将管理端口公开为服务器的主机名 -服务器状态检测器：启动轮询器=管理服务 -服务器状态检测器：关机轮询器=进程已终止

相关问题
最新问题