JBAS015810: failed to resolve interface unsecure in jboss 7.1.1.Final - jboss

When i try to deploy my application (JSF, Primefaces and EJB) in JBoss7.1.1.Final, the deployment failed and showing the following error messages.
15:07:54,373 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.network.unsecure: org.jboss.msc.service.StartException in service jboss.network.unsecure: JBAS015810: failed to resolve interface unsecure
at org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:97) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_91]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_91]
15:07:54,399 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
15:07:54,464 INFO [org.jboss.jaxr] (MSC service thread 1-1) JBAS014000: Started JAXR subsystem, binding JAXR connection factory into JNDI as: java:jboss/jaxr/ConnectionFactory
15:07:54,489 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]
15:07:54,531 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.2.GA
15:07:54,841 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /usr/share/jboss-as-7.1.1.Final/standalone/deployments
15:08:00,262 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
service jboss.network.unsecure: org.jboss.msc.service.StartException in service jboss.network.unsecure: JBAS015810: failed to resolve interface unsecure
service jboss.network.management: org.jboss.msc.service.StartException in service jboss.network.management: JBAS015810: failed to resolve interface management
the port is automatically (8080) closing.
Anyone have any idea what is the problem.
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:127.0.0.1}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:127.0.0.1}"/>
</interface>
<!-- TODO - only show this if the jacorb subsystem is added -->
<interface name="unsecure">
<!--
~ Used for IIOP sockets in the standard configuration.
~ To secure JacORB you need to setup SSL
-->
<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
</interface>
</interfaces>

Have you made any changes to standalone.xml or standalone.conf to set a new bind address? In that case, you will most probably need to create a loopback entry in /etc/sysconfig/network-scripts/ifcfg-lo:1.
Check this link for details:
https://developer.jboss.org/thread/222677?tstart=0&_sscc=t

Related

Server is not coming up when we configure HTTPS in wildfly 17 <socket-binding https="management-https"/> under management-interfaces

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?

how to enable admin console in jboss

when i start jboss, it return this:
Calling "D:\Servers\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
"JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -XX:MaxPermSize=256m"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\Servers\jboss-as-7.1.1.Final
JAVA: D:\Program Files\Java\jdk1.7.0_79\bin\java
JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m
===============================================================================
12:35:34,229 INFORMAZIONI [org.jboss.modules] JBoss Modules version 1.1.1.GA
12:35:35,009 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
12:35:35,047 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
12:35:36,728 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
12:35:36,729 INFO [org.xnio] XNIO Version 3.0.3.GA
12:35:36,738 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
12:35:36,743 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
12:35:36,760 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
12:35:36,762 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
12:35:36,780 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
12:35:36,781 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
12:35:36,794 INFO [org.jboss.as.security] (MSC service thread 1-14) JBAS013100: Current PicketBox version=4.0.7.Final
12:35:36,799 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
12:35:36,812 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
12:35:36,818 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
12:35:36,835 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
12:35:36,841 INFO [org.jboss.as.connector] (MSC service thread 1-10) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
12:35:36,852 INFO [org.jboss.as.naming] (MSC service thread 1-16) JBAS011802: Starting Naming Service
12:35:36,858 INFO [org.jboss.as.mail.extension] (MSC service thread 1-16) JBAS015400: Bound mail session [java:jboss/mail/Default]
12:35:37,010 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-13) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
12:35:37,340 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
12:35:38,025 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-15) JBoss Web Services - Stack CXF Server 4.0.2.GA
12:35:38,223 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) JBAS015012: Started FileSystemDeploymentService for directory D:\Servers\jboss-as-7.1.1.Final\standalone\deployments
12:35:38,229 INFO [org.jboss.as.remoting] (MSC service thread 1-16) JBAS017100: Listening on /127.0.0.1:4447
12:35:38,229 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /127.0.0.1:9999
12:35:38,233 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:210) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_79]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:145) [jboss-as-domain-http-interface-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:177) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
12:35:38,459 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
12:35:38,502 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
12:35:38,503 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 4573ms - Started 131 of 208 services (2 services failed or missing dependencies, 74 services are passive or on-demand)
i tried to surf on web, but nothing work...
the page localhost:8080 returns 404 error.
how can i enable the console?
edit
the port is used by another process (thx to ozOli)
the process is the jdk!
i terminate it and then, when i start jboss, it returns:
Calling "D:\Servers\jboss-as-7.1.1.Final\bin\standalone.conf.bat"
"JAVA_OPTS already set in environment; overriding default settings with values: -Xms128m -Xmx512m -XX:MaxPermSize=256m"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\Servers\jboss-as-7.1.1.Final
JAVA: D:\Program Files\Java\jdk1.7.0_79\bin\java
JAVA_OPTS: -XX:+TieredCompilation -Dprogram.name=standalone.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m
===============================================================================
17:38:29,149 INFORMAZIONI [org.jboss.modules] JBoss Modules version 1.1.1.GA
17:38:29,289 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
17:38:29,320 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
17:38:29,825 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
17:38:29,825 INFO [org.xnio] XNIO Version 3.0.3.GA
17:38:29,834 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
17:38:29,839 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
17:38:29,853 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
17:38:29,859 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
17:38:29,870 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
17:38:29,871 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
17:38:29,875 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
17:38:29,876 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
17:38:29,884 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
17:38:29,892 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
17:38:29,908 INFO [org.jboss.as.connector] (MSC service thread 1-15) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
17:38:29,926 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
17:38:29,948 INFO [org.jboss.as.naming] (MSC service thread 1-6) JBAS011802: Starting Naming Service
17:38:29,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
17:38:30,050 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-3) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
17:38:30,075 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-5) JBoss Web Services - Stack CXF Server 4.0.2.GA
17:38:30,243 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-14) JBAS015012: Started FileSystemDeploymentService for directory D:\Servers\jboss-as-7.1.1.Final\standalone\deployments
17:38:30,243 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:4447
17:38:30,243 INFO [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999
17:38:30,246 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment MyWheelEE-war.war
17:38:30,249 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-12) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:210) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_79]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:145) [jboss-as-domain-http-interface-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:177) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
17:38:30,316 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
17:38:30,528 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
17:38:30,556 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "MyWheelEE-war.war"
17:38:31,118 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) Class Path entry lib/eclipselink.jar in "/D:/Servers/jboss-as-7.1.1.Final/bin/content/MyWheelEE-war.war/WEB-INF/lib/MyWheelEEJavaLibrary.jar" does not point to a valid jar for a Class-Path reference.
17:38:31,119 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) Class Path entry lib/javax.persistence_2.1.0.v201304241213.jar in "/D:/Servers/jboss-as-7.1.1.Final/bin/content/MyWheelEE-war.war/WEB-INF/lib/MyWheelEEJavaLibrary.jar" does not point to a valid jar for a Class-Path reference.
17:38:31,120 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) Class Path entry lib/org.eclipse.persistence.jpa.jpql_2.5.2.v20140319-9ad6abd.jar in "/D:/Servers/jboss-as-7.1.1.Final/bin/content/MyWheelEE-war.war/WEB-INF/lib/MyWheelEEJavaLibrary.jar" does not point to a valid jar for a Class-Path reference.
17:38:31,121 WARN [org.jboss.as.server.deployment] (MSC service thread 1-10) Class Path entry lib/javaee-api-6.0.jar in "/D:/Servers/jboss-as-7.1.1.Final/bin/content/MyWheelEE-war.war/WEB-INF/lib/MyWheelEEJavaLibrary.jar" does not point to a valid jar for a Class-Path reference.
17:38:31,165 INFO [org.jboss.as.jpa] (MSC service thread 1-9) JBAS011401: Read persistence.xml for MyWheelEE-warPU
17:38:31,168 INFO [org.jboss.as.jpa] (MSC service thread 1-9) JBAS011401: Read persistence.xml for MyWheelEEJavaLibraryPU
17:38:31,185 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.module.service."deployment.MyWheelEE-war.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.MyWheelEE-war.war".main: Failed to load module: deployment.MyWheelEE-war.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: org.jboss.modules.ModuleNotFoundException: Module org.eclipse.persistence:main is not found in local module loader #4e3e95e6 (roots: D:\Servers\jboss-as-7.1.1.Final\modules)
at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126)
at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275)
at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222)
at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94)
at org.jboss.modules.Module.addPaths(Module.java:841)
at org.jboss.modules.Module.link(Module.java:1181)
at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207)
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208)
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:70) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
... 5 more
17:38:31,193 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015954: Admin console is not enabled
17:38:31,193 ERROR [org.jboss.as] (MSC service thread 1-7) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 2308ms - Started 138 of 218 services (3 services failed or missing dependencies, 76 services are passive or on-demand)
17:38:31,394 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "MyWheelEE-war.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.MyWheelEE-war.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.MyWheelEE-war.war\".main: Failed to load module: deployment.MyWheelEE-war.war:main"}}
17:38:31,419 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment MyWheelEE-war.war in 28ms
17:38:31,419 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.module.service."deployment.MyWheelEE-war.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.MyWheelEE-war.war".main: Failed to load module: deployment.MyWheelEE-war.war:main
17:38:31,419 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.module.service.\"deployment.MyWheelEE-war.war\".main" => "org.jboss.msc.service.StartException in service jboss.module.service.\"deployment.MyWheelEE-war.war\".main: Failed to load module: deployment.MyWheelEE-war.war:main"}}}}
The admin console is most probably disabled. To enable it using the CLI you can use this command:
/core-service=management/management-interface=http-interface/:write-attribute(name=console-enabled,value=true)
FIXED some NVIDIA's process was using 9990 port;)

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>

JBOSS throws exception on startup

I'm starting jboss server through CLI in windows 7. Initially it was starting but then I wrote java code for sending messages to learn JMS. After that I'm getting below exceptions. Could anyone please help me in resolving this.
Note: I've removed java file(Consumer.java) from my system, still somehow exception shows it's referring to my java file.
17:52:18,845 INFO [org.jboss.as.deployment.connector] (MSC service thread 1-7) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
17:52:18,902 INFO [org.jboss.as.messaging] (MSC service thread 1-8) JBAS011601: Bound messaging object to jndi name java:/topic/test
17:52:19,270 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of "Consumer.java"
17:52:19,318 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC00001: Failed to start service jboss.deployment.unit."Consumer.java".STRUCTURE
: org.jboss.msc.service.StartException in service jboss.deployment.unit."Consumer.java".STRUCTURE: Failed to process phase STRUCTURE of deployment "Consumer.java"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.1.Final.jar:7.1.1.Fin
al]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to mount deployment content
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:91) [jboss-as-server-7.1.1.Final.ja
r:7.1.1.Final]
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Fin
al]
... 5 more
Caused by: java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method) [rt.jar:1.7.0_40]
at java.util.zip.ZipFile.<init>(ZipFile.java:215) [rt.jar:1.7.0_40]
at java.util.zip.ZipFile.<init>(ZipFile.java:145) [rt.jar:1.7.0_40]
at java.util.jar.JarFile.<init>(JarFile.java:153) [rt.jar:1.7.0_40]
at java.util.jar.JarFile.<init>(JarFile.java:117) [rt.jar:1.7.0_40]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:97) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.spi.JavaZipFileSystem.<init>(JavaZipFileSystem.java:83) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFS.mountZip(VFS.java:408) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFS.mountZip(VFS.java:434) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.ja
va:95) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:87) [jboss-as-server-7.1.1.Final.ja
r:7.1.1.Final]
... 6 more
17:52:19,488 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "Consumer.java" was rolled back with failure mes
sage {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Consumer.java\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.depl
oyment.unit.\"Consumer.java\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Consumer.java\""}}
17:52:19,492 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015877: Stopped deployment Consumer.java in 4ms
17:52:19,517 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."Consumer.java".STRUCTURE: org.jboss.msc.service.StartException in servic
e jboss.deployment.unit."Consumer.java".STRUCTURE: Failed to process phase STRUCTURE of deployment "Consumer.java"
17:52:19,529 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
17:52:19,544 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back.
Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"Consumer.java\".STRUCTURE" => "org.jboss.msc.ser
vice.StartException in service jboss.deployment.unit.\"Consumer.java\".STRUCTURE: Failed to process phase STRUCTURE of deployment \"Consumer.java\""}}}}
17:52:19,550 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 5704ms - Started 171 of 251
services (1 services failed or missing dependencies, 78 services are passive or on-demand)
Thanks in advance.
I've come across this problem when deploying an ear file that contained an empty jar (view the contents and order by size). Check your ear file for an empty jar, if it contains one remove it.
Regards,
Saz

How to deploy cxf web service on jboss eap 6.1

Hey guys I am trying to deploy my cxf web service on jboss-eap-6.1 but its not getting done.. I am providing the stack trace below:
16:37:30,821 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."GenericEnterpriseApplicationSkeleton.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."GenericEnterpriseApplicationSkeleton.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "GenericEnterpriseApplicationSkeleton.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_40]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_40]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_40]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011030: Could not configure component org.apache.cxf.wsn.client.Publisher
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:91)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.apache.cxf.wsn.client.Publisher
at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:607)
at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:80)
... 6 more
16:37:30,854 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "GenericEnterpriseApplicationSkeleton.war" (runtime-name : "GenericEnterpriseApplicationSkeleton.war")
16:37:30,854 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "EAApplication.ear" (runtime-name : "EAApplication.ear")
16:37:30,855 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."GenericEnterpriseApplicationSkeleton.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."GenericEnterpriseApplicationSkeleton.war".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment "GenericEnterpriseApplicationSkeleton.war"
16:37:31,036 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http:// 127.0.0.1:9990/management
16:37:31,037 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http:// 127.0.0.1:9990
16:37:31,037 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started (with errors) in 5102ms - Started 198 of 260 services (1 services failed or missing dependencies, 60 services are passive or on-demand)
Please do have a look.
I got similar but not the exact error as mentioned by you. I solved it by bypassing the default Jboss Webservices implementation.
I commented out the following lines in the standalone.xml
<extension module="org.jboss.as.webservices"/>
and the subsystem
<subsystem xmlns="urn:jboss:domain:webservices:1.2">
<modify-wsdl-address>true</modify-wsdl-address>
<wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
<endpoint-config name="Standard-Endpoint-Config"/>
<endpoint-config name="Recording-Endpoint-Config">
<pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
<handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
</pre-handler-chain>
</endpoint-config>
<client-config name="Standard-Client-Config"/>
</subsystem>
Please see the link on how I got the idea - https://developer.jboss.org/thread/221654. Hope this helps.