Wildfly : application deployed but not running

Question

I'm trying to deploy an .ear application to Wildfly 10.1 final. The .ear has 2 nested .war files. There's no "jboss-web.xml" file in the .war files.

Here's the application.xml file :

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
    "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
    "http://java.sun.com/dtd/application_1_3.dtd">
<application>
    <display-name>myApp-ear</display-name>
    <description>myApp</description>
    <module>
      <web>
        <web-uri>myApp-rest</web-uri>
        <context-root>/myApp-rest</context-root>
      </web>
    </module>
    <module>
      <web>
        <web-uri>myApp-webapp</web-uri>
        <context-root>/myApp-webapp</context-root>
      </web>
    </module>
</application>

After deploying, I have the following log :

INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found myApp.ear in deployment directory. To trigger deployment create a file called myApp.ear.dodeploy
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "myApp.ear" (runtime-name: "myApp.ear")
WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /C:/Dev/Wildfly/wildfly-10.1.0.Final/standalone/deployments/myApp.ear/liquibase-core-3.3.0.jar does not point to a valid jar for a Class-Path reference.
(...)
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-rest")
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-webapp")
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "myApp.ear" (runtime-name : "myApp.ear")

And that's all, no "register" in the logs or something like that. So, whenever I try to access "localhost:8080/myApp-webapp" I have a 404 error.

The application was previously deployed on Weblogic 11 (with the same configuration) and it worked fine.

Any clue ?

Actually yes, each time I create this file in the deployement folder, myApp gets deployed again with the following message : "WFLYSRV0016: Replaced deployment "myApp.ear" with deployment "myApp.ear"". But the problem remains. — Christos Loupassakis
Is this an exploded deployment? If so you'll want to have an extension on your myApp-rest and myApp-webapp, i.e. myApp-rest.jar myApp-webapp.war. — James R. Perkins
I have already tried to add an extension (first thing that crossed my mind), but that changes nothing — Christos Loupassakis

James R. Perkins James R. Perkins · Accepted Answer · 2016-12-22T16:57:47

Based on the following log messages it looks like the contents of your EAR are missing the appropriate file extensions

INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-rest") 
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-webapp") 
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "myApp.ear" (runtime-name : "myApp.ear")

Specifically note the myApp-rest and myApp-webapp. Those should both have a .war extension even if this is an exploded deployment. (Note the myApp-rest may have a .jar extension if it's just an EJB module.)

Wildfly : application deployed but not running

1 Answers