ear file will not deploy

Answered

Running intellij and have an ear project. the project builds fine, but when I go do debug, the app server starts up (Wildflpy 30), but there is no dployment started, no error either, just nothing happens.

0
25 comments

I see a duplicate issue post in https://intellij-support.jetbrains.com/hc/en-us/community/posts/25218962141330-exploeded-ear-wil-not-deploy . Could you help us with the required information from the post ? Thanks. 

0

I can't provied source code.  Is there some logging I can turn on in intellij? 

0
Could you share the run config screenshot and the deployment tab : https://www.jetbrains.com/help/idea/run-debug-configuration-jboss-server.html#deployment-tab 
Wildfly does not accept exploded war by default. So if this is the first time configuration you may need to configure your server accordingly: https://stackoverflow.com/questions/50695327/how-to-deploy-exploded-war-as-folder-in-wildfly-10
0

Leor Amikam Could you please double confirm if your case matches https://youtrack.jetbrains.com/issue/IDEA-355965/Wrong-exploded-EAR-layout? If no, could you please share the zipped log folder (Help | Collect Logs and Diagnostic Data) and screenshot of the project tree layout?

0

I don't see where to add files.

0
What file do you need to add? Does the "New" option work for you on the desired folder? Also, can you locate your war file?
0

I don't see where I can attach a log file to the ticket.

0

Please file a ticket to support via https://intellij-support.jetbrains.com/hc/requests/new and attach the logs using Help | Collect Logs and Diagnostic Data. You can also upload the logs via https://uploads.jetbrains.com and provide the Upload ID in the ticket.

In your support ticket, please copy/paste the complete output from the server run console in IntelliJ IDEA.

It will also help a lot if you create a small sample project that will reproduce the same issue as your main project and share it in the support ticket.

Thank you.

0

I uploaded the files to 2025_06_03_UzW4Q81KLx3YQRzBQNNKBs 

0

If you build this project via Maven / Gradle and try to deploy the produced ear file to the JBoss server, does it work without errors?

In other words, is this issue specific to IntelliJ IDEA?

The logs show some dependencies may be missing or incorrect, or there can be some other configuration issue with the project itself that may be not related to IntelliJ IDEA.

Could not create plugin of type class org.apache.logging.log4j.core.appender.mom.JmsAppender for element JMS: java.lang.NoClassDefFoundError: javax/jms/JMSException

 

0

Yes, I can build the ear in intellij and manually deploy it to the app server.  I can even debug that code.  

0

ear or exploded ear? Please clarify which one deploys fine and which one fails.

To better help you with this issue, please create a support ticket and share any sample project to reproduce the issue. It will speed up the process of finding the issue and will avoid back-and-forth questions in this public forum.

0

neither ear or exploaded ear deploy from within intellij.  I copy the ear file to the jboss deployments folder and it picks it up.  I will try to make a sampe project.

0

You are using JDK 21 to run Wildfly from IntelliJ IDEA. Is it the same version as you use for your standalone Wildfly installation where the deployment works?

0

I uploaded ( 2025_06_03_Fsnan91AGsBPoZirenAqbG  ) a sample project that also fails the same way.  Artifact will not deploy.

0

Your sample project deploys fine if you add the missing Build steps for the project and the artifact itself, otherwise there is an error that the deployment path is not found:

 

0

I added the build steps and and still does not deploy.  

0

What is the specific error in the server run console log?

0

there is no error.  It just doesn't start deployment.  

0

Share the full output from the run console.

0
X:\javatools\wildfly-30.0.0.Final-hif\bin\standalone.bat -c standalone-full.xml
Calling "X:\javatools\wildfly-30.0.0.Final-hif\bin\standalone.conf.bat"
"JAVA_OPTS already set in environment; overriding default settings with values: -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:63979,suspend=y,server=n -javaagent:C:\Users\amikaml\AppData\Local\JetBrains\IntelliJIdea2024.3\captureAgent\debugger-agent.jar=file:/C:/Users/amikaml/AppData/Local/Temp/capture.props -Dkotlinx.coroutines.debug.enable.creation.stack.trace=false -Ddebugger.agent.enable.coroutines=true -Dkotlinx.coroutines.debug.enable.flows.stack.trace=true -Dkotlinx.coroutines.debug.enable.mutable.state.flows.stack.trace=true -Djboss.socket.binding.port-offset=1 "
Setting JAVA property to "X:\javatools\jdk-21\bin\java"
===============================================================================
 JBoss Bootstrap Environment
 JBOSS_HOME: "X:\javatools\wildfly-30.0.0.Final-hif"
 JAVA: "X:\javatools\jdk-21\bin\java"
 JAVA_OPTS: "-Dprogram.name=standalone.bat -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:63979,suspend=y,server=n -javaagent:C:\Users\amikaml\AppData\Local\JetBrains\IntelliJIdea2024.3\captureAgent\debugger-agent.jar=file:/C:/Users/amikaml/AppData/Local/Temp/capture.props -Dkotlinx.coroutines.debug.enable.creation.stack.trace=false -Ddebugger.agent.enable.coroutines=true -Dkotlinx.coroutines.debug.enable.flows.stack.trace=true -Dkotlinx.coroutines.debug.enable.mutable.state.flows.stack.trace=true -Djboss.socket.binding.port-offset=1  -Dlog4j2.enableJndiJms=true -Dlog4j2.enableJndiJdbc=true  --add-exports=java.desktop/sun.awt=ALL-UNNAMED --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-exports=java.naming/com.sun.jndi.url.ldap=ALL-UNNAMED --add-exports=java.naming/com.sun.jndi.url.ldaps=ALL-UNNAMED --add-exports=jdk.naming.dns/com.sun.jndi.dns=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.management/javax.management=ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED -Djava.security.manager=allow"
===============================================================================
X:\javatools\jdk-21\bin\java.exe -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -classpath C:\Users\amikaml\AppData\Local\Temp\classpath30247313.jar com.intellij.javaee.oss.process.JavaeeProcess 59807 com.intellij.javaee.oss.jboss.agent.WildFly28Agent
[2025-06-05 02:46:25,551] Artifact HansenIntegrationFramework-ear:ear exploded: Waiting for server connection to start artifact deployment…
Detected server admin port: 9991
Detected server http port: 8081
Connected to the target VM, address: '127.0.0.1:63979', transport: 'socket'
14:46:26,704 INFO  [org.jboss.modules] (main) JBoss Modules version 2.1.2.Final
14:46:28,499 INFO  [org.jboss.msc] (main) JBoss MSC version 1.5.2.Final
14:46:28,528 INFO  [org.jboss.threads] (main) JBoss Threads version 2.4.0.Final
14:46:28,791 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 30.0.0.Final (WildFly Core 22.0.1.Final) starting
14:46:30,399 INFO  [org.wildfly.security] (ServerService Thread Pool -- 26) ELY00001: WildFly Elytron version 2.2.2.Final
14:46:32,773 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 29) WFLYCTL0028: Attribute 'cluster' in the resource at address '/subsystem=ejb3/service=remote' is deprecated, and may be removed in a future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:46:33,002 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:46:33,055 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.8.11.Final
14:46:33,078 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.8.11.Final
14:46:33,356 INFO  [org.wildfly.extension.elytron.oidc._private] (ServerService Thread Pool -- 55) WFLYOIDC0001: Activating WildFly Elytron OIDC Subsystem
14:46:33,362 INFO  [org.wildfly.extension.health] (ServerService Thread Pool -- 56) WFLYHEALTH0001: Activating Base Health Subsystem
14:46:33,372 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 58) WFLYCLINF0001: Activating Infinispan subsystem.
14:46:33,378 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 59) WFLYIO001: Worker 'default' has auto-configured to 24 IO threads with 192 max task threads based on your 12 available processors
14:46:33,379 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 60) WFLYRS0016: RESTEasy version 6.2.5.Final
14:46:33,379 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 57) WFLYIIOP0001: Activating IIOP Subsystem
14:46:33,409 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 46) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 2.2)
14:46:33,463 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting Jakarta Connectors Subsystem (WildFly/IronJacamar 3.0.4.Final)
14:46:33,484 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
14:46:33,532 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 65) WFLYJSF0007: Activated the following Jakarta Server Faces Implementations: [main]
14:46:33,538 INFO  [org.wildfly.extension.microprofile.config.smallrye] (ServerService Thread Pool -- 69) WFLYCONF0001: Activating MicroProfile Config Subsystem
14:46:33,564 INFO  [org.wildfly.extension.microprofile.jwt.smallrye] (ServerService Thread Pool -- 70) WFLYJWT0001: Activating MicroProfile JWT Subsystem
14:46:33,569 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 71) WFLYNAM0001: Activating Naming Subsystem
14:46:33,590 INFO  [org.wildfly.extension.metrics] (ServerService Thread Pool -- 68) WFLYMETRICS0001: Activating Base Metrics Subsystem
14:46:33,634 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 78) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
14:46:33,772 INFO  [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.27.Final
14:46:33,889 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 80) WFLYWS0002: Activating WebServices Extension
14:46:33,908 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 2.3.10.Final starting
14:46:33,946 INFO  [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
14:46:33,954 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 192 (per class), which is derived from thread worker pool sizing.
14:46:33,954 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 48 (per class), which is derived from the number of CPUs on this host.
14:46:33,974 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 46) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 12.1)
14:46:33,975 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 46) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.driver.OracleDriver (version 12.1)
14:46:33,981 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:46:34,031 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = OracleJDBCDriver
14:46:34,032 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = OracleJDBCDriver2
14:46:34,254 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 79) WFLYUT0014: Creating file handler for path 'X:\javatools\wildfly-30.0.0.Final-hif/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:46:34,321 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
14:46:34,331 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) Queuing requests.
14:46:34,345 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
14:46:34,570 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on 10.152.10.160:8081
14:46:35,185 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0098: Bound non-transactional data source: java:/jdbc/HIF-LoggerPU
14:46:35,382 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
14:46:35,427 INFO  [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-1) IJ020018: Enabling <validate-on-match> for java:/jdbc/banner50
14:46:35,437 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:46:35,457 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/jdbc/HIF-BannerPU]
14:46:35,469 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/jdbc/banner50]
14:46:35,472 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/jdbc/HIF-AuditPU]
14:46:35,684 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 10.152.10.160:8444
14:46:35,859 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-8) WFLYIIOP0009: CORBA ORB Service started
14:46:36,077 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0008: CORBA Naming Service started
Jun 05, 2025 2:46:36 PM org.jboss.logmanager.JBossLoggerFinder getLogger
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.
14:46:36,577 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) WFLYDS0013: Started FileSystemDeploymentService for directory X:\javatools\wildfly-30.0.0.Final-hif\standalone\deployments
14:46:36,624 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.
14:46:36,880 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=X:\javatools\wildfly-30.0.0.Final-hif\standalone\data\activemq\journal,bindingsDirectory=X:\javatools\wildfly-30.0.0.Final-hif\standalone\data\activemq\bindings,largeMessagesDirectory=X:\javatools\wildfly-30.0.0.Final-hif\standalone\data\activemq\largemessages,pagingDirectory=X:\javatools\wildfly-30.0.0.Final-hif\standalone\data\activemq\paging)
14:46:36,934 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 7.0.0.Final (Apache CXF 4.0.0) 
14:46:37,305 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221013: Using NIO Journal
14:46:37,790 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
14:46:37,793 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
14:46:37,796 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
14:46:37,798 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
14:46:37,976 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221034: Waiting indefinitely to obtain live lock
14:46:37,977 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221035: Live Server Obtained live lock
14:46:39,165 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.ExpiryQueue on address jms.queue.ExpiryQueue
14:46:39,179 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.DLQ on address jms.queue.DLQ
14:46:39,180 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.HIFAuditQueue on address jms.queue.HIFAuditQueue
14:46:39,180 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying ANYCAST queue jms.queue.HIFWebHookQueue on address jms.queue.HIFWebHookQueue
14:46:39,186 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:46:39,186 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:46:39,186 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-5) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:46:39,186 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:46:39,930 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221007: Server is now live
14:46:39,930 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221001: Apache ActiveMQ Artemis Message Broker version 2.31.0 [default, nodeID=583d8946-4f6a-11ef-9d4a-0a0027000013] 
14:46:39,967 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
14:46:40,013 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 84) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
14:46:40,105 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0007: Registered connection factory java:/JmsXA
14:46:40,442 INFO  [org.apache.activemq.artemis.ra.ActiveMQRALogger] (MSC service thread 1-2) AMQ151007: Resource adaptor started
14:46:40,444 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatoractivemq-ra
14:46:40,449 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound Jakarta Connectors ConnectionFactory [java:/JmsXA]
14:46:40,449 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0118: Binding connection factory named java:/JmsXA to alias java:jboss/DefaultJMSConnectionFactory
14:46:40,916 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
14:46:40,930 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://10.152.10.160:9991/management
14:46:40,931 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://10.152.10.160:9991
14:46:40,939 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 30.0.0.Final (WildFly Core 22.0.1.Final) started in 15002ms - Started 356 of 598 services (342 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml
 
0

This is the correct directory from the log file - WFLYDS0013: Started FileSystemDeploymentService for directory X:\javatools\wildfly-30.0.0.Final-hif\standalone\deployments.  Its like intellij is not copying the exploded ear file contents.

0

Try with a clean server installation with unmodified configs.

If you override logging, IDE will not detect the server startup correctly and will not start artifact deployment.

The logs should have something like this when it works properly:

12:03:13,850 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory d:\dev\wildfly-35.0.1.Final\standalone\deployments
12:03:13,870 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
12:03:14,030 INFO  [org.jboss.as.ejb3] (MSC service thread 1-6) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
12:03:14,092 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 7.3.1.Final (Apache CXF 4.0.6) 
12:03:14,124 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
12:03:14,205 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
12:03:14,217 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
12:03:14,217 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
12:03:14,218 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly 35.0.1.Final (WildFly Core 27.0.1.Final) started in 3586ms - Started 326 of 541 services (323 services are lazy, passive or on-demand) - Server configuration file in use: standalone.xml - Minimum feature stability level: community
Jun 05, 2025 12:03:14 PM org.jboss.logmanager.JBossLoggerFinder getLogger
ERROR: The LogManager accessed before the "java.util.logging.manager" system property was set to "org.jboss.logmanager.LogManager". Results may be unexpected.
Connected to server
[2025-06-05 12:03:15,059] Artifact helloworld:war exploded: Artifact is being deployed, please wait…
12:03:15,143 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "helloworld" (runtime-name: "helloworld.war")
12:03:15,934 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 23) WFLYUT0021: Registered web context: '/helloworld' for server 'default-server'
12:03:15,957 INFO  [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0010: Deployed "helloworld" (runtime-name : "helloworld.war")
[2025-06-05 12:03:15,966] Artifact helloworld:war exploded: Artifact is deployed successfully
[2025-06-05 12:03:15,966] Artifact helloworld:war exploded: Deploy took 907 milliseconds
0

Please sign in to leave a comment.