Deploy failed - missing depedencies When i am using annotations - jboss

i am not so familiar with ejb. I had hard time to set up realm authorization at wildfly, (13) all the time i had same error:
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
After this i have removed #Singleton Annotation from "ProgrammaticScheduler" and with out it my realm authentication works well. But than my scheduler doesnt work at all. When i remove lane with
exampleApplicationDomain
Scheduler works, realm doesnt. Where is the point? This two componenst dont have any common classes.. (well.. i dont know about any). Any one have some ideas? I have seen many familiar problems here but almost all of them were about missing or wrong line in standalone.xml.
Ps. I had another class with #stateless annotation and this class was in error too, but i didnt need it and jsut removed it. Full error log, standalone, jboss-web.xml below. Hope some will find solution
standalone.xml
<security-domains>
<security-domain name="ApplicationDomain" default-realm="ApplicationRealm" permission-mapper="default-permission-mapper">
<realm name="ApplicationRealm" role-decoder="groups-to-roles"/>
<realm name="local"/>
</security-domain>
<security-domain name="ManagementDomain" default-realm="ManagementRealm" permission-mapper="default-permission-mapper">
<realm name="ManagementRealm" role-decoder="groups-to-roles"/>
<realm name="local" role-mapper="super-user-mapper"/>
</security-domain>
<security-domain name="jdbcdomain" default-realm="jdbcRealm">
<realm name="jdbcRealm"/>
</security-domain>
<security-domain name="exampleDbSD" default-realm="exampleDbRealm" permission-mapper="default-permission-mapper">
<realm name="exampleDbRealm" role-decoder="groups-to-roles"/>
</security-domain>
</security-domains>
ProgrammaticScheduler
#Singleton
public class ProgrammaticScheduler {
#Schedule(hour="20", minute="33")
public void removeExpiredSearches() throws IOException{
System.out.println("Kick off!");
}
#Timeout()
public void onTimeout(Timer timer){
}
}
Error log
20:33:34,908 INFO [org.jboss.modules] (main) JBoss Modules version 1.8.5.Final
20:33:36,349 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.2.Final
20:33:36,373 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.2.Final
20:33:36,662 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 13.0.0.Final (WildFly Core 5.0.0.Final) starting
20:33:40,940 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.
20:33:41,000 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 17) 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.
20:33:41,004 INFO [org.wildfly.security] (ServerService Thread Pool -- 7) ELY00001: WildFly Elytron version 1.3.3.Final
20:33:41,220 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found RaportGeneratorEE-0.0.1-SNAPSHOT.war in deployment directory. To trigger deployment create a file called RaportGeneratorEE-0.0.1-SNAPSHOT.war.dodeploy
20:33:41,324 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
20:33:41,409 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.6.3.Final
20:33:41,421 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.6.3.Final
20:33:41,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 60) WFLYSEC0002: Activating Security Subsystem
20:33:41,683 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension
20:33:41,666 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) 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.
20:33:41,677 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 47) WFLYRS0016: RESTEasy version 3.5.1.Final
20:33:41,682 INFO [org.jboss.as.security] (MSC service thread 1-5) WFLYSEC0001: Current PicketBox version=5.0.2.Final
20:33:41,705 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 52) WFLYJSF0007: Activated the following JSF Implementations: [main]
20:33:41,718 INFO [org.jboss.as.ee] (ServerService Thread Pool -- 41) WFLYEE0119: The system property 'ee8.preview.mode' is NOT set to 'true'. For provided EE 8 APIs where the EE 8 version of the API differs from what is supported in EE 7, the EE 7 variant of the API will be used. Support for this setting will be removed once all EE 8 APIs are provided and certified.
20:33:41,737 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 45) WFLYCLINF0001: Activating Infinispan subsystem.
20:33:41,743 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem
20:33:41,818 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0003: Undertow 2.0.9.Final starting
20:33:41,863 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
20:33:41,885 INFO [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.9.Final)
20:33:41,932 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
20:33:42,046 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
20:33:42,056 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
20:33:42,419 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path 'C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
20:33:42,886 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 46) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
20:33:42,904 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) 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.
20:33:42,913 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.
20:33:43,056 INFO [org.jboss.remoting] (MSC service thread 1-6) JBoss Remoting version 5.0.7.Final
20:33:43,060 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0012: Started server default-server.
20:33:43,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0018: Host default-host starting
20:33:43,112 INFO [org.jboss.as.patching] (MSC service thread 1-5) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
20:33:43,226 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
20:33:43,236 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\Wiki\Downloads\wildfly-13.0.0.Final\wildfly-13.0.0.Final\standalone\deployments
20:33:43,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "mysql" (runtime-name: "mysql-connector-java-5.1.44-bin.jar")
20:33:43,271 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name: "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:43,301 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
20:33:43,345 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0493: EJB subsystem suspension complete
20:33:44,142 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
20:33:44,619 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
20:33:44,801 INFO [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.2.1.Final (Apache CXF 3.2.4.jbossorg-1)
20:33:45,530 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:45,536 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:45,705 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:45,706 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = mysql-connector-java-5.1.44-bin.jar_com.mysql.jdbc.Driver_5_1
20:33:45,736 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:/MysqlXADS]
20:33:45,745 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:/examplePostgresDS]
20:33:47,033 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Gaina' 9.2.4.Final
20:33:48,039 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 66) WFLYCLINF0002: Started client-mappings cache from ejb container
20:33:52,002 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/serializer-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xercesImpl.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry xml-apis.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:52,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry serializer.jar in /C:/Users/Wiki/Downloads/wildfly-13.0.0.Final/wildfly-13.0.0.Final/standalone/deployments/RaportGeneratorEE-0.0.1-SNAPSHOT.war/WEB-INF/lib/xalan-2.7.2.jar does not point to a valid jar for a Class-Path reference.
20:33:53,000 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0003: Processing weld deployment RaportGeneratorEE-0.0.1-SNAPSHOT.war
20:33:53,923 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-3) HV000001: Hibernate Validator 5.3.6.Final
20:33:54,036 INFO [org.jboss.as.ejb3.deployment] (MSC service thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'ProgrammaticScheduler' in deployment unit 'deployment "RaportGeneratorEE-0.0.1-SNAPSHOT.war"' are as follows:
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:module/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
ejb:RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler!czesak.raportgenerator.service.ProgrammaticScheduler
java:global/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:app/RaportGeneratorEE-0.0.1-SNAPSHOT/ProgrammaticScheduler
java:module/ProgrammaticScheduler
20:33:54,485 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:33:54,490 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.fabric.jdbc.FabricMySQLDriver (version 5.1)
20:33:54,500 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0005: Deploying non-JDBC-compliant driver class com.mysql.cj.jdbc.Driver (version 8.0)
20:33:54,539 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900: 3.0.4 (Final)
20:33:54,721 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.fabric.jdbc.FabricMySQLDriver_5_1
20:33:54,722 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.jdbc.Driver_5_1
20:33:54,724 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = RaportGeneratorEE-0.0.1-SNAPSHOT.war_com.mysql.cj.jdbc.Driver_8_0
20:33:55,037 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "RaportGeneratorEE-0.0.1-SNAPSHOT.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.exampleApplicationDomain"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"RaportGeneratorEE-0.0.1-SNAPSHOT.war\".component.ProgrammaticScheduler.CREATE is missing [jboss.security.security-domain.exampleApplicationDomain]"]
}
20:33:55,057 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mysql" (runtime-name : "mysql-connector-java-5.1.44-bin.jar")
20:33:55,058 INFO [org.jboss.as.server] (ServerService Thread Pool -- 39) WFLYSRV0010: Deployed "RaportGeneratorEE-0.0.1-SNAPSHOT.war" (runtime-name : "RaportGeneratorEE-0.0.1-SNAPSHOT.war")
20:33:55,064 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service jboss.security.security-domain.exampleApplicationDomain (missing) dependents: [service jboss.deployment.unit."RaportGeneratorEE-0.0.1-SNAPSHOT.war".component.ProgrammaticScheduler.CREATE]
WFLYCTL0448: 225 additional services are down due to their dependencies being missing or failed

There is need to add aplication-security-domain (using security-domain) in ejb3 services:
subsystem=ejb3/application-security-domain=exampleApplicationDomain:add(security-domain=exampleDbSD)

Related

Deployed on WildFly but still getting 404

I am referring to the following helloworld example
My application is successfully deployed on my eclipse using WildFly 9.x as shown in the screenshot and the console log below:
Here's the eclipse console log details :
14:08:16,447 INFO [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final
14:08:17,156 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
14:08:17,293 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0049: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) starting
14:08:19,873 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 19) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:08:19,890 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.
14:08:19,908 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found JAX-RS_examples.war in deployment directory. To trigger deployment create a file called JAX-RS_examples.war.dodeploy
14:08:19,953 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:08:19,993 INFO [org.xnio] (MSC service thread 1-3) XNIO version 3.3.1.Final
14:08:20,007 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.3.1.Final
14:08:20,075 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.9.Final
14:08:20,106 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,213 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
14:08:20,183 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:08:20,179 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
14:08:20,110 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.2.9.Final starting
14:08:20,164 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.
14:08:20,164 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
14:08:20,136 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
14:08:20,106 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
14:08:20,377 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:08:20,684 INFO [org.jboss.as.connector] (MSC service thread 1-3) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.5.Final)
14:08:20,975 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
14:08:20,985 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
14:08:21,016 INFO [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=4.9.2.Final
14:08:21,158 INFO [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:08:21,194 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path D:\Users\dan\wildfly-9.0.2.Final/welcome-content
14:08:21,246 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0012: Started server default-server.
14:08:21,264 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
14:08:21,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0006: Undertow HTTP listener default listening on localhost/127.0.0.1:8080
14:08:22,413 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory D:\Users\dan\wildfly-9.0.2.Final\standalone\deployments
14:08:22,475 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "JAX-RS_examples.war" (runtime-name: "JAX-RS_examples.war")
14:08:22,885 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final
14:08:23,423 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:08:25,131 INFO [org.jboss.resteasy.spi.ResteasyDeployment] (ServerService Thread Pool -- 61) Deploying javax.ws.rs.core.Application: class com.thejavageek.jaxrs.ExampleApplication
14:08:25,203 INFO [org.hibernate.validator.internal.util.Version] (ServerService Thread Pool -- 61) HV000001: Hibernate Validator 5.1.3.Final
14:08:25,283 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0021: Registered web context: /JAX-RS_examples
14:08:25,463 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "JAX-RS_examples.war" (runtime-name : "JAX-RS_examples.war")
14:08:25,939 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:08:25,941 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:08:25,942 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started in 9899ms - Started 272 of 453 services (221 services are lazy, passive or on-demand)
I am trying to access the application like this :
http://127.0.0.1:9990/JAX-RS_examples/rest/HelloWorld/sayHello
And getting 404 not found.
Came across similar thread but can't figure out :
WildFly running, project deployed, but 404
someone already told you.
You call your REST service with the port 9990.
But, this port is form the admin console.
by default, the correct port should be 8080. So, just call:
http://127.0.0.1:8080/JAX-RS_examples/rest/HelloWorld/sayHello
The runtime name needs to have a .war estension.

JBOSS EAP7 and eclipse, HTTP 403 Forbidden::The website declined to show this webpage

I am new to JBOSS EAP and trying to run a basic web application on this.Below is the process I did:
Downloaded and installed JBOSS EAP 7
Downloaded Eclipse mars.
Downloaded jdk 1.8
JAVA_HOME set in the env variable and java path variable set.
Open eclipse
Configuration JBOSS EAP server in eclipse
a. Define a new Server
b. Select Red Hat JBoss Enterprise Application Platform 7.x
Server's host name = localhost
Server Name = Red Hat JBoss EAP 7.x
c.Clicked on next button and finish.
7.Right click and started the server ( server started successfully).
I am able to open (http://localhost:8080/), without any issue.
Creating Web Application in eclipse
a. Open New Project => Dynamic web Project
b. Project name given : HelloApp
c. I didn't select checkbox for "Generate web.xml deployment descriptor".
d. Create new HTML file (Index.html), inside HelloApp/WebContent folder
e. Added Hello in the body part of the HTML.
Running HelloApp Project.
a. Right Click and select run as sever
b. Select Red Hat JBoss EAP 7.x
c. Adding HelloApp to configured tab.
d. Finish button
Below is the jboss logs:
13:29:11,462 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final-redhat-1
13:29:11,887 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final-redhat-1
13:29:12,019 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) starting
13:29:14,178 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found MyWebApp.war in deployment directory. To trigger deployment create a file called MyWebApp.war.dodeploy
13:29:14,246 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
13:29:14,326 INFO [org.xnio] (MSC service thread 1-1) XNIO version 3.3.6.Final-redhat-1
13:29:14,343 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.6.Final-redhat-1
13:29:14,410 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
13:29:14,419 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
13:29:14,434 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
13:29:14,434 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
13:29:14,438 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.
13:29:14,446 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
13:29:14,456 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
13:29:14,504 INFO [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=4.9.6.Final-redhat-1
13:29:14,551 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:29:14,687 INFO [org.jboss.as.connector] (MSC service thread 1-7) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.3.Final-redhat-1)
13:29:14,690 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,694 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.21.Final-redhat-1 starting
13:29:14,710 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-5) WFLYJCA0018: Started Driver service with driver-name = h2
13:29:14,779 INFO [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service
13:29:14,783 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
13:29:15,030 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path 'C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
13:29:15,181 INFO [org.jboss.as.ejb3] (MSC service thread 1-6) 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.
13:29:15,184 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) 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.
13:29:15,489 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
13:29:15,498 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
13:29:15,500 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 4.0.18.Final-redhat-1
13:29:15,588 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
13:29:15,729 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\AVIKUMAR\JBOSS-EAP-7.0.0\standalone\deployments
13:29:15,861 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "MyWebApp.war" (runtime-name: "MyWebApp.war")
13:29:16,247 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
13:29:16,250 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-4) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.2.Final-redhat-1
13:29:16,463 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.3.SP1-redhat-1 (Apache CXF 3.1.4.redhat-1)
13:29:17,751 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 58) WFLYUT0021: Registered web context: /MyWebApp
13:29:17,798 INFO [org.jboss.as.server] (ServerService Thread Pool -- 34) WFLYSRV0010: Deployed "MyWebApp.war" (runtime-name : "MyWebApp.war")
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
13:29:18,056 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
13:29:18,057 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.0.0.GA (WildFly Core 2.1.2.Final-redhat-1) started in 7216ms - Started 336 of 627 services (382 services are lazy, passive or on-demand)
19:36:12,928 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found HelloApp.war in deployment directory. To trigger deployment create a file called HelloApp.war.dodeploy
19:36:12,953 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "HelloApp.war" (runtime-name: "HelloApp.war")
19:36:13,048 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 64) WFLYUT0021: Registered web context: /HelloApp
19:36:13,134 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "HelloApp.war" (runtime-name : "HelloApp.war")
In the eclipse browser getting below error
The website declined to show this webpage.
More information
This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage.
See the quickstart example below follow step by step process:
http://www.jboss.org/quickstarts/eap/helloworld/

SIP Servlet not starting in JBOSS 7.2 from Eclipse

I currently work on a project based on Mobicents SIP Servlets and JBoss 7.2. I created a new Dynamic Web Project in Eclipse with the template the Mobicents Eclipse Plugin gives me, then mavenize it. Then I created a JBoss Server in Eclipse pointing to my Mobicents Jboss installation. When I deploy my servlet now, I see the exploded war in the Jboss installation and the logs say that it is deployed, but I do not see that it logged anything.
My very basic servlet:
package org.example.servlet.sip;
import javax.servlet.ServletException;
import javax.servlet.sip.SipServlet;
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
#SuppressWarnings("serial")
public class MySipServlet extends SipServlet {
private static Log logger = LogFactory.getLog(MySipServlet.class);
#Override
public void init() throws ServletException {
logger.info("the HelloSipWorld servlet has been started");
}
}
Log:
12:54:12,102 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
12:54:12,315 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA
12:54:12,378 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss AS 7.2.0.Final "Janus" starting
12:54:13,392 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found test-as.war in deployment directory. To trigger deployment create a file called test-as.war.dodeploy
12:54:13,426 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.7.GA
12:54:13,430 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
12:54:13,435 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.7.GA
12:54:13,453 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.14.GA
12:54:13,533 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
12:54:13,546 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
12:54:13,570 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
12:54:13,575 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
12:54:13,619 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
12:54:13,635 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.15.Final
12:54:13,677 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.15.Final)
12:54:13,686 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
12:54:13,691 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:54:13,777 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:54:13,958 INFO [org.jboss.ws.common.management] (MSC service thread 1-6) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final
12:54:14,080 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080
12:54:14,093 INFO [org.apache.coyote.http11] (MSC service thread 1-6) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080
12:54:14,357 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:54:14,467 INFO [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on 127.0.0.1:4447
12:54:14,469 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999
12:54:14,472 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /home/jck/Desktop/ngncc/as/mobicents/mss-2.1.547-jboss-as-7.2.0.Final/standalone/deployments
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "media-jsr309-servlet.war" (runtime-name: "media-jsr309-servlet.war")
12:54:14,508 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "test-as.war" (runtime-name: "test-as.war")
12:54:14,509 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "click2call.war" (runtime-name: "click2call.war")
12:54:14,507 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jolokia.war" (runtime-name: "jolokia.war")
12:54:14,525 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "sip-servlets-management.war" (runtime-name: "sip-servlets-management.war")
12:54:14,528 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "websockets-sip-servlet.war" (runtime-name: "websockets-sip-servlet.war")
12:54:15,139 INFO [org.jboss.web] (ServerService Thread Pool -- 51) JBAS018210: Register web context: /test-as
12:54:15,140 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /websockets-sip-servlet
12:54:15,143 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /jolokia
12:54:15,145 INFO [org.jboss.web] (ServerService Thread Pool -- 52) JBAS018210: Register web context: /sip-servlets-management
12:54:15,373 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jolokia]] (ServerService Thread Pool -- 50) jolokia-agent: No access restrictor found at classpath:/jolokia-access.xml, access to all MBeans is allowed
12:54:15,754 INFO [org.jboss.web] (ServerService Thread Pool -- 50) JBAS018210: Register web context: /media-jsr309-servlet
12:54:16,014 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "sip-servlets-management.war" (runtime-name : "sip-servlets-management.war")
12:54:16,015 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "test-as.war" (runtime-name : "test-as.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "jolokia.war" (runtime-name : "jolokia.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "websockets-sip-servlet.war" (runtime-name : "websockets-sip-servlet.war")
12:54:16,016 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "click2call.war" (runtime-name : "click2call.war")
12:54:16,017 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "media-jsr309-servlet.war" (runtime-name : "media-jsr309-servlet.war")
12:54:16,018 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
12:54:16,118 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
12:54:16,119 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
12:54:16,119 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.0.Final "Janus" started (with errors) in 4413ms - Started 368 of 443 services (3 services failed or missing dependencies, 71 services are passive or on-demand)
Any hints on what I am doing wrong is highly appreciated. I use SIP Servlets 2.1.547 on JBoss 7.2.
Make sure you select standalone-sip.xml as profile in the configuration. SIP Servlets Container uses a specific configuration which is not the default I believe when you start through Eclipse
Annotate your servlet with #SipServlet:
#SuppressWarnings("serial")
#javax.servlet.sip.annotation.SipServlet
public class MySipServlet extends SipServlet {
Add sip dependencies like:
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>sip-api</artifactId>
<version>1.0</version>
</dependency>
Make sure maven dependencies are present in WEB-INF/lib. If not, go to
Your Project> Properties > Deployment Assembly > Click Add.. and select "Build Path entries", then select "Maven dependencies".
Also you have error in your log, so you are definitely missing some dependencies:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.security.security-domain.sip-servlets (missing) dependents: [service jboss.web.deployment.default-host./click2call.realm]
Did you add the following category in the \server\default\conf\jboss-log4j.xml
<category name="org.example.servlet">
<priority value="INFO"/></category>
If you do not intend to test click2call use-case why not remove the war from your jboss's deploy folder.

404 error for servlets in Eclipse/JBoss Dynamic Web Project

I have setup a dynamic web project using Servlets and HTML/CSS/JS. While deploying the project, any request sent to the servlets via AJAX, leads to a 404 error every time starting from today.
Also adding any new servlets has the same effect - 404.
However, the HTML pages are rendered fine with working JS and CSS. (No 404).
Here is the console output on running the project :
20:41:17,765 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
20:41:18,304 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
20:41:18,399 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
20:41:20,334 INFO [org.xnio] XNIO Version 3.0.3.GA
20:41:20,335 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
20:41:20,379 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
20:41:20,418 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
20:41:20,456 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
20:41:20,464 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
20:41:20,527 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
20:41:20,611 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
20:41:20,614 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
20:41:20,663 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
20:41:20,672 INFO [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
20:41:20,716 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
20:41:20,747 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
20:41:20,945 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
20:41:21,024 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
20:41:21,120 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
20:41:21,143 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
20:41:21,312 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
20:41:21,695 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
20:41:22,716 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
20:41:22,720 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/mydb]
20:41:22,904 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:9999
20:41:22,905 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on localhost/127.0.0.1:4447
20:41:22,921 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /usr/local/share/jboss/standalone/deployments
20:41:22,935 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found VodaBillEAR.ear in deployment directory. To trigger deployment create a file called VodaBillEAR.ear.dodeploy
20:41:22,936 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found Vodafone BillingEAR.ear in deployment directory. To trigger deployment create a file called Vodafone BillingEAR.ear.dodeploy
20:41:23,285 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.oracle (missing) dependents: [service jboss.data-source.java:/OracleDS]
20:41:23,329 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "VodaBillEAR.ear"
20:41:23,369 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "VodaBill.war"
20:41:24,051 INFO [org.jboss.web] (MSC service thread 1-4) JBAS018210: Registering web context: /VodaBill
20:41:24,054 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015951: Admin console listening on http://127.0.0.1:9990
20:41:24,055 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 7192ms - Started 191 of 274 services (2 services failed or missing dependencies, 78 services are passive or on-demand)
20:41:24,237 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "VodaBillEAR.ear"
Seems like there was some problem with my build path - two images included in it (PNG files). Removing them fixed the error.

Error deploying WAR file to Jboss EAP 6.0, which works under JBOSS AS 7.1

We are working on our new system which is built using Jboss, Spring and Hibernate and at the moment we're in the progress of migrating from AS 7.1 to EAP 6.0.
For reasons unknown to us the deployment fails when deploying to the EAP 6.0 server, but works perfectly fine under AS 7.1(both on our local machines and our local test-server).
In short, we get the following error:
"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},
"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: ]"]
Furthermore, we have the console log, see below for further information. We've found https://issues.jboss.org/browse/AS7-5222, and as far as we understand there is a fix included which gives more detailed error information, alas we can't update/upgrade at the moment.
So my humble question is, does anyone have an idea on how to solve this issue?
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/EAP-6.0.0.GA/jboss-eap-6.0
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:30:54,539 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1
10:30:54,896 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1
10:30:55,002 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) starting
10:30:56,296 INFO [org.xnio] XNIO Version 3.0.4.GA-redhat-1
10:30:56,301 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:30:56,312 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1
10:30:56,322 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1
10:30:56,362 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:30:56,369 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
10:30:56,393 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
10:30:56,506 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:30:56,510 INFO [org.jboss.as.connector.logging] (MSC service thread 1-3) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
10:30:56,559 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
10:30:56,568 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.9.Final-redhat-1
10:30:56,598 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
10:30:56,602 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
10:30:56,622 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
10:30:56,692 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
10:30:56,719 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:30:56,920 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1
10:30:57,138 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
10:30:57,167 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-4) Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080
10:30:57,413 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:30:57,632 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /opt/EAP-6.0.0.GA/jboss-eap-6.0/standalone/deployments
10:30:57,644 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:4447
10:30:57,645 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on 0.0.0.0:9999
10:30:57,763 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
10:30:57,763 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started in 3619ms - Started 133 of 212 services (78 services are passive or on-demand)
10:33:36,236 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "Web.war"
10:33:41,301 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
10:33:41,306 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
10:33:41,404 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011907: Register module: Module "deployment.Web.war:main" from Service Module Loader
10:33:51,310 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Error listenerStart
10:33:51,311 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) Context [/Web] startup failed due to previous errors
10:33:51,335 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.web.deployment.default-host./Web: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_06]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_06]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_06]
10:33:51,542 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "Web.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: <one or more transitive dependencies>]"]}
10:33:51,565 INFO [org.jboss.as.osgi] (MSC service thread 1-1) JBAS011908: Unregister module: Module "deployment.Web.war:main" from Service Module Loader
10:33:51,675 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment Web.war in 132ms
Updated: Here's some more log. Note that this is running OpenJDK 1.7, instead of the regular version. We've tried both of them but the issue remains.
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/EAP-6.0.0.GA/jboss-eap-6.0
JAVA: java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
14:12:59,719 INFO [org.jboss.modules] JBoss Modules version 1.1.2.GA-redhat-1
14:13:00,028 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA-redhat-1
14:13:00,111 INFO [org.jboss.as] JBAS015899: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) starting
14:13:01,469 INFO [org.xnio] XNIO Version 3.0.4.GA-redhat-1
14:13:01,488 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
14:13:01,493 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.4.GA-redhat-1
14:13:01,505 INFO [org.jboss.remoting] JBoss Remoting version 3.2.8.GA-redhat-1
14:13:01,540 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
14:13:01,546 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
14:13:01,560 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
14:13:01,674 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
14:13:01,699 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.11.Final-redhat-1)
14:13:01,715 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:13:01,729 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
14:13:01,735 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.9.Final-redhat-1
14:13:01,757 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011906: Activating OSGi Subsystem
14:13:01,838 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
14:13:01,848 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:13:01,898 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:13:02,153 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.4.GA-redhat-1
14:13:02,383 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:13:02,530 WARN [com.arjuna.ats.arjuna] (Transaction Expired Entry Monitor) ARJUNA012210: Unable to use InetAddress.getLocalHost() to resolve address.
14:13:02,754 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:13:02,895 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 0.0.0.0:9999
14:13:02,897 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on 0.0.0.0:4447
14:13:02,908 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /opt/EAP-6.0.0.GA/jboss-eap-6.0/standalone/deployments
14:13:03,018 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://0.0.0.0:9990
14:13:03,019 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) started in 3697ms - Started 133 of 212 services (78 services are passive or on-demand)
14:13:50,537 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "Web.war"
14:13:55,458 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
14:13:55,462 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010404: Deploying non-JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
14:13:55,598 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011907: Register module: Module "deployment.Web.war:main" from Service Module Loader
14:14:01,556 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart
14:14:01,556 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/Web] startup failed due to previous errors
14:14:01,575 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment.default-host./Web: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA-redhat-1.jar:1.0.2.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05-icedtea]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05-icedtea]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05-icedtea]
14:14:01,782 INFO [org.jboss.as.server] (HttpManagementService-threads - 1) JBAS015870: Deploy of deployment "Web.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./Web" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./Web: JBAS018040: Failed to start context"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.deployment.unit.\"Web.war\".jboss.security.jacc Missing[JBAS014861: <one or more transitive dependencies>]"]}
14:14:01,794 INFO [org.jboss.as.osgi] (MSC service thread 1-3) JBAS011908: Unregister module: Module "deployment.Web.war:main" from Service Module Loader
14:14:01,934 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment Web.war in 152ms
14:15:39,916 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Container org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/] has not been started
14:15:39,935 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Pausing Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:15:39,935 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Stopping Coyote HTTP/1.1 on http-/0.0.0.0:8080
14:15:39,945 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers
14:15:39,950 INFO [com.arjuna.ats.jbossatx] ARJUNA032018: Destroying TransactionManagerService
14:15:39,951 INFO [com.arjuna.ats.jbossatx] ARJUNA032014: Stopping transaction recovery manager
14:15:39,965 INFO [org.jboss.as] JBAS015950: JBoss EAP 6.0.0.GA (AS 7.1.2.Final-redhat-1) stopped in 6ms
Ensure that you are not using Spring Framework versions between 2.5 and 3.0.1. These are known to be incompatible with all versions of JBoss from 5.0 or so and newer;
Use below command and let me know the the status.
standalone.sh -Dorg.jboss.as.logging.per-deployment=false
We faced similar issue, with JBoss AS 7.2.0 final and Spring 3.2.8. In our case we missed the setting of spring's active profile to point to Jboss7. Once we set this the context was resolved, deployment was successful.
set "JAVA_OPTS=%JAVA_OPTS% -Dspring.profiles.active=jboss7
Hope this helps.