I am trying to deploy a hello world web application in my local JBOSS.
here is my Index.jsp
<%# page language="java" contentType="text/html; charset=BIG5"
pageEncoding="BIG5"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=BIG5">
<title>hello</title>
</head>
<body>
<h1>Thank you for coming!</h1>
</body>
</html>
Also, I have web.xml configured like this:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd" id="WebApp_ID" version="3.0">
<display-name>HelloWorld</display-name>
<welcome-file-list>
<welcome-file>Index.jsp</welcome-file>
</welcome-file-list>
</web-app>
But when I run as server, I got following error:
12:48:51,568 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 59) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("configuration" => "handler"),
("file" => "welcome-content")
]) - failure description: "WFLYUT0095: the path ['C:\\JBOSS_7.1/welcome-content'] doesn't exist on file system"
12:48:51,576 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0012: Started server default-server.
12:48:51,578 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
12:48:51,618 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
12:48:51,647 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0493: EJB subsystem suspension complete
12:48:51,757 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
12:48:51,777 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/NEWTMISDEV]
12:48:51,778 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
12:48:51,786 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-8) WFLYDM0111: Keystore C:\JBOSS_7.1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
12:48:51,790 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) WFLYDS0013: Started FileSystemDeploymentService for directory C:\JBOSS_7.1\standalone\deployments
12:48:51,799 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "HelloWorld.jar" (runtime-name: "HelloWorld.jar")
12:48:52,076 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
12:48:52,129 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
12:48:52,341 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-6) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final-redhat-1
12:48:52,556 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 62) WFLYCLINF0002: Started client-mappings cache from ejb container
12:48:52,601 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("host" => "default-host"),
("location" => "/")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.extension.undertow.handler.welcome-content"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["org.wildfly.undertow.host.location.default-server.default-host./ is missing [org.wildfly.extension.undertow.handler.welcome-content]"]
}
12:48:52,626 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "HelloWorld.jar" (runtime-name : "HelloWorld.jar")
12:48:52,629 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service org.wildfly.extension.undertow.handler.welcome-content (missing) dependents: [service org.wildfly.undertow.host.location.default-server.default-host./]
I am new to JBOSS, I have no idea what does
Related
Description
Since the latest OpenJDK 8 patch for Ubuntu the WildFly deployment loops in redeployments. Everytime the depoyment finished the DeploymentScanner starts a redeployment and repeat this endlessly.
Used technology
Ubuntu Version: Ubuntu 20.04.3 LTS
Java Version: openjdk version "1.8.0_312"
JRE Version: OpenJDK Runtime Environment (build 1.8.0_312-8u312-b07-0ubuntu1~20.04-b07)
WildFly Version: 26.0.0.Final
Deployment: WAR-file; generated from maven archtypes maven-archetype-webapp
State of knowledge
When starting the vanilla WF with the WAR in the standalone mode, I get the following (looping) log output:
14:17:19,243 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8182
14:17:19,278 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
14:17:19,655 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Registered web context: /TestWebApp
14:17:19,667 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "TestWebApp.war" (runtime-name : "TestWebApp.war")
14:17:19,682 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0022: Unregistered web context: /TestWebApp
14:17:19,688 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment TestWebApp.war (runtime-name: TestWebApp.war) in 8ms
14:17:19,689 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "TestWebApp.war" (runtime-name: "TestWebApp.war")
14:17:19,719 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 23) WFLYUT0021: Registered web context: /TestWebApp
14:17:19,782 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9991/management
14:17:19,782 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9991
14:17:19,783 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 1972ms - Started 410 of 660 services (406 services are lazy, passive or on-demand)
14:17:19,803 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0013: Redeployed "TestWebApp.war"
14:17:24,870 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 23) WFLYUT0022: Unregistered web context: /TestWebApp
14:17:24,872 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment TestWebApp.war (runtime-name: TestWebApp.war) in 2ms
14:17:24,873 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "TestWebApp.war" (runtime-name: "TestWebApp.war")
14:17:24,905 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0021: Registered web context: /TestWebApp
14:17:24,914 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0016: Replaced deployment "TestWebApp.war" with deployment "TestWebApp.war"
14:17:29,979 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0022: Unregistered web context: /TestWebApp
14:17:29,985 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment TestWebApp.war (runtime-name: TestWebApp.war) in 6ms
14:17:29,986 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "TestWebApp.war" (runtime-name: "TestWebApp.war")
14:17:30,010 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 19) WFLYUT0021: Registered web context: /TestWebApp
14:17:30,019 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0013: Redeployed "TestWebApp.war"
After I enabled the debug log level I saw that the DeploymentScanner detected a changed in the deployment folder which triggers the redeployment:
15:54:55,206 DEBUG [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) Deployment scan of [***/standalone/deployments] found update action [{
"operation" => "redeploy",
"address" => [("deployment" => "TestWebApp.war")],
"owner" => [
("subsystem" => "deployment-scanner"),
("scanner" => "default")
]
}]
After I set the auto-deploy-zipped="false" attribute in the deployment scanner subsystem in the standalone.xml the deployment redeployed just one time and than ran normaly.
To be honest, I am overwhelmed by how I can start the application "normally" - without manually deactivating redeployments? Last night everything went normally; the JDK update came this morning and now I've been working on the topic for a few hours. I can not find any related changes in the changelog of the patch.
Thank you for your ideas and help!
I found in other threads others having a problem similar to mine but none of the solutions worked for me.
I'm migrating from jBoss 5 to Wildfly 18. I followed the official guide to migrate.
I set up the datasources in the standalone.xml file, and they are correctly connected (the admin console test - localhost:9990 - confirms that the connections to the DB are up and running).
Anyway, I got some errors while deploying my application.
It seems that there is something wrong with the services that are supposed to use the datasources and the connections.
Can anyone please take a look at the error log here below? Is anything familiar for anyone?
I cannot figure it out ...
Thanks in advance
17:16:47,804 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
17:16:48,855 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
17:16:48,863 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
17:16:48,940 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) starting
17:16:49,818 INFO [org.wildfly.security] (ServerService Thread Pool -- 28) ELY00001: WildFly Elytron version 1.10.4.Final
17:16:51,270 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' 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.
17:16:51,284 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 31) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' 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.
17:16:51,544 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found myApplication.war in deployment directory. To trigger deployment create a file called myApplication.war.dodeploy
17:16:51,565 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
17:16:51,579 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.7.3.Final
17:16:51,585 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.7.3.Final
17:16:51,612 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 72) 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.
17:16:51,618 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem.
17:16:51,626 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
17:16:51,626 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
17:16:51,632 INFO [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem
17:16:51,633 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem
17:16:51,637 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
17:16:51,643 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=5.0.3.Final
17:16:51,646 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
17:16:51,651 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main]
17:16:51,652 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
17:16:51,653 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.17.Final)
17:16:51,687 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.27.Final starting
17:16:51,738 INFO [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service
17:16:51,759 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
17:16:51,812 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 6.4)
17:16:51,815 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path 'SERVER_PATH\wildfly-18.0.1.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
17:16:51,819 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = sqlserver
17:16:51,985 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 24 core threads with 192 task threads based on your 12 available processors
17:16:51,989 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) 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.
17:16:51,989 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.
17:16:52,007 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.9.1.Final
17:16:52,010 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.15.Final
17:16:52,014 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
17:16:52,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
17:16:52,045 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
17:16:52,263 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
17:16:52,290 INFO [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-2) IJ020018: Enabling <validate-on-match> for java:jboss/datasources/datasource1
17:16:52,290 INFO [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-8) IJ020018: Enabling <validate-on-match> for java:jboss/datasources/datasource2
...
other datasources enabled
...
17:16:52,354 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/datasource1]
17:16:52,354 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/datasource2]
...
other datasources bind
...
17:16:53,791 INFO [org.jboss.as.patching] (MSC service thread 1-1) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
17:16:53,798 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore SERVER_PATH\wildfly-18.0.1.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
17:16:53,801 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory SERVER_PATH\wildfly-18.0.1.Final\standalone\deployments
17:16:53,806 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "myApplication.war" (runtime-name: "myApplication.war")
17:16:53,815 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
17:16:54,236 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.3)
17:16:55,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry toolbox.jar in SERVER_PATH/wildfly-18.0.1.Final/standalone/deployments/myApplication.war/WEB-INF/lib/iText-2.0.8.jar does not point to a valid jar for a Class-Path reference.
17:16:55,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry bcmail-jdk14-138.jar in SERVER_PATH/wildfly-18.0.1.Final/standalone/deployments/myApplication.war/WEB-INF/lib/iText-2.0.8.jar does not point to a valid jar for a Class-Path reference.
17:16:55,095 WARN [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0059: Class Path entry bcprov-jdk14-138.jar in SERVER_PATH/wildfly-18.0.1.Final/standalone/deployments/myApplication.war/WEB-INF/lib/iText-2.0.8.jar does not point to a valid jar for a Class-Path reference.
17:16:55,456 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for datasource1
17:16:55,456 INFO [org.jboss.as.jpa] (MSC service thread 1-6) WFLYJPA0002: Read persistence.xml for datasource2
...
other persistence.xml reading
...
17:16:56,949 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5) ISPN000128: Infinispan version: Infinispan 'Infinity Minus ONE +2' 9.4.16.Final
17:16:57,047 WARN [org.jboss.as.ee] (MSC service thread 1-8) WFLYEE0007: Not installing optional component org.springframework.web.context.ContextLoaderListener due to an exception (enable DEBUG log level to see the cause)
17:16:57,239 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 76) WFLYCLINF0002: Started client-mappings cache from ejb container
17:16:57,508 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 6.4)
17:16:57,538 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) WFLYJCA0018: Started Driver service with driver-name = myApplication.war_com.microsoft.sqlserver.jdbc.SQLServerDriver_6_4
17:16:57,795 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "myApplication.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => [
"jboss.naming.context.java.datasource1",
"jboss.naming.context.java.datasource2",
...
other required services not installed
...
],
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.persistenceunit.\"myApplication.war#datasource1\" is missing [jboss.naming.context.java.datasource1]",
"jboss.persistenceunit.\"myApplication.war#datasource2\" is missing [jboss.naming.context.java.datasource2]"
...
other missing dependencies
...
]
}
17:16:57,802 INFO [org.jboss.as.server] (ServerService Thread Pool -- 44) WFLYSRV0010: Deployed "myApplication.war" (runtime-name : "myApplication.war")
17:16:57,806 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.naming.context.java.dbDB1 (missing) dependents: [service jboss.persistenceunit."myApplication.war#datasource1", service jboss.persistenceunit."myApplication.war#datasource1".__FIRST_PHASE__]
service jboss.naming.context.java.dbDB2 (missing) dependents: [service jboss.persistenceunit."myApplication.war#datasource2".__FIRST_PHASE__, service jboss.persistenceunit."myApplication.war#datasource2"]
...
other missing dependencies
...
WFLYCTL0448: 350 additional services are down due to their dependencies being missing or failed
17:16:57,835 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
17:16:57,838 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
17:16:57,839 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
17:16:57,839 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 18.0.1.Final (WildFly Core 10.0.3.Final) started (with errors) in 12801ms - Started 1754 of 2359 services (389 services failed or missing dependencies, 470 services are lazy, passive or on-demand)
I'm trying to implement a simple method in my JAX-WS project that, for the moment, prints to the console every second. I found this simple guide and I have tried to implement it to my current working project.
My TimerService.java looks like this:
package brass.ducks.controller;
import javax.ejb.EJB;
import javax.ejb.Schedule;
import javax.ejb.Singleton;
#Singleton
public class TimerService {
#EJB
HelloService helloService;
#Schedule(second="*/1", minute="*",hour="*", persistent=false)
public void doWork(){
System.out.println("timer: " + helloService.sayHello());
}
}
And my HelloService.java looks like this:
package brass.ducks.controller;
import javax.ejb.Stateless;
#Stateless
public class HelloService {
public String sayHello(){
return "Hello from control: " + System.currentTimeMillis();
}
}
I noted that the tutorial mentioned something about how to deploy? Would this be covered by just deploying the project on my local WildFly server or does it require something else?
Here is my stacktrace too:
14:53:03,672 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
14:53:04,119 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:53:04,239 INFO [org.jboss.as] (MSC service thread 1-6) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
14:53:06,683 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment BrassDucks.war
14:53:06,708 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found BrassDucks.war in deployment directory. To trigger deployment create a file called BrassDucks.war.dodeploy
14:53:06,829 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:53:06,860 INFO [org.xnio] (MSC service thread 1-6) XNIO version 3.3.4.Final
14:53:06,873 INFO [org.xnio.nio] (MSC service thread 1-6) XNIO NIO Implementation Version 3.3.4.Final
14:53:06,981 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 4.0.18.Final
14:53:07,003 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.
14:53:07,044 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:53:07,063 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
14:53:07,072 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:53:07,303 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
14:53:07,359 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.3.15.Final starting
14:53:07,373 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.3.15.Final starting
14:53:07,378 INFO [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem
14:53:07,446 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
14:53:07,470 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
14:53:07,475 INFO [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=4.9.4.Final
14:53:07,510 INFO [org.jboss.as.naming] (MSC service thread 1-4) WFLYNAM0003: Starting Naming Service
14:53:07,530 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
14:53:07,552 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:53:07,559 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:53:07,782 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0018: Started Driver service with driver-name = h2
14:53:08,133 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path 'C:\wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:53:08,154 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) WFLYUT0012: Started server default-server.
14:53:08,183 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
14:53:08,221 INFO [org.jboss.as.ejb3] (MSC service thread 1-7) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 16 (per class), which is derived from the number of CPUs on this host.
14:53:08,238 INFO [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 64 (per class), which is derived from thread worker pool sizing.
14:53:08,882 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
14:53:09,092 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:53:09,237 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "mysql-connector-java-5.1.39-bin.jar" (runtime-name: "mysql-connector-java-5.1.39-bin.jar")
14:53:09,253 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "BrassDucks.war" (runtime-name: "BrassDucks.war")
14:53:09,280 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-6) WFLYDS0013: Started FileSystemDeploymentService for directory C:\wildfly-10.0.0.Final\standalone\deployments
14:53:09,374 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\wildfly-10.0.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\wildfly-10.0.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\wildfly-10.0.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\wildfly-10.0.0.Final\standalone\data\activemq\paging)
14:53:09,587 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal
14:53:09,823 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
14:53:10,757 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
14:53:10,824 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
14:53:10,835 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP
14:53:10,857 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:53:10,865 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
14:53:10,868 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP
14:53:11,045 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-4) WFLYIIOP0009: CORBA ORB Service started
14:53:11,264 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:53:11,266 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
14:53:11,358 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.39-bin.jar_com.mysql.jdbc.Driver_5_1
14:53:11,544 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_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
14:53:11,559 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/MySqlNorthwindDS]
14:53:11,605 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/BrassDucksDS]
14:53:11,634 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:/MySqlEquitiesDS]
14:53:12,241 INFO [org.jboss.as.protocol] (management I/O-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]
14:53:12,479 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:53:12,483 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:53:12,483 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:53:12,484 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:53:12,614 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221007: Server is now live
14:53:12,615 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-011 [nodeID=ad393a41-759e-11e6-8402-b9b09451d246]
14:53:12,660 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 64) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
14:53:12,696 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 67) AMQ221003: trying to deploy queue jms.queue.Tasks
14:53:12,726 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221003: trying to deploy queue jms.queue.ExpiryQueue
14:53:12,731 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue jms.queue.DLQ
14:53:12,737 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
14:53:12,796 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0007: Registered connection factory java:/JmsXA
14:53:12,895 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-7) Resource adaptor started
14:53:12,895 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-7) IJ020002: Deployed: file://RaActivatoractivemq-ra
14:53:12,897 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-7) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
14:53:12,898 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
14:53:15,665 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) WFLYWELD0003: Processing weld deployment BrassDucks.war
14:53:15,797 INFO [org.jboss.as.protocol] (management I/O-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 1,5,management-handler-thread]
14:53:15,811 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.2.3.Final
14:53:15,930 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'BrassDucksDAO' in deployment unit 'deployment "BrassDucks.war"' are as follows:
java:global/BrassDucks/BrassDucksDAO!brass.ducks.model.BrassDucksDAO
java:app/BrassDucks/BrassDucksDAO!brass.ducks.model.BrassDucksDAO
java:module/BrassDucksDAO!brass.ducks.model.BrassDucksDAO
java:global/BrassDucks/BrassDucksDAO
java:app/BrassDucks/BrassDucksDAO
java:module/BrassDucksDAO
14:53:15,931 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'Trader' in deployment unit 'deployment "BrassDucks.war"' are as follows:
java:global/BrassDucks/Trader!brass.ducks.model.Trader
java:app/BrassDucks/Trader!brass.ducks.model.Trader
java:module/Trader!brass.ducks.model.Trader
java:global/BrassDucks/Trader
java:app/BrassDucks/Trader
java:module/Trader
14:53:15,932 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'HelloService' in deployment unit 'deployment "BrassDucks.war"' are as follows:
java:global/BrassDucks/HelloService!brass.ducks.controller.HelloService
java:app/BrassDucks/HelloService!brass.ducks.controller.HelloService
java:module/HelloService!brass.ducks.controller.HelloService
java:global/BrassDucks/HelloService
java:app/BrassDucks/HelloService
java:module/HelloService
14:53:15,932 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-2) WFLYEJB0473: JNDI bindings for session bean named 'TimerService' in deployment unit 'deployment "BrassDucks.war"' are as follows:
java:global/BrassDucks/TimerService!brass.ducks.controller.TimerService
java:app/BrassDucks/TimerService!brass.ducks.controller.TimerService
java:module/TimerService!brass.ducks.controller.TimerService
java:global/BrassDucks/TimerService
java:app/BrassDucks/TimerService
java:module/TimerService
14:53:16,333 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."BrassDucks.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."BrassDucks.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "BrassDucks.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0052: Failed to install component TimerService
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:109)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
... 5 more
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.module.BrassDucks.BrassDucks.TimerService is already registered
at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2401)
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deployComponent(ComponentInstallProcessor.java:198)
at org.jboss.as.ee.component.deployers.ComponentInstallProcessor.deploy(ComponentInstallProcessor.java:101)
... 6 more
14:53:16,377 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "BrassDucks.war")]) - failure description: {
"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"BrassDucks.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"BrassDucks.war\".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment \"BrassDucks.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0052: Failed to install component TimerService
Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.naming.context.java.module.BrassDucks.BrassDucks.TimerService is already registered"},
"WFLYCTL0180: Services with missing/unavailable dependencies" => [
"jboss.deployment.unit.\"BrassDucks.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"BrassDucks.war\".beanmanager]",
"jboss.deployment.unit.\"BrassDucks.war\".batch.environment is missing [jboss.deployment.unit.\"BrassDucks.war\".beanmanager]"
]
}
14:53:16,427 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mysql-connector-java-5.1.39-bin.jar" (runtime-name : "mysql-connector-java-5.1.39-bin.jar")
14:53:16,477 INFO [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "BrassDucks.war" (runtime-name : "BrassDucks.war")
14:53:16,493 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.deployment.unit."BrassDucks.war".beanmanager (missing) dependents: [service jboss.deployment.unit."BrassDucks.war".batch.environment, service jboss.deployment.unit."BrassDucks.war".weld.weldClassIntrospector]
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."BrassDucks.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."BrassDucks.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "BrassDucks.war"
14:53:16,782 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:53:16,782 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:53:16,783 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started (with errors) in 13851ms - Started 395 of 689 services (3 services failed or missing dependencies, 401 services are lazy, passive or on-demand)
14:53:16,887 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0028: Stopped deployment BrassDucks.war (runtime-name: BrassDucks.war) in 60ms
14:53:17,087 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "BrassDucks.war" (runtime-name: "BrassDucks.war")
14:53:17,088 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."BrassDucks.war".INSTALL
14:53:21,595 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found BrassDucks.war in deployment directory. To trigger deployment create a file called BrassDucks.war.dodeploy
Try using the following steps:
These are the steps I followed to resolve the issue.
1.Stop the Server.
2.Go to deployment path.
3.Manually deleted the existing project in deployment folder.
4.Restarted the server
5.Deploy the application again.
because From the error, it looks like ".BrassDucks.BrassDucks.TimerService" already deployed on the server
iam trying to run my enterprise application project but it does not work.
WildFly cant find the index.xhtml file and giving a 404 error and it gives ServiceNotFoundException and a StartException.
The war folder has the following structure.
WebContent
META-INF
WEB-INF
faces-config.xml
web.xml
index.xhtml
The error message is the following:
11:40:56,051 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "CustomerManagementEJB.jar" of deployment "CustomerManagement.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_45]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_45]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_45]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:668) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:278)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:155)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:82)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [wildfly-server-8.2.0.Final.jar:8.2.0.Final]
... 5 more
11:40:56,337 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
11:40:56,384 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
11:40:56,387 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
11:40:56,448 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) JBAS010417: Started Driver service with driver-name = mysql-connector-java-5.1.35-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
11:40:56,448 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) JBAS010417: Started Driver service with driver-name = mysql-connector-java-5.1.35-bin.jar_com.mysql.jdbc.Driver_5_1
11:40:56,453 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/VideoTrainingDS]
11:40:56,457 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/BookDS]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found"}}
11:40:56,608 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "mysql-connector-java-5.1.35-bin.jar" (runtime-name : "mysql-connector-java-5.1.35-bin.jar")
11:40:56,610 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "CustomerManagement.ear" (runtime-name : "CustomerManagement.ear")
11:40:56,613 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "CustomerManagementEJB.jar" of deployment "CustomerManagement.ear"
11:40:56,647 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
11:40:56,647 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
11:40:56,648 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 6202ms - Started 242 of 301 services (3 services failed or missing dependencies, 91 services are lazy, passive or on-demand)
11:40:56,913 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: CustomerManagementEJB.jar) in 9ms
11:40:56,913 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015974: Stopped subdeployment (runtime-name: CustomerManagementWeb.war) in 9ms
11:40:56,915 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment CustomerManagement.ear (runtime-name: CustomerManagement.ear) in 11ms
11:40:57,000 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "CustomerManagement.ear" (runtime-name: "CustomerManagement.ear")
11:40:57,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."CustomerManagement.ear"."CustomerManagementEJB.jar".PARSE
11:41:01,689 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found CustomerManagement.ear in deployment directory. To trigger deployment create a file called CustomerManagement.ear.dodeploy
Try staring Wildfly with standalone.sh/bat -c standalone-full.xml
I am getting following error while deploying our EAR to JBoss AS 7.1 as a standalone deployment. Please see the server error log and help me out in what I need to do for it to start functioning correctly. Thank You
12:21:47,165 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
12:21:47,167 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
12:21:47,211 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
12:21:47,211 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
12:21:47,212 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
12:21:47,215 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
12:21:47,219 INFO [org.jboss.as.security] (MSC service thread 1-5) JBAS013100: Current PicketBox version=4.0.7.Final
12:21:47,232 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
12:21:47,250 INFO [org.jboss.as.connector] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
12:21:47,262 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:21:47,328 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:21:47,467 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
12:21:47,624 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8085
12:21:47,658 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory D:\jboss-as-7.1.1.Final\standalone\deployments
12:21:47,659 INFO [org.jboss.as.remoting] (MSC service thread 1-8) JBAS017100: Listening on /127.0.0.1:4447
12:21:47,660 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on /127.0.0.1:9999
12:21:47,808 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:21:48,018 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.ojdbc14-10_2_0_5_jar (missing) dependents: [service jboss.data-source.java:/jdbc/DefaultDS]
12:21:48,036 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "Shrisurance.ear"
12:21:54,210 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: Failed to process phase STRUCTURE of deployment "Shrisurance.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_25]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_25]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to get manifest for deployment "/D:/jboss-as-7.1.1.Final/bin/content/Shrisurance.ear/Shrisurance.war"
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:73) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
Caused by: java.io.IOException: invalid header field
at java.util.jar.Attributes.read(Attributes.java:393) [rt.jar:1.6.0_25]
at java.util.jar.Manifest.read(Manifest.java:182) [rt.jar:1.6.0_25]
at java.util.jar.Manifest.<init>(Manifest.java:52) [rt.jar:1.6.0_25]
at org.jboss.vfs.VFSUtils.readManifest(VFSUtils.java:216) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFSUtils.getManifest(VFSUtils.java:199) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.as.server.deployment.module.ManifestAttachmentProcessor.deploy(ManifestAttachmentProcessor.java:69) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 6 more
12:21:54,257 INFO [org.jboss.as] (MSC service thread 1-5) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:21:54,257 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Shrisurance.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Shrisurance.ear\""}}
12:21:54,258 ERROR [org.jboss.as] (MSC service thread 1-5) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7927ms - Started 136 of 215 services (3 services failed or missing dependencies, 74 services are passive or on-demand)
12:21:54,266 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment Shrisurance.ear in 7ms
12:21:54,267 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."Shrisurance.ear".STRUCTURE: Failed to process phase STRUCTURE of deployment "Shrisurance.ear"
12:21:54,277 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"Shrisurance.ear\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Shrisurance.ear\""}}}}
12:22:02,431 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011942: Stopping OSGi Framework
Case 1 : Looking from log
New missing/unsatisfied dependencies:
service jboss.jdbc-driver.ojdbc14-10_2_0_5_jar
It is found that you are using ojdbc14 version of jar. It is for JDK 1.4. If you are using JDK 1.4+ version then use ojdbc14+ driver. Latest Oracle Driver Download Link
Modify module.xml ( # jboss-as-web-7.0.2.Final\modules\com\oracle\ojdbcXXX\main )
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.oracle.ojdbcXXX">
<resources>
<resource-root path="ojdbcXXX.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
</dependencies>
</module>
Add ojdbcXXX.jar ( # jboss-as-web-7.0.2.Final\modules\com\oracle\ojdbcXXX\main )
Define Data-source in standalone.xml
<datasource jndi-name="java:/OracleDS" pool-name="OracleDS">
<connection-url>jdbc:oracle:thin:#host:port:SID</connection-url>
<driver>ojdbcXXX</driver>
</datasource>
<drivers>
<driver name="ojdbcXXX" module="com.oracle.ojdbcXXX">
<xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
</driver>
</drivers>
Case 2 : Include other deployments in EAR
JBoss find that dependency spurious. If your EAR contains other deployments like .jar or.war then you can try below :-
<jboss-deployment-structure>
<ear-subdeployments-isolated>false</ear-subdeployments-isolated>
</jboss-deployment-structure>