Intellij Idea Wildfly 23启动...但由于启动超时而阻塞

cdmah0mi  于 2024-01-05  发布在  其他
关注(0)|答案(2)|浏览(173)

似乎启动正确

  1. 17:44:17,093 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
  2. 17:44:17,201 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8180
  3. 17:44:17,202 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8543
  4. 17:44:17,456 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\ActionICT-Motti\IdeaProjects\DocumentsStorage_v1\target\server\standalone\deployments
  5. 17:44:17,522 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
  6. 17:44:17,779 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
  7. 17:44:17,808 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 7.0.0.Final (Apache CXF 4.0.0)
  8. 17:44:17,961 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
  9. 17:44:17,968 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:10090/management
  10. 17:44:17,968 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:10090
  11. 17:44:17,971 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 30.0.0.Final (WildFly Core 22.0.1.Final) started in 8592ms - Started 280 of 522 services (317 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml

字符串
但是当启动超时结束时,


的数据
有什么问题吗?谢谢。
编辑:我正在使用wildfly-maven-plugin管理它。

  1. <plugin>
  2. <groupId>org.wildfly.plugins</groupId>
  3. <artifactId>wildfly-maven-plugin</artifactId>
  4. <version>4.0.0.Final</version>
  5. <configuration>
  6. <!--
  7. In produzione c'e' JBoss EAP 6.3 => JBoss AS 7.4.0.Final
  8. ma tale release non e' disponibile nei repo Maven
  9. quindi usiamo la versione piu' simile disponibile
  10. -->
  11. <version>23.0.0.Final</version>
  12. <javaOpts>
  13. -Xms64m
  14. <!-- -Xmx512m-->
  15. <!-- -XX:MaxMetaspaceSize=256m-->
  16. -Djava.net.preferIPv4Stack=true
  17. -Dorg.jboss.resolver.warning=true
  18. -Dsun.rmi.dgc.client.gcInterval=3600000
  19. -Dsun.rmi.dgc.server.gcInterval=3600000
  20. -Djboss.socket.binding.port-offset=100
  21. -Djboss.server.config.dir=${project.build.testOutputDirectory}/configuration
  22. <!-- ${jacocoAgent}-->
  23. <!-- &lt;!&ndash;per eseguire il debug remoto rimuovere il commento dalla riga sottostante-->
  24. <!-- -Xrunjdwp:transport=dt_socket,address=33333,server=y,suspend=y-->
  25. </javaOpts>
  26. <port>10090</port>
  27. </configuration>

6jjcrrmo

6jjcrrmo1#

我已经解决了运行wildfly:runwildfly:deploy maven任务,正确记录了错误。

uwopmtnx

uwopmtnx2#

您可以找到wildfly-maven-plugin的所有可用目标here
如果你想在开发过程中运行你的服务器,我想最好的方法是wildfly:dev
启动WildFly的独立示例,并将应用程序部署到服务器。部署类型myst是WAR。一旦服务器运行,将监视源目录的更改。如果需要,将编译源并重新部署部署。
请注意,对POM文件的更改不会受到监视。如果对POM文件进行了更改,则需要终止并重新启动该进程。
您也可以使用wildfly:startwildfly:shutdown,因为start将执行以下操作:
启动WildFly Application Server的独立示例。此目标的目的是启动WildFly Application Server,以便在maven生命周期期间进行测试。

相关问题