Wildfly not starting in debug mode with weld deployment stuck, but run mode is normal - deployment

When starting Wildfly 19 with Eclipse in run mode, it deploys and starts without problems.
When I'm starting it with debug mode, it starts then stops, still in the deployment phase.
This is how the log always ends:
2022-01-04 20:34:54,531 INFO [be2aq664] [MSC service thread 1-3:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.plugins.jar
2022-01-04 20:34:54,581 INFO [be2aq664] [MSC service thread 1-2:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.reporting.web.war
2022-01-04 20:34:54,583 INFO [be2aq664] [MSC service thread 1-8:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.services.facade.jar
2022-01-04 20:34:54,680 INFO [be2aq664] [MSC service thread 1-8:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.pvmt.web.war
2022-01-04 20:34:54,763 INFO [be2aq664] [MSC service thread 1-4:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.business.jar
2022-01-04 20:34:54,798 INFO [be2aq664] [MSC service thread 1-1:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.importer.jar
2022-01-04 20:34:54,799 INFO [be2aq664] [MSC service thread 1-4:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.remoting.web.war
2022-01-04 20:34:54,816 INFO [be2aq664] [MSC service thread 1-1:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.plugins.tmd.jar
2022-01-04 20:34:54,937 INFO [be2aq664] [MSC service thread 1-1:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.exporter.jar
2022-01-04 20:35:05,007 INFO [be2aq664] [MSC service thread 1-6:] [io.jaegertracing.internal.JaegerTracer] No shutdown hook registered: Please call close() manually on application shutdown.
2022-01-04 20:35:04,984 INFO [be2aq664] [MSC service thread 1-5:] [io.jaegertracing.internal.JaegerTracer] No shutdown hook registered: Please call close() manually on application shutdown.
2022-01-04 20:35:05,151 INFO [be2aq664] [MSC service thread 1-2:] [io.jaegertracing.internal.JaegerTracer] No shutdown hook registered: Please call close() manually on application shutdown.
2022-01-04 20:36:15,801 INFO [be2aq664] [MSC service thread 1-1:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.utils.jar
2022-01-04 20:36:40,168 INFO [be2aq664] [MSC service thread 1-6:] [org.jboss.weld.deployer] WFLYWELD0003: Processing weld deployment com.xxx.jee.services.web.war
Then the log ends as the server shuts down. Where should I be looking?


The "Skip All Breakpoints" in eclipse was disabled. As soon as I set it to skip all breakpoints it was resolved.

Related

Wildfly Http interface not listening while deploying

Context: I'm trying to deploy two artifacts appA.war and appB.war within the same server. During startup, appB makes an http request to appA, therefore appB.war depends of the other on startup so I declare that dependency in the jboss-all.xml
<jboss umlns="urn:jboss:1.0">
<jboss-deployment-dependencies xmlns="urn:jboss:deployment-dependencies:1.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:jboss:deployment-dependencies:1.0 ">
<dependency name="appA.war"/>
</jboss-deployment-dependencies>
Problem: Dependency rule works as expected. But during container restart, http requests are rejected even if I retry infinitely. Only after wildfly is completly up the requests are processed. Looks like the interface is whether not set up or disabled during deployment scanning. I've found this on my logs
2021-04-24 13:52:53,846 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.2.5.Final starting
2021-04-24 13:52:53,967 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 74) WFLYUT0014: Creating file handler for path '/opt/wildfly/develop/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2021-04-24 13:52:53,976 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0012: Started server default-server.
2021-04-24 13:52:53,977 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) Queuing requests.
2021-04-24 13:52:53,978 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting
2021-04-24 13:52:54,044 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:8081
2021-04-24 13:52:54,170 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: Jakarta Enterprise Beans subsystem suspension complete
2021-04-24 13:52:54,249 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2021-04-24 13:52:54,324 INFO [org.jboss.as.patching] (MSC service thread 1-8) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
2021-04-24 13:52:54,352 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-7) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/develop/standalone/deployments
2021-04-24 13:52:54,356 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "appA.war" (runtime-name: "holiday.war")
2021-04-24 13:52:54,359 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "appB.war" (runtime-name: "configuracion.war")
2021-04-24 13:52:54,478 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 0.0.0.0:8444
2021-04-24 13:52:54,531 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBossWS 5.4.3.Final (Apache CXF 3.3.10)
Do you know how to solve this? or any workarround?

It's expected behaviour that the server does not accept external connections until it's finished booting. You can alternative try
Disable this behaviour (I would not recommend)
start the server with no apps deployed. Then deploy one by one using the cli
Just run two different server instances with one app each
Alternatively if you know that both apps are always on the same sever, swap to in-vm calls like making ejb calls rather than http which is much less efficient way for two items in the same jvm to communicate

I believe you are looking for https://issues.redhat.com/browse/WFCORE-4291 which was introduced in WF 23

Why JBoss doesn't deploy first artefact by IDEA

My problem is that from time to time JBoss doesn't want deploy 1st artifact (ear) on the list, but after restarting or redeploying all is OK.
This problem happens not only with my machine, so maybe someone knows cause of this? It takes time to redeploy all my artifacts because IDEA sometimes don't want to deploy only one and begins to make whole project without maven.
P.S. It seems like problem with IDEA deployment tool - I got this string in console
...
Detected server admin port: 9999
Artifact int-bus-nsi-service-ear:ear: Server is not connected. Deploy is not available.
Detected server http port: 8080
Artifact int-bus-ppa-service-ear:ear: Server is not connected. Deploy is not available.
Artifact nsi-rest:war: Server is not connected. Deploy is not available.
Artifact ppa-rest:war: Server is not connected. Deploy is not available.
Artifact ppa-service-ear:ear: Server is not connected. Deploy is not available.
Artifact nsi-service-ear:ear: Server is not connected. Deploy is not available.
Connected to the target VM, address: '127.0.0.1:35251', transport: 'socket'
INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
...
Then deployment starts...
...
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "eventjournal.war" (runtime-name: "eventjournal.war")
INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "int-bus-nsi-service-ear.ear" (runtime-name: "int-bus-nsi-service-ear.ear")
INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/hcsebds]
...
After binding to data sources:
...
INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016002: Processing weld deployment int-bus-nsi-service-impl.jar
INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-7) JNDI bindings for session bean named NsiFacade in deployment unit subdeployment "int-bus-nsi-service-impl.jar" of deployment "int-bus-nsi-service-ear.ear" are as follows:
java:global/int-bus-nsi-service-ear/int-bus-nsi-service-impl/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
java:app/int-bus-nsi-service-impl/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
java:module/NsiFacade!ru.lanit.hcs.intbus.nsi.api.NsiFacade
...
ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) JBAS014613: Operation ("add") failed - address: ([("deployment" => "int-bus-nsi-service-ear.ear")]) - failure description: "JBAS014803: Duplicate resource [(\"deployment\" => \"int-bus-nsi-service-ear.ear\")]"
INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment int-bus-nsi-service-ear.ear
INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment null (runtime-name: int-bus-nsi-service-impl.jar) in 592ms
INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) started (with errors) in 71396ms - Started 4397 of 4548 services (19 services failed or missing dependencies, 103 services are passive or on-demand)
INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015877: Stopped deployment int-bus-nsi-service-ear.ear (runtime-name: int-bus-nsi-service-ear.ear) in 1250ms
INFO [org.jboss.as.server] (management-handler-thread - 1) JBAS018558: Undeployed "int-bus-nsi-service-ear.ear" (runtime-name: "int-bus-nsi-service-ear.ear")
INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016009: Stopping weld service for deployment int-bus-ppa-service-ear.ear
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment null (runtime-name: int-bus-ppa-service-impl.jar) in 126ms
Artifact int-bus-nsi-service-ear:ear: Error during artifact deployment. See server log for details.
Artifact int-bus-nsi-service-ear:ear: java.lang.Exception: JBAS014803: Duplicate resource [("deployment" => "int-bus-nsi-service-ear.ear")]
...

Openshift: war file disappears

I deployed war-file to openshift via rhc and wildfly administrative console. It works fine. But after few days (approximately one week) war disappears. The administrative tool on openshift and wildfly console works correctly. Then I redeploy war and it's ok again. Is there any time limit on openshift? Any ideas what is the problem?
UPD: log
==> wildfly/logs/server.log.2015-02-23 <==
2015-02-23 11:25:04,282 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
2015-02-23 11:25:04,282 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
2015-02-23 11:25:04,805 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
2015-02-23 11:25:05,107 INFO [org.hornetq.ra] (MSC service thread 1-6) HornetQ resource adaptor started
2015-02-23 11:25:05,109 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
2015-02-23 11:25:05,113 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
2015-02-23 11:25:05,113 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011601: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
2015-02-23 11:25:06,079 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.6.80.1:9990/management
2015-02-23 11:25:06,102 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.6.80.1:9990
2015-02-23 11:25:06,102 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 24894ms - Started 226 of 352 services (168 services are lazy, passive or on-demand)
================================
Looks like it restarts every week.

JBoss startup warning : MSC service thread ... Invalid class name

I want to get rid of the WARN messages in the following JBoss console output.
08:46:53,653 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "IodLogin.war"
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on 127.0.0.1:9999
08:46:53,670 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,124 WARN [org.jboss.as.server.deployment] (MSC service thread 1-14) JBAS015893: Encountered invalid class name 'com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection' for service type 'com.sun.faces.spi.injectionprovider'
08:46:54,596 INFO [org.jboss.weld.deployer] (MSC service thread 1-15) JBAS016002: Processing weld deployment IodLogin.war
08:46:54,815 INFO [org.jboss.weld.deployer] (MSC service thread 1-10) JBAS016005: Starting Services for CDI deployment: IodLogin.war
08:46:54,858 INFO [org.jboss.weld.Version] (MSC service thread 1-10) WELD-000900 1.1.10 (redhat)
08:46:54,901 INFO [org.jboss.as.osgi] (MSC service thread 1-7) JBAS011907: Register module: Module "deployment.IodLogin.war:main" from Service Module Loader
08:46:54,904 INFO [org.jboss.weld.deployer] (MSC service thread 1-11) JBAS016008: Starting weld service for deployment IodLogin.war
08:46:55,269 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-13) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
08:46:55,327 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Initializing Mojarra 2.1.13-jbossorg-1 20121010-0442 for context '/IodLogin'
08:46:55,933 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-13) Hibernate Validator 4.2.0.Final-redhat-2
08:46:56,281 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-13) Monitoring jndi:/default-host/IodLogin/WEB-INF/faces-config.xml for modifications
This is "just" a warning message, and I doubt it has any direct negative effect, but I try to avoid warning messages that might distract me and others from a warning that shouldn't be ignored -- the "Boy who cried 'Wolf'" parable.
I'm not using Tomcat or Jetty, but it looks like some configuration file or code is referring to classes specific to those environments. I've verified that none of the XML files refer to them directly.
I'm running JBoss EAP 6.0.1.GA. So far, this JSF 2.0 application is pretty simple -- just one page and a few classes. I'm using Eclipse, without Maven. Elsewhere on SO, I found a reference to org.jboss.shrinkwrap, but I don't see how that applies to my situation.
Update: My question is along the line of "how do I make this symptom of a non-problem go away so it doesn't mask a real problem". I'm not looking for a mistake in my code, just an improvement in the configuration.
Any suggestions about where I should look?

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.