Wildfly : application deployed but not running - eclipse

I'm trying to deploy an .ear application to Wildfly 10.1 final. The .ear has 2 nested .war files. There's no "jboss-web.xml" file in the .war files.
Here's the application.xml file :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE application PUBLIC
"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
"http://java.sun.com/dtd/application_1_3.dtd">
<application>
<display-name>myApp-ear</display-name>
<description>myApp</description>
<module>
<web>
<web-uri>myApp-rest</web-uri>
<context-root>/myApp-rest</context-root>
</web>
</module>
<module>
<web>
<web-uri>myApp-webapp</web-uri>
<context-root>/myApp-webapp</context-root>
</web>
</module>
</application>
After deploying, I have the following log :
INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0004: Found myApp.ear in deployment directory. To trigger deployment create a file called myApp.ear.dodeploy
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "myApp.ear" (runtime-name: "myApp.ear")
WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in /C:/Dev/Wildfly/wildfly-10.1.0.Final/standalone/deployments/myApp.ear/liquibase-core-3.3.0.jar does not point to a valid jar for a Class-Path reference.
(...)
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-rest")
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-webapp")
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "myApp.ear" (runtime-name : "myApp.ear")
And that's all, no "register" in the logs or something like that.
So, whenever I try to access "localhost:8080/myApp-webapp" I have a 404 error.
The application was previously deployed on Weblogic 11 (with the same configuration) and it worked fine.
Any clue ?

Based on the following log messages it looks like the contents of your EAR are missing the appropriate file extensions
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-rest")
INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0207: Starting subdeployment (runtime-name: "myApp-webapp")
INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "myApp.ear" (runtime-name : "myApp.ear")
Specifically note the myApp-rest and myApp-webapp. Those should both have a .war extension even if this is an exploded deployment. (Note the myApp-rest may have a .jar extension if it's just an EJB module.)

Related

Problems with Jboss 6.1+ deployment

I think I have some related problems with JBOSS. If I start server with some project in the deploy folder, the server doesn't start and gives me the error:
'Server JBoss EAP 6.1+ Runtime Server failed to start'.
Furthermore if I add an ear in the deploy folder I get the following warning:
'JBAS015000: Cannot delete deployment progress marker file'.
Sometimes adding the ear's in the folder I get the errors:
JBAS018559: Deployed "my-ear-7.5.13.ear" (runtime-name : "my-ear-7.5.13.ear")
17:11:18,463 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2)
JBAS015877: Stopped deployment null (runtime-name: my-ejb.jar) in 32ms
17:11:18,511 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3)
JBAS015877: Stopped deployment my-ear-7.5.13.ear (runtime-name: my-ear-7.5.13.ear) in 90ms
17:11:18,573 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "my-ear-7.5.13.ear"

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.

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")]
...

Jboss server not starting

i am installatng the JBoss server and starting it as part of jbpm installation.
when i start the server with ant start.demo syntax, i am getting the below error in log file,
13:13:55,082 INFO [org.jboss.jaxr] (MSC service thread 1-2) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
13:13:55,082 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
13:13:55,565 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 48) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:13:57,250 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.2.GA
13:13:58,014 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory D:\New folder\jbpm-6.0.0.Final-installer-full\jbpm-installer\jboss-as-7.1.1.Final\standalone\deployments
13:13:58,014 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment dashboard-builder.war
13:13:58,046 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment jbpm-console.war
13:14:03,256 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.network.public: org.jboss.msc.service.StartException in service jboss.network.public: JBAS015810: failed to resolve interface public
13:14:03,287 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "jbpm-console.war"
13:14:03,287 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "dashboard-builder.war"
13:14:35,610 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice.
13:14:35,610 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.lang:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.io:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.collections:main") which may be changed or removed in future versions without notice.
13:14:35,626 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.apache.commons.codec:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice.
13:14:35,642 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) JBAS018567: Deployment "deployment.dashboard-builder.war" is using a private module ("org.jboss.ironjacamar.jdbcadapters:main") which may be changed or removed in future versions without notice.
13:14:35,907 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment dashboard-builder.war
13:14:38,372 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: dashboard-builder.war
13:14:38,434 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900 1.1.5 (AS71)
13:15:49,679 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry avalon-framework-4.2.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,679 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry batik-all-1.7.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-io-1.3.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry commons-logging-1.0.4.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry serializer-2.7.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry servlet-2.2.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,695 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xalan-2.7.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xercesImpl-2.7.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-1.3.04.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-ext-1.3.04.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlgraphics-commons-1.3.1.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry fop-hyph.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,710 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_codec.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,726 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_core.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,726 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jai_imageio.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jimi-1.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xmlunit1.0.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/fop-0.95.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,757 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry activation.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb1-impl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-impl-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jaxb-impl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry jsr173_1.0_api.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,773 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry activation.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jaxb-xjc-2.2.5.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,788 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis-1.0.b2.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jbpmmigration-0.11.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,788 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry log4j-1.2.16.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/jbpmmigration-0.11.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/serializer-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xercesImpl.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,804 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry xml-apis.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,866 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path entry serializer.jar in "/D:/New folder/jbpm-6.0.0.Final-installer-full/jbpm-installer/content/jbpm-console.war/WEB-INF/lib/xalan-2.7.1.jar" does not point to a valid jar for a Class-Path reference.
13:15:49,991 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException,org.springframework.beans.factory.xml.NamespaceHandlerResolver' for service type 'org.apache.cxf.bus.factory'
13:15:50,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
13:15:50,007 WARN [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
13:15:50,194 INFO [org.jboss.as.jpa] (MSC service thread 1-3) JBAS011401: Read persistence.xml for org.jbpm.domain
13:15:52,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.jbpm-console.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice.
13:15:52,815 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.jbpm-console.war" is using a private module ("org.jboss.netty:main") which may be changed or removed in future versions without notice.
13:15:52,924 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016002: Processing weld deployment jbpm-console.war
13:15:52,986 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named RetryTrackerSingleton in deployment unit deployment "jbpm-console.war" are as follows:
java:global/jbpm-console/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:app/jbpm-console/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:module/RetryTrackerSingleton!org.kie.services.remote.jms.RetryTrackerSingleton
java:global/jbpm-console/RetryTrackerSingleton
java:app/jbpm-console/RetryTrackerSingleton
java:module/RetryTrackerSingleton
13:15:53,901 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:15:53,901 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
13:15:53,911 WARN [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010402: Unable to instantiate driver class "org.h2.Driver": org.jboss.msc.service.DuplicateServiceException: Service jboss.jdbc-driver.jbpm-console_warorg_h2_Driver_1_3 is already registered
13:15:53,911 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jbpm-console.war
13:15:53,931 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015954: Admin console is not enabled
13:15:53,931 ERROR [org.jboss.as] (MSC service thread 1-2) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 140455ms - Started 323 of 754 services (376 services failed or missing dependencies, 53 services are passive or on-demand)
13:15:54,131 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "jbpm-console.war" was rolled back with no failure message
13:15:54,141 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "dashboard-builder.war" was rolled back with failure message JBAS014750: Operation handler failed to complete
13:15:55,746 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment dashboard-builder.war in 1596ms
13:15:59,537 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment jbpm-console.war in 5393ms
13:15:59,537 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.naming.context.java.JmsXA (missing) dependents: [service jboss.naming.context.java.module.jbpm-console.jbpm-console.env."org.kie.services.remote.jms.RequestMessageBean".connectionFactory, service jboss.naming.context.java.module.jbpm-console.jbpm-console.env."org.kie.services.remote.jms.RequestMessageBean".factory]
service jboss.ra.hornetq-ra (missing) dependents: [service jboss.deployment.unit."jbpm-console.war".component.JMSAuditProcessor.CREATE, service jboss.deployment.unit."jbpm-console.war".component.TaskServiceRequesMessageBean.CREATE, service jboss.deployment.unit."jbpm-console.war".component.KieSessionRequesMessageBean.CREATE]
13:15:59,537 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => "JBAS014750: Operation handler failed to complete"}}
13:15:59,552 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS014654: Composite operation was rolled back
Can any one of you help to get rid of this issue?
In order to deploy JBPM in jboss server we need run in standalone-full mode.
In jboss->standalone-->configuration standalone.xml and standalone-full.xml will be there. Normally jboss will configured with standalone.xml so we need to change as standalone-full.xml and run.
This error will be solved.
Can you try the new versions? 6.1 and 6.2.CRx ?
That kind of issue seems to be caused because the application server wasn't started with the full profile, but ant start.demo should that for you, unless you modify it in some way or provided another server installation.

JavaEE and Eclipse: Setting up JPA with EAR (EJB JBA WAR)

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>