Related
Using Red Hat WildFly 27.0.1 I'm trying to migrate Mojarra 4.0.0.SP01 to MyFaces 4.0.
Trying to use document "7.26. Jakarta Server Faces Configuration" at:
https://docs.wildfly.org/27/Admin_Guide.html#Jakarta_Server_Faces
Also I can't run "7.26.2. Changing the default Jakarta Server Faces implementation":
./jboss-cli.sh /subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=<JSF_IMPL_NAME>-<JSF_VERSION>)
I find the document conflicts.
Also "Working of the Multi-JSF Implementation" (posted on WildFly Forum).
How can I do this? TIA.
Posted on WildFly Forum: "That support is currently not working correctly. We have an open JIRA to address that, but we've simply had higher priorities. I hope to get to that "soon", but I can't make any promises. Principal Software Engineer, Red Hat JBoss EAP"
Have upgraded to MyFaces 4.0.0-RC4. Unable to resolve "WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid":
15:00:15,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
15:00:17,208 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
15:00:17,223 WARN [org.jboss.as.jsf] (MSC service thread 1-8) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0-RC4'. Default version 'myfaces-impl-4.0.0' will be used instead.
15:00:17,223 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,226 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 17ms
Next ...
Have added to WildFly 27 with:
com/sun/jsf-impl/myfaces-impl-4.0.0/myfaces-impl-4.0.0-RC4.jar
com/sun/jsf-impl/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/myfaces-api-4.0.0-RC4.jar
org/apache/commons/digester/main/commons-digester3-3.2.jar
org/apache/commons/digester/main/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
Run:
./jboss-cli.sh
connect
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-impl-4.0.0)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
Then:
/subsystem=jsf:list-active-jsf-impls()
Deployed test WAR:
14:03:01,310 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
14:03:03,431 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
14:03:03,455 WARN [org.jboss.as.jsf] (MSC service thread 1-2) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0'. Default version 'myfaces-impl-4.0.0' will be used instead.
14:03:03,456 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,461 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,487 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 26ms
14:08:35,964 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0009: Content /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6 is obsolete and will be removed
14:08:35,967 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0002: Content removed from location /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6/content
Results still with:
Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
Answer - MyFaces won't run/deploy on:
wildfly-preview-27.0.1.Final
Works with:
wildfly-27.0.1.Final
I have a small project on tomcat, it works well, now I decided to migrate to wildfly 10.
The deployment is ok but when I want to display my jsf (primefaces)pages, it's return me a 404 not found. I don't know what I have to do because I see any errors on the console. What's wrong, What's the problem?
My web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" id="WebApp_ID" version="3.1">
<display-name>Watchlist</display-name>
<welcome-file-list>
<welcome-file>Search.xhtml</welcome-file>
</welcome-file-list>
<context-param>
<param-name>primefaces.THEME</param-name>
<param-value>bluesky</param-value>
</context-param>
<servlet>
<servlet-name>facesServlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>facesServlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
</web-app>
My primefaces page which return 404 not found ( this type of return is the same for all my xhtml pages). Even when i create a simple helloWorld.xhtml page, it's return me "404 not found" :
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:h="http://java.sun.com/jsf/html"
xmlns:p="http://primefaces.org/ui">
<h:head>
<style>
input[type=text] {
color: red;
text-align: left;
cursor: pointer;
display: block;
width: 70%;
}
::-webkit-input-placeholder {
color: grey;
}
fieldset {
width: 400px;
}
</style>
</h:head>
<body>
<h1>Test</h1>
<h:form method="post" action="Movies.xhtml">
<p:inputText type="text" value="#{tshiliflixBean.m.title}" placeholder="Rechercher un film, un artiste..."/>
<p:commandButton value="Rechercher " action="#{tshiliflixBean.ListFilmSearch()}"/>
</h:form>
</body>
</html>
My pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.TshiliDB.movieDB</groupId>
<artifactId>Tshiflix</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>war</packaging>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<source>1.8</source>
<target>1.8</target>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
<!-- https://mvnrepository.com/artifact/javax.ejb/javax.ejb-api -->
<dependency>
<groupId>javax.ejb</groupId>
<artifactId>javax.ejb-api</artifactId>
<version>3.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/javax.servlet.jsp.jstl/jstl-api -->
<dependency>
<groupId>javax.servlet.jsp.jstl</groupId>
<artifactId>jstl-api</artifactId>
<version>1.2</version>
</dependency>
<dependency>
<groupId>com.github.wnameless</groupId>
<artifactId>json-flattener</artifactId>
<version>0.2.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/org.jsoup/jsoup -->
<!-- https://mvnrepository.com/artifact/com.sun.faces/jsf-impl -->
<dependency>
<groupId>com.sun.faces</groupId>
<artifactId>jsf-impl</artifactId>
<version>2.2.12</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>6.0.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-databind -->
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>2.8.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-annotations -->
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-annotations</artifactId>
<version>2.8.2</version>
</dependency>
<!-- https://mvnrepository.com/artifact/com.fasterxml.jackson.core/jackson-core -->
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.8.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>2.23.2</version>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.primefaces</groupId>
<artifactId>primefaces</artifactId>
<version>6.0</version>
</dependency>
<dependency>
<groupId>com.google.code.gson</groupId>
<artifactId>gson</artifactId>
<version>2.7</version>
</dependency>
<dependency>
<groupId>javax.faces</groupId>
<artifactId>jsf-api</artifactId>
<version>2.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<version>5.2.2.Final</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-entitymanager</artifactId>
<version>5.2.2.Final</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>javax.ws.rs</groupId>
<artifactId>javax.ws.rs-api</artifactId>
<version>2.0.1</version>
</dependency>
<!-- Jersey 2.19 -->
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-server</artifactId>
<version>2.23.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.core</groupId>
<artifactId>jersey-client</artifactId>
<version>2.23.2</version>
</dependency>
<dependency>
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet</artifactId>
<version>2.10.1</version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>log4j-over-slf4j</artifactId>
<version>1.7.21</version>
</dependency>
</dependencies>
</project>
My console view when, i start my wildfly server:
19:04:00,505 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
19:04:00,685 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
19:04:00,750 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
19:04:01,566 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found Tshiflix-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called Tshiflix-0.0.1-SNAPSHOT.war.dodeploy
19:04:01,605 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
19:04:01,619 INFO [org.xnio] (MSC service thread 1-7) XNIO version 3.3.4.Final
19:04:01,625 INFO [org.xnio.nio] (MSC service thread 1-7) XNIO NIO Implementation Version 3.3.4.Final
19:04:01,649 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
19:04:01,658 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
19:04:01,664 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
19:04:01,671 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
19:04:01,688 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
19:04:01,689 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
19:04:01,689 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
19:04:01,698 INFO [org.jboss.as.security] (MSC service thread 1-6) WFLYSEC0001: Current PicketBox version=4.9.4.Final
19:04:01,713 INFO [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
19:04:01,799 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
19:04:01,800 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
19:04:01,800 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0003: Undertow 1.3.15.Final starting
19:04:01,811 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2
19:04:01,815 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.18.Final
19:04:01,830 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
19:04:01,831 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.39-bin.jar
19:04:01,847 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
19:04:01,848 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
19:04:01,954 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/Users/Tshili/Documents/Library/wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
19:04:01,987 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
19:04:01,989 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting
19:04:02,026 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
19:04:02,026 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
19:04:02,076 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:9090
19:04:02,154 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:/dsWatchlist]
19:04:02,154 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
19:04:02,247 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory /Users/Tshili/Documents/Library/wildfly-10.0.0.Final/standalone/deployments
19:04:02,253 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "Tshiflix-0.0.1-SNAPSHOT.war" (runtime-name: "Tshiflix-0.0.1-SNAPSHOT.war")
19:04:02,253 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "Tshiflix2.war" (runtime-name: "Tshiflix2.war")
19:04:02,471 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
19:04:02,471 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
19:04:02,471 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
19:04:02,480 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
19:04:04,093 INFO [org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read persistence.xml for Watchlist
19:04:04,146 INFO [org.jboss.as.jpa] (MSC service thread 1-7) WFLYJPA0002: Read persistence.xml for Watchlist
19:04:04,274 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 58) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'Tshiflix-0.0.1-SNAPSHOT.war#Watchlist'
19:04:04,295 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 58) HHH000204: Processing PersistenceUnitInfo [
name: Watchlist
...]
19:04:04,295 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 59) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service 'Tshiflix2.war#Watchlist'
19:04:04,296 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 59) HHH000204: Processing PersistenceUnitInfo [
name: Watchlist
...]
19:04:04,342 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment Tshiflix-0.0.1-SNAPSHOT.war
19:04:04,378 INFO [org.hibernate.Version] (ServerService Thread Pool -- 59) HHH000412: Hibernate Core {5.0.7.Final}
19:04:04,379 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 59) HHH000206: hibernate.properties not found
19:04:04,381 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 59) HHH000021: Bytecode provider name : javassist
19:04:04,396 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0003: Processing weld deployment Tshiflix2.war
19:04:04,418 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-8) HV000001: Hibernate Validator 5.2.3.Final
19:04:04,425 INFO [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 58) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
19:04:04,425 INFO [org.hibernate.orm.deprecation] (ServerService Thread Pool -- 59) HHH90000001: Found usage of deprecated setting for specifying Scanner [hibernate.ejb.resource_scanner]; use [hibernate.archive.scanner] instead
19:04:04,438 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 59) HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
19:04:04,502 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-8) WFLYEJB0473: JNDI bindings for session bean named 'watchlistDAO' in deployment unit 'deployment "Tshiflix2.war"' are as follows:
java:global/Tshiflix2/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:app/Tshiflix2/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:module/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:global/Tshiflix2/watchlistDAO
java:app/Tshiflix2/watchlistDAO
java:module/watchlistDAO
19:04:04,502 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'watchlistDAO' in deployment unit 'deployment "Tshiflix-0.0.1-SNAPSHOT.war"' are as follows:
java:global/Tshiflix-0.0.1-SNAPSHOT/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:app/Tshiflix-0.0.1-SNAPSHOT/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:module/watchlistDAO!com.Tshiflix.DAO.WatchlistImpl
java:global/Tshiflix-0.0.1-SNAPSHOT/watchlistDAO
java:app/Tshiflix-0.0.1-SNAPSHOT/watchlistDAO
java:module/watchlistDAO
19:04:04,685 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
19:04:04,687 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
19:04:04,688 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
19:04:04,689 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 59) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be passivated.
19:04:04,867 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
19:04:04,869 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0006: Starting Services for CDI deployment: Tshiflix-0.0.1-SNAPSHOT.war
19:04:04,904 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 6.0)
19:04:04,904 INFO [org.jboss.weld.deployer] (MSC service thread 1-8) WFLYWELD0006: Starting Services for CDI deployment: Tshiflix2.war
19:04:04,904 INFO [org.jboss.weld.Version] (MSC service thread 1-3) WELD-000900: 2.3.2 (Final)
19:04:04,943 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = Tshiflix-0.0.1-SNAPSHOT.war_com.mysql.cj.jdbc.Driver_6_0
19:04:04,943 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = Tshiflix2.war_com.mysql.cj.jdbc.Driver_6_0
19:04:04,944 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0009: Starting weld service for deployment Tshiflix2.war
19:04:04,944 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) WFLYWELD0009: Starting weld service for deployment Tshiflix-0.0.1-SNAPSHOT.war
19:04:05,031 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 59) WFLYCLINF0002: Started client-mappings cache from ejb container
19:04:05,129 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 58) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'Tshiflix2.war#Watchlist'
19:04:05,129 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 59) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service 'Tshiflix-0.0.1-SNAPSHOT.war#Watchlist'
19:04:05,473 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 59) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
19:04:05,473 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 58) HHH000400: Using dialect: org.hibernate.dialect.MySQL5Dialect
19:04:05,517 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 58) Envers integration enabled? : true
19:04:05,517 INFO [org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread Pool -- 59) Envers integration enabled? : true
19:04:06,758 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 69) Initializing Mojarra 2.2.12 ( 20150720-0848 https://svn.java.net/svn/mojarra~svn/tags/2.2.12#14885) for context '/Tshiflix2'
19:04:06,758 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 66) Initializing Mojarra 2.2.12 ( 20150720-0848 https://svn.java.net/svn/mojarra~svn/tags/2.2.12#14885) for context '/Tshiflix-0.0.1-SNAPSHOT'
19:04:08,152 INFO [javax.enterprise.resource.webcontainer.jsf.config] (ServerService Thread Pool -- 69) Monitoring file:/Users/Tshili/Documents/Library/wildfly-10.0.0.Final/standalone/tmp/vfs/temp/temp33c1df153414a973/content-a01220796e5c75cd/WEB-INF/faces-config.xml for modifications
19:04:08,163 INFO [org.primefaces.webapp.PostConstructApplicationEventListener] (ServerService Thread Pool -- 69) Running on PrimeFaces 6.0
19:04:08,163 INFO [org.primefaces.webapp.PostConstructApplicationEventListener] (ServerService Thread Pool -- 66) Running on PrimeFaces 6.0
19:04:08,181 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 69) WFLYUT0021: Registered web context: /Tshiflix2
19:04:08,182 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 66) WFLYUT0021: Registered web context: /Tshiflix-0.0.1-SNAPSHOT
19:04:08,205 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "Tshiflix2.war" (runtime-name : "Tshiflix2.war")
19:04:08,206 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "Tshiflix-0.0.1-SNAPSHOT.war" (runtime-name : "Tshiflix-0.0.1-SNAPSHOT.war")
19:04:08,276 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
19:04:08,277 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
19:04:08,279 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 8076ms - Started 792 of 1066 services (394 services are lazy, passive or on-demand)
I found myself where is the problem. My web.xml wasn't good. I post the good one for somebody who will have the same issue than me
> <?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd" id="WebApp_ID" version="3.1">
<display-name>Watchlist</display-name>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>/Tshiflix-0.0.1-SNAPSHOT/Search.xhtml</welcome-file>
</welcome-file-list>
</web-app>
I have followed this link to install Wildfly on EC2 Linux instance. After it was installed I tried to run the server using
service wildfly start
After a while it threw an error.
It says wildfly server started with errors but the server was not started infact stopped right after it was started. This is my Log file.
2016-07-20 09:18:10,571 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
2016-07-20 09:18:11,255 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
2016-07-20 09:18:11,499 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = UTF-8
file.encoding.pkg = sun.io
file.separator = /
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = /opt/wildfly/jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/endorsed
java.ext.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
java.home = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre
java.io.tmpdir = /tmp
java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.net.preferIPv4Stack = true
java.runtime.name = OpenJDK Runtime Environment
java.runtime.version = 1.8.0_91-b14
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.util.logging.manager = org.jboss.logmanager.LogManager
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.8.0_91
java.vm.info = mixed mode
java.vm.name = OpenJDK 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.91-b14
javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
jboss.home.dir = /opt/wildfly
jboss.host.name = ip-172-31-25-47
jboss.modules.dir = /opt/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = ip-172-31-25-47
jboss.qualified.host.name = ip-172-31-25-47
jboss.server.base.dir = /opt/wildfly/standalone
jboss.server.config.dir = /opt/wildfly/standalone/configuration
jboss.server.data.dir = /opt/wildfly/standalone/data
jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
jboss.server.log.dir = /opt/wildfly/standalone/log
jboss.server.name = ip-172-31-25-47
jboss.server.persist.config = true
jboss.server.temp.dir = /opt/wildfly/standalone/tmp
line.separator =
logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
module.path = /opt/wildfly/modules
org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 4.4.11-23.53.amzn1.x86_64
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/classes
sun.boot.library.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = UTF-8
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /opt/wildfly-10.0.0.Final/bin
user.home = /root
user.language = en
user.name = root
user.timezone = Etc/UTC
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) VM Arguments: -D[Standalone] -Xms2048m -Xmx2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties
2016-07-20 09:18:16,598 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2016-07-20 09:18:16,664 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final
2016-07-20 09:18:16,708 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final
2016-07-20 09:18:16,919 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final
2016-07-20 09:18:17,066 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
2016-07-20 09:18:16,992 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
2016-07-20 09:18:17,085 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
2016-07-20 09:18:17,104 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
2016-07-20 09:18:16,975 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
2016-07-20 09:18:17,087 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
2016-07-20 09:18:17,363 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
2016-07-20 09:18:17,433 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,849 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,861 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final
2016-07-20 09:18:17,850 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
2016-07-20 09:18:18,081 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2016-07-20 09:18:18,162 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
2016-07-20 09:18:18,173 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2016-07-20 09:18:18,708 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
2016-07-20 09:18:19,244 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2016-07-20 09:18:19,731 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
2016-07-20 09:18:19,733 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
2016-07-20 09:18:19,943 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
2016-07-20 09:18:20,327 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:28080
2016-07-20 09:18:20,328 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
2016-07-20 09:18:21,779 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
2016-07-20 09:18:22,045 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
2016-07-20 09:18:22,208 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2016-07-20 09:18:22,208 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:18:23,028 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2016-07-20 09:18:23,028 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2016-07-20 09:18:23,029 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 13530ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)
2016-07-20 09:20:40,572 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
2016-07-20 09:20:40,617 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:20:40,762 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
2016-07-20 09:20:40,780 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending
2016-07-20 09:20:40,781 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 0.0.0.0:28080
2016-07-20 09:20:40,781 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2
2016-07-20 09:20:40,785 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.15.Final stopping
2016-07-20 09:20:40,815 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in 206ms
Looking at this log file I am unable to comprehend the issue which causing the server to stop.
Update-1:
Thanks to #James R. Perkins I looked at /var/log/wildfly/console.log and the issue is wildfly was unable to write to its child files. Like
Caused by: java.io.FileNotFoundException: /opt/wildfly/standalone/log/server.log (Permission denied)
Caused by: java.lang.IllegalStateException: WFLYDR0006: Directory /opt/wildfly/standalone/data/content is not writable
Even though wildfly is owner of wildfly parent folder
Do I have to make it the owner of all of its sub folders?
The solution to my particular problem was the issue of permissions. Only root had permissions but all the children didn't had wildfly as owner. Applying
chown -R
did the job. Thanks to #James R. Perkins I checked my console logs that were in /var/logs/wildfly/console.log i found the issue.
Currently, my service is running on http://localhost:8080/MyService/. I want to change localhost to service.example.com - http://service.example.com:8080/MyService/. I updated standalone-full.xml with the new alias.
<subsystem xmlns="urn:jboss:domain:web:2.1" default-virtual-server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" />
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="service.example.com"/>
</virtual-server>
</subsystem>
But it did not work. I am getting "This Webpage is not available" message. Please suggest.
Update:
Changed jboss-web.xml as above. When deploy my war file, I am getting 404 error.
jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<security-domain>java:/jaas/EmpMem</security-domain>
<context-root>/</context-root>
<virtual-host>service.example.com</virtual-host>
</jboss-web>
standalone-full.xml
Server Log:
16:09:21,705 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-7) Exception during createSubject()JBAS013303: Runtime Exception:: java.lang.RuntimeException: JBAS013303: Runtime Exception:
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:56)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:317)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1078)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1073)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1072)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.jboss.modules.ModuleNotFoundException: com.usaa.loginmodule:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.as.security.plugins.SecurityActions.getModuleClassLoader(SecurityActions.java:61)
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:47)
... 16 more
16:09:21,718 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:/usecom_sau]
16:09:21,734 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221013: Using NIO Journal
16:09:21,911 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock
16:09:21,912 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock
16:09:21,917 WARN [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
16:09:21,940 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started
16:09:22,009 INFO [org.jboss.web] (ServerService Thread Pool -- 61) JBAS018210: Register web context: /JBOSSWAR
16:09:22,035 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
16:09:22,083 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:22,110 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:22,163 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.23 (redhat)
16:09:22,170 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:22,352 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5455 for CORE protocol
16:09:22,354 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5445 for CORE protocol
16:09:22,355 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live
16:09:22,356 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.3.20.Final (2.3.20, 123) [43f01d80-b3cb-11e4-a1e5-0d8484f2438a]
16:09:22,371 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:09:22,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.fooQueue
16:09:22,376 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/queue/foo
16:09:22,377 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/foo
16:09:22,378 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
16:09:22,414 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
16:09:22,445 INFO [org.hornetq.ra] (MSC service thread 1-6) HornetQ resource adaptor started
16:09:22,446 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
16:09:22,447 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
16:09:22,594 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "JBOSSEAR.ear" (runtime-name : "JBOSSEAR.ear")
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "ent_securityprefs_empMemService.war" (runtime-name : "ent_securityprefs_empMemService.war")
16:09:22,631 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:09:22,718 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 3347ms - Started 360 of 399 services (2 services failed or missing dependencies, 75 services are lazy, passive or on-demand)
16:09:27,677 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:27,686 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 14ms
16:09:27,757 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:27,759 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.jboss.as.weld.webtier.jsp.JspInitializationListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.web.deployment."emp.example.com"./.realm (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
16:09:42,782 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found ent_securityprefs_empMemService.war in deployment directory. To trigger deployment create a file called ent_securityprefs_empMemService.war.dodeploy
16:09:42,788 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:42,834 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:42,841 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:42,843 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:42,889 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:42,893 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "ent_securityprefs_empMemService.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.web.deployment.\"emp.example.com\"./" => "org.jboss.msc.service.StartException in service jboss.web.deployment.\"emp.example.com\"./: Failed to start service
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists"}}
16:09:42,894 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:42,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 4ms
16:09:42,897 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (no longer required)
service jboss.web.deployment."emp.example.com"./.realm (no longer required)
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
you need to specify an appropriate virtual-host definition in your jboss-web.xml descriptor.
<jboss-web>
<context-root>/</context-root>
<virtual-host>www.mydot.com</virtual-host>
</jboss-web>
Click here to read more
I'm trying to get a web app up and running on jboss 5 in eclipse and i'm not getting any errors in the log and when i hit http://localhost:8080/WebDataViewer, i just get the default http 404 error page.
When i hit http://localhost:8080/ i get the default jboss page with some links on it.
I've not worked with jboss before, but can anyone help figure out how i can access my app or how i can troubleshoot this?
10:07:39,706 INFO [ServerImpl] Starting JBoss (Microcontainer)...
10:07:39,707 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)
10:07:39,707 INFO [ServerImpl] Bootstrap URL: null
10:07:39,707 INFO [ServerImpl] Home Dir: C:\jboss-5.1.0.GA
10:07:39,708 INFO [ServerImpl] Home URL: file:/C:/jboss-5.1.0.GA/
10:07:39,708 INFO [ServerImpl] Library URL: file:/C:/jboss-5.1.0.GA/lib/
10:07:39,708 INFO [ServerImpl] Patch URL: null
10:07:39,708 INFO [ServerImpl] Common Base URL: file:/C:/jboss-5.1.0.GA/common/
10:07:39,708 INFO [ServerImpl] Common Library URL: file:/C:/jboss-5.1.0.GA/common/lib/
10:07:39,709 INFO [ServerImpl] Server Name: default
10:07:39,709 INFO [ServerImpl] Server Base Dir: C:\jboss-5.1.0.GA\server
10:07:39,709 INFO [ServerImpl] Server Base URL: file:/C:/jboss-5.1.0.GA/server/
10:07:39,709 INFO [ServerImpl] Server Config URL: file:/C:/jboss-5.1.0.GA/server/default/conf/
10:07:39,709 INFO [ServerImpl] Server Home Dir: C:\jboss-5.1.0.GA\server\default
10:07:39,709 INFO [ServerImpl] Server Home URL: file:/C:/jboss-5.1.0.GA/server/default/
10:07:39,709 INFO [ServerImpl] Server Data Dir: C:\jboss-5.1.0.GA\server\default\data
10:07:39,709 INFO [ServerImpl] Server Library URL: file:/C:/jboss-5.1.0.GA/server/default/lib/
10:07:39,710 INFO [ServerImpl] Server Log Dir: C:\jboss-5.1.0.GA\server\default\log
10:07:39,710 INFO [ServerImpl] Server Native Dir: C:\jboss-5.1.0.GA\server\default\tmp\native
10:07:39,710 INFO [ServerImpl] Server Temp Dir: C:\jboss-5.1.0.GA\server\default\tmp
10:07:39,710 INFO [ServerImpl] Server Temp Deploy Dir: C:\jboss-5.1.0.GA\server\default\tmp\deploy
10:07:40,279 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
10:07:40,898 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
10:07:40,900 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
10:07:41,132 INFO [CopyMechanism] VFS temp dir: C:\jboss-5.1.0.GA\server\default\tmp
10:07:41,133 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
10:07:42,399 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.
10:07:42,399 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_35-b10)
10:07:42,399 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.
10:07:42,399 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
10:07:42,399 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dfile.encoding=Cp1252
10:07:42,425 INFO [JMXKernel] Legacy JMX core initialized
10:07:44,183 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey#2ee634bf[domain=default, server=default, name=default]
10:07:45,435 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
10:07:50,839 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
10:07:50,839 INFO [NativeServerConfig] 3.1.2.GA
10:07:51,473 INFO [AttributeCallbackItem] Owner callback not implemented.
10:07:52,334 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl#5de82b72[ defaultDomain='jboss' ]
10:08:06,536 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,536 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,537 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:06,537 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext#1493227242{vfsfile:/C:/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
10:08:08,928 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
10:08:09,029 INFO [MailService] Mail Service bound to java:/Mail
10:08:11,006 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
10:08:11,020 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
10:08:11,073 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
10:08:11,111 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
10:08:11,111 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
10:08:11,312 INFO [TransactionManagerService] Initializing recovery manager
10:08:11,436 INFO [TransactionManagerService] Recovery manager configured
10:08:11,436 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
10:08:11,457 INFO [TransactionManagerService] Starting transaction recovery manager
10:08:12,016 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.6.0_35\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/bin/server;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/bin;C:/Program Files/Java/jdk1.6.0_35/bin/../jre/lib/amd64;c:\program files\apache-maven-3.0.x\bin;C:\Ruby192\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\sybase15_0_7\OCS-15_0\bin;C:\sybase15_0_7\OCS-15_0\dll;C:\sybase15_0_7\OCS-15_0\lib3p;C:\sybase15_0_7\DataAccess\ADONET\dll;C:\sybase15_0_7\DataAccess\ODBC\dll;C:\sybase15_0_7\DataAccess\OLEDB\dll;C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\MySQL\MySQL Server 5.5\bin;c:\Program Files\Stellent\IBPM;C:\PROGRA~2\IBM\SQLLIB\BIN;C:\PROGRA~2\IBM\SQLLIB\FUNCTION;C:\PROGRA~2\IBM\SQLLIB\bin;%JAVA_HOME%\bin;C:\Program Files\apache-maven-3.0.4\bin;C:\Oracle_Instant_Client(32bit)\instantclient_11_2;C:\Program Files (x86)\Git\cmd;C:\Program Files\TortoiseSVN\bin;C:\Program Files\eclipse;;.
10:08:12,087 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
10:08:12,089 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:08:12,122 INFO [StandardService] Starting service jboss.web
10:08:12,130 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
10:08:12,235 INFO [Catalina] Server startup in 145 ms
10:08:12,258 INFO [TomcatDeployment] deploy, ctxPath=/web-console
10:08:12,993 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
10:08:13,068 INFO [TomcatDeployment] deploy, ctxPath=/invoker
10:08:13,242 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
10:08:13,285 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
10:08:13,310 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
10:08:13,324 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
10:08:13,353 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
10:08:13,422 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
10:08:13,442 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
10:08:13,445 INFO [RAMJobStore] RAMJobStore initialized.
10:08:13,446 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
10:08:13,446 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
10:08:13,446 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
10:08:13,769 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
10:08:14,145 INFO [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started
10:08:14,220 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
10:08:14,269 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,269 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#4bb8e77c started
10:08:14,271 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
10:08:14,272 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,272 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#28062593 started
10:08:14,272 INFO [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
10:08:14,282 INFO [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
10:08:14,283 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
10:08:14,283 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory#30726eca started
10:08:14,419 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
10:08:14,705 INFO [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar
10:08:14,712 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
10:08:14,712 INFO [JBossASKernel] with dependencies:
10:08:14,712 INFO [JBossASKernel] and demands:
10:08:14,712 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
10:08:14,712 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,713 INFO [JBossASKernel] and supplies:
10:08:14,713 INFO [JBossASKernel] Class:org.jboss.profileservice.spi.ProfileService
10:08:14,713 INFO [JBossASKernel] jndi:SecureProfileService/remote
10:08:14,713 INFO [JBossASKernel] jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
10:08:14,713 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,714 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
10:08:14,714 INFO [JBossASKernel] with dependencies:
10:08:14,714 INFO [JBossASKernel] and demands:
10:08:14,714 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,714 INFO [JBossASKernel] and supplies:
10:08:14,714 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
10:08:14,714 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
10:08:14,714 INFO [JBossASKernel] jndi:SecureDeploymentManager/remote
10:08:14,714 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,715 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
10:08:14,715 INFO [JBossASKernel] with dependencies:
10:08:14,715 INFO [JBossASKernel] and demands:
10:08:14,715 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService
10:08:14,715 INFO [JBossASKernel] and supplies:
10:08:14,715 INFO [JBossASKernel] jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
10:08:14,715 INFO [JBossASKernel] Class:org.jboss.deployers.spi.management.ManagementView
10:08:14,715 INFO [JBossASKernel] jndi:SecureManagementView/remote
10:08:14,715 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
10:08:14,722 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#6cdc5f76{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,723 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#240c5895{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,723 INFO [EJB3EndpointDeployer] Deploy AbstractBeanMetaData#1cfd0695{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
10:08:14,877 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
10:08:14,887 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
10:08:15,010 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface
10:08:15,055 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
10:08:15,056 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
10:08:15,064 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureManagementView/remote - EJB3.x Default Remote Business Interface
SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface
10:08:15,107 INFO [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
10:08:15,108 INFO [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
10:08:15,150 INFO [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:
SecureProfileService/remote - EJB3.x Default Remote Business Interface
SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface
10:08:15,778 INFO [TomcatDeployment] deploy, ctxPath=/admin-console
10:08:15,930 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
10:08:19,678 INFO [TomcatDeployment] deploy, ctxPath=/
10:08:23,577 INFO [TomcatDeployment] deploy, ctxPath=/WebDataViewer
10:08:23,825 INFO [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/WebDataViewer'
10:08:24,812 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
10:08:25,069 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
10:08:25,093 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
10:08:25,099 INFO [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221634)] Started in 45s:387ms
Snippet from web.xml
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
The address http://localhost:8080/WebDataViewer just points to the context root of the application, so it will just work if you've a default page defined (such as index.jsp). If you've no default resource for the context root WebDataViewer, you'll have to especify a resource name (a resource can be a servlet, a jsp, jsf ...), for example: http://localhost:8080/WebDataViewer/myservlet.
Usually you can look at the resources defined for your application in the WEB-INF/web.xml of your application, for example:
<servlet-mapping>
<servlet-name>MyServlet</servlet-name>
<url-pattern>/myservlet</url-pattern>
</servlet-mapping>
In your case, according to your web.xml, it seems you're using JSF. So I guess that you should have some xhtml files in the root of your war (or at least in any subdirectory). For example if your war is like:
WebDataViewer.war
|
|--page.xhtml
|
|--WEB-INF
| |
| |- web.xml
| |- ...
|- ...
A valid address would be: http://localhost:8080/WebDataViewer/page.xhtml.