I'm developing a webapp with EJB3, Hibernate, JSF and JBOSS, but I'm not able to start JBOSS, as it keeps on throwing this error:
16:03:55,888 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
16:03:56,130 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:03:56,187 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting
16:03:57,085 INFO [org.xnio] XNIO Version 3.0.3.GA
16:03:57,086 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
16:03:57,097 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
16:03:57,105 INFO [org.jboss.remoting] JBoss Remoting version 3.2.2.GA
16:03:57,131 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
16:03:57,135 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
16:03:57,136 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
16:03:57,148 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
16:03:57,160 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.6.final
16:03:57,165 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
16:03:57,168 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
16:03:57,172 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
16:03:57,220 INFO [org.jboss.as.connector] (MSC service thread 1-10) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
16:03:57,261 INFO [org.jboss.as.naming] (MSC service thread 1-12) JBAS011802: Starting Naming Service
16:03:57,273 INFO [org.jboss.as.mail.extension] (MSC service thread 1-10) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:03:57,286 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:03:57,419 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.1.GA
16:03:57,680 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) JBAS015012: Started FileSystemDeploymentService for directory C:\desarrollo\jboss-as-7.1.0.Final\standalone\deployments
16:03:57,682 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found AllYouCanVisit.ear in deployment directory. To trigger deployment create a file called AllYouCanVisit.ear.dodeploy
16:03:57,684 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on localhost/127.0.0.1:4447
16:03:57,685 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on /127.0.0.1:9999
16:03:57,700 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-11) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
16:03:57,836 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-9) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:03:58,086 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.mysql (missing) dependents: [service jboss.data-source.java:jboss/datasources/mysql_ds]
16:03:58,113 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 2515ms - Started 135 of 209 services (2 services failed or missing dependencies, 70 services are passive or on-demand)
My persistence.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0"
xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
<persistence-unit name="primary">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:jboss/datasources/mysql_ds</jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<!-- Properties for Hibernate -->
<property name="hibernate.show_sql" value="true" />
<property name="hibernate.hbm2ddl.auto" value="update" />
<property name="hibernate.use_sql_comments" value="true" />
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
</properties>
</persistence-unit>
</persistence>
And the datasources from the standalone.xml file in JBOSS:
<datasource jndi-name="java:jboss/datasources/mysql_ds" pool-name="mysql_ds" enabled="true" use-java-context="true" jta="true">
<connection-url>jdbc:mysql://localhost:3306/mydatabase</connection-url>
<driver>mysql</driver>
<security>
<user-name>user</user-name>
<password>password</password>
</security>
</datasource>
<drivers>
<driver name="h2" module="com.h2database.h2">
<xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
</driver>
<driver name="mysql" module="com.mysql">
<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
</driver>
</drivers>
What am I missing?
Reinstalling the server and configuring the driver and datasources again made it work.
Hope this can help anyone.
It is work for me.
https://www.youtube.com/watch?v=G-oj9XagiPo
Related
I am facing one issue when i am trying to use Management Interfaces for HTTPS , wildfly not able to deploy the wars and its stopped but when i changed to http its working fine.
you can refer the configuration which i did in standalone.xml file.
Below tag i added in the management .
<management-interfaces>
<http-interface security-realm="ManagementRealmHTTPS">
<http-upgrade enabled="true"/>
<socket-binding https="management-https"/>
</http-interface>
I added the security realm under security-realms.
<security-realm name="ManagementRealmHTTPS">
<server-identities>
<ssl>
<keystore path="keystore" relative-to="jboss.server.config.dir" keystore-password="Ivr#123"/>
</ssl>
</server-identities>
<authentication>
<properties path="https-mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
and below is the socket-binding group config.
<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
<socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/>
<socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9993}"/>
<socket-binding name="ajp" port="${jboss.ajp.port:8009}"/>
<socket-binding name="http" port="${jboss.http.port:8080}"/>
<socket-binding name="https" port="${jboss.https.port:8443}"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
<socket-binding name="txn-status-manager" port="4713"/>
<outbound-socket-binding name="mail-smtp">
<remote-destination host="localhost" port="25"/>
</outbound-socket-binding>
After doing all this config server is not coming up.
Its giving the below logs.
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /tmp/wildfly-17.0.0.Final
JAVA: /opt/jdk1.8.0_181/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
08:15:17,354 INFO [org.jboss.modules] (main) JBoss Modules version 1.9.1.Final
08:15:17,869 INFO [org.jboss.msc] (main) JBoss MSC version 1.4.7.Final
08:15:17,899 INFO [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
08:15:18,075 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) starting
08:15:19,291 INFO [org.wildfly.security] (ServerService Thread Pool -- 21) ELY00001: WildFly Elytron version 1.9.1.Final
08:15:20,013 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.
08:15:20,053 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 6) 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.
08:15:20,160 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0040: Creating http management service using secure-socket-binding (management-https)
08:15:20,190 INFO [org.xnio] (MSC service thread 1-8) XNIO version 3.7.2.Final
08:15:20,205 INFO [org.xnio.nio] (MSC service thread 1-8) XNIO NIO Implementation Version 3.7.2.Final
08:15:20,272 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 51) WFLYCLINF0001: Activating Infinispan subsystem.
08:15:20,308 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 53) WFLYRS0016: RESTEasy version 3.7.0.Final
08:15:20,319 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 52) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
08:15:20,337 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 43) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
08:15:20,339 INFO [org.jboss.as.connector] (MSC service thread 1-5) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.16.Final)
08:15:20,350 INFO [org.wildfly.extension.microprofile.metrics.smallrye] (ServerService Thread Pool -- 62) WFLYMETRICS0001: Activating Eclipse MicroProfile Metrics Subsystem
08:15:20,367 INFO [org.wildfly.extension.microprofile.config.smallrye._private] (ServerService Thread Pool -- 60) WFLYCONF0001: Activating WildFly MicroProfile Config Subsystem
08:15:20,375 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2
08:15:20,395 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 64) WFLYNAM0001: Activating Naming Subsystem
08:15:20,395 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 72) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
08:15:20,442 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 74) WFLYWS0002: Activating WebServices Extension
08:15:20,455 INFO [org.wildfly.extension.microprofile.opentracing] (ServerService Thread Pool -- 63) WFLYTRACEXT0001: Activating MicroProfile OpenTracing Subsystem
08:15:20,469 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 58) WFLYJSF0007: Activated the following JSF Implementations: [main]
08:15:20,440 INFO [org.wildfly.extension.microprofile.health.smallrye] (ServerService Thread Pool -- 61) WFLYHEALTH0001: Activating Eclipse MicroProfile Health Subsystem
08:15:20,475 INFO [org.jboss.as.security] (ServerService Thread Pool -- 70) WFLYSEC0002: Activating Security Subsystem
08:15:20,521 INFO [org.jboss.as.naming] (MSC service thread 1-7) WFLYNAM0003: Starting Naming Service
08:15:20,532 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
08:15:20,544 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 2.0.21.Final starting
08:15:20,555 INFO [org.jboss.as.security] (MSC service thread 1-7) WFLYSEC0001: Current PicketBox version=5.0.3.Final
08:15:20,619 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 5.0.12.Final
08:15:20,663 INFO [io.smallrye.metrics] (MSC service thread 1-6) Converted [2] config entries and added [4] replacements
08:15:20,840 INFO [io.smallrye.metrics] (MSC service thread 1-6) Converted [3] config entries and added [14] replacements
08:15:20,920 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 73) WFLYUT0014: Creating file handler for path '/tmp/wildfly-17.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
08:15:20,945 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.
08:15:20,949 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) 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.
08:15:21,096 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.
08:15:21,101 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
08:15:21,271 INFO [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
08:15:21,516 INFO [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none
08:15:21,526 INFO [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0493: EJB subsystem suspension complete
08:15:21,661 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
08:15:21,747 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
08:15:21,854 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBossWS 5.3.0.Final (Apache CXF 3.3.2)
08:15:21,945 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0008: Undertow HTTPS listener https suspending
08:15:21,946 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0007: Undertow HTTPS listener https stopped, was bound to 127.0.0.1:8443
08:15:21,963 INFO [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0002: Unbound mail session [java:jboss/mail/Default]
08:15:21,967 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
08:15:21,968 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0008: Undertow HTTP listener default suspending
08:15:21,971 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
08:15:21,989 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 127.0.0.1:8080
08:15:22,006 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0004: Undertow 2.0.21.Final stopping
08:15:22,008 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-7) WFLYJCA0019: Stopped Driver service with driver-name = h2
08:15:22,051 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
08:15:22,078 INFO [org.jboss.as] (MSC service thread 1-7) WFLYSRV0050: WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) stopped in 20ms
The worst part of this is that there isn't an error associated with it. I stumbled into the problem after changing one line at a time to match a Wildfly-16.0.0_Final server. The rest of the configuration seems to be working as expected, but as soon as you change to "socket-binding https="management-https"" the server breaks and refuses to come up. Does anyone know if this has been deprecated to force a move to Elytron SSL configuration?
I tried several tutorials about how to add DB connection(mainly this one) to jboss and seems a got lost.
Please correct my steps if I miss did something:
I added following description to standalone/configuration.xml:
<datasources>
<datasource module="org.postgresql" jndi-name="java:jboss/datasources/Postgres" pool-name="Postgres" enabled="true" use-java-context="true">
<connection-url>jdbc:postgresql://localhost:5432/postgres;DB_CLOSE_DELAY=-1</connection-url>
<driver>postgresDriver</driver>
<security>
<user-name>postgres</user-name>
<password>postgres</password>
</security>
</datasource>
<drivers>
<driver name="postgresDriver" module="org.postgresql">
<xa-datasource-class>org.postgresql.xa.PGXADataSource</xa-datasource-class>
</driver>
</drivers>
</datasources>
I created org/postgres/main/ directory in ...modules/system/layers/base/org/ directory
I moved there postgres-9.4.1208.jre6.jar file.
I created in this location org/postgres/main/ following module.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.postgresql">
<resources>
<resource-root path="postgresql-9.4-1208.jre6.jar" />
</resources>
<dependencies>
<module name="javax.api" />
<module name="javax.transaction.api" />
</dependencies>
</module>
And my persistence.xml looks like:
<persistence xmlns="http://java.sun.com/xml/ns/persistence"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd"
version="2.0">
<persistence-unit name="movie-unit">
<jta-data-source>java:jboss/datasources/Postgres</jta-data-source>
</persistence-unit>
</persistence>
Then I start server with deployed *.war:
/usr/local/share/jboss/bin/standalone.sh
15:36:14,370 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1
15:36:14,502 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
15:36:14,556 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting
15:36:15,188 INFO [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.7.GA-redhat-1
15:36:15,190 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
15:36:15,192 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
15:36:15,198 INFO [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 3.2.16.GA-redhat-1
15:36:15,243 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
15:36:15,267 INFO [org.jboss.as.connector.logging] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.19.Final-redhat-2)
15:36:15,327 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
15:36:15,328 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 25) JBAS014613: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "postgresDriver")
]) - failure description: "JBAS010441: Failed to load module for driver [org.postgresql]"
Please, verify my steps and help me figure out where is my mistake.
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.
I am trying to create an Java Enterprise Application using Eclipse IDE with JBoss 7.0 Server. I already had experience developing such applications but using NetBeans IDE. The main problem for me are the differences between these two IDEs. Currently, Eclipse's giving me headaches about adding JPA to EAR.
I already configured Enterprise Application (EAR) that has two containers:
-- EJB
-- WAR
Those two are configured to work together (Java Build Paths, Manifest and Deployment assembly are set for those two) so when I run EAR on the server it all works properly.
Problem:
The next thing I would like to configure is JPA. I want to add JPA container to my EAR and so I did. I've created JPA 2.1 (with EclipseLink 2.5.x and MySQL), added to EAR, I've add the changes to EJB project (right click on project->properties->deployment assembly->add jpa project).
After this point when I try to run EAR again I got HTTP Status 404 - The requested resource (/eLearningJJ-war/) is not available and my stacktrace looks like as down bellow.
Punch line
I wonder do I have to configure something extra in order to avoid this error after adding JPA to my EAR project.
If you need more details about the project please let me know,
Thank you.
Console
18:51:41,833 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA
18:51:42,224 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA
18:51:42,280 INFO [org.jboss.as] JBoss AS 7.0.1.Final "Zap" starting
18:51:43,186 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted.
18:51:43,202 INFO [org.jboss.as] creating http management service using network interface (management) port (9990)
18:51:43,202 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted.
18:51:43,217 INFO [org.jboss.as.logging] Removing bootstrap log handlers
18:51:43,233 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2)
18:51:43,280 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem.
18:51:43,452 INFO [org.jboss.as.naming] (Controller Boot Thread) Activating Naming Subsystem
18:51:43,468 INFO [org.jboss.as.osgi] (Controller Boot Thread) Activating OSGi Subsystem
18:51:43,468 INFO [org.jboss.as.naming] (MSC service thread 1-6) Starting Naming Service
18:51:43,530 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem
18:51:43,546 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 3.2.0.Beta2
18:51:43,561 INFO [org.xnio] (MSC service thread 1-3) XNIO Version 3.0.0.Beta3
18:51:43,593 INFO [org.xnio.nio] (MSC service thread 1-3) XNIO NIO Implementation Version 3.0.0.Beta3
18:51:43,999 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-2) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jdk1.8.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\MinGW\bin;C:\msys\1.0\bin;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;.
18:51:43,999 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem
18:51:44,452 INFO [org.jboss.as.remoting] (MSC service thread 1-4) Listening on /127.0.0.1:9999
18:51:44,585 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-6) Starting remote JMX connector
18:51:44,675 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
18:51:44,847 INFO [org.jboss.as.connector] (MSC service thread 1-6) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final)
18:51:44,907 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) Bound data source [java:jboss/datasources/ExampleDS]
18:51:44,927 INFO [org.jboss.as.deployment] (MSC service thread 1-1) Started FileSystemDeploymentService for directory C:\Users\Milan\jboss-as-7.0.1.Final\standalone\deployments
18:51:44,975 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.1.Final "Zap" started in 3626ms - Started 93 of 148 services (55 services are passive or on-demand)
18:51:45,022 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found eLearningJJ-ear.ear in deployment directory. To trigger deployment create a file called eLearningJJ-ear.ear.dodeploy
18:51:45,100 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-ear.ear"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "eLearningJJ-war.war"
18:51:45,334 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "eLearningJJ-ejb.jar"
18:51:45,897 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) Class Path entry in "/C:/Users/Milan/jboss-as-7.0.1.Final/standalone/deployments/eLearningJJ-ear.ear/lib/testjpa.jar" does not point to a valid jar for a Class-Path reference.
18:51:46,101 INFO [org.jboss.jpa] (MSC service thread 1-3) read persistence.xml for testjpa
18:51:46,458 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Tomcat6InjectionProvider:org.apache.catalina.util.DefaultAnnotationProcessor" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,459 WARN [org.jboss.as.server.deployment.service-loader] (MSC service thread 1-4) Encountered invalid class name "com.sun.faces.vendor.Jetty6InjectionProvider:org.mortbay.jetty.plus.annotation.InjectionCollection" for service type "com.sun.faces.spi.injectionprovider"
18:51:46,526 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ear.ear
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
18:51:46,528 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added org.hibernate dependency to application deployment
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-4) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-ejb.jar
18:51:46,533 INFO [org.jboss.as.jpa] (MSC service thread 1-7) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to eLearningJJ-war.war
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserTest in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTest
java:app/eLearningJJ-ejb/UserTest!com.test.UserTest
java:module/UserTest!com.test.UserTest
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:app/eLearningJJ-ejb/UserTest!com.test.UserTestLocal
java:module/UserTest!com.test.UserTestLocal
18:51:46,704 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-8) JNDI bindings for session bean named UserStateless in deployment unit subdeployment "eLearningJJ-ejb.jar" of deployment "eLearningJJ-ear.ear" are as follows:
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:module/UserStateless!com.elearningjj.beans.UserStatelessLocal
java:global/eLearningJJ-ear/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:app/eLearningJJ-ejb/UserStateless!com.elearningjj.beans.UserStateless
java:module/UserStateless!com.elearningjj.beans.UserStateless
18:51:48,392 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,399 INFO [org.apache.catalina.core.StandardContext] (MSC service thread 1-2) The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
18:51:48,712 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.0.4 (FCS b09-jbossorg-4) for context '/eLearningJJ-war'
18:51:53,821 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /eLearningJJ-war
18:51:54,055 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "eLearningJJ-ear.ear" was rolled back with failure message {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}
18:51:54,180 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Stopped deployment eLearningJJ-ejb.jar in 131ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-war.war in 140ms
18:51:54,195 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Stopped deployment eLearningJJ-ear.ear in 144ms
18:51:54,195 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"eLearningJJ-ear.ear#testjpa\" missing [ jboss.data-source.java:/ ]"]}}}
Solution
The main problem was improperly configured JPA's persistance.xml file. In my case, concrete problem was related to the jta-data-source which wasn't properly configured.
The solution for this is checking the JBoss Administration Console for more details about Datasource Configurations, Registered Datasources, etc. Regarding to this source of information, my persistance.xml file looks like down bellow:
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
<persistence-unit name="eLearningJJ-jpa">
<provider>org.hibernate.ejb.HibernatePersistence</provider>
<jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
<properties>
<property name="hibernate.dialect"
value="org.hibernate.dialect.HSQLDialect"/>
<property name="hibernate.hbm2ddl.auto" value="create-drop"/>
</properties>
</persistence-unit>
</persistence>
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.