Currently, my service is running on http://localhost:8080/MyService/. I want to change localhost to service.example.com - http://service.example.com:8080/MyService/. I updated standalone-full.xml with the new alias.
<subsystem xmlns="urn:jboss:domain:web:2.1" default-virtual-server="default-host" native="false">
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" />
<virtual-server name="default-host" enable-welcome-root="true">
<alias name="localhost"/>
<alias name="service.example.com"/>
</virtual-server>
</subsystem>
But it did not work. I am getting "This Webpage is not available" message. Please suggest.
Update:
Changed jboss-web.xml as above. When deploy my war file, I am getting 404 error.
jboss-web.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-web>
<security-domain>java:/jaas/EmpMem</security-domain>
<context-root>/</context-root>
<virtual-host>service.example.com</virtual-host>
</jboss-web>
standalone-full.xml
Server Log:
16:09:21,705 ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] (MSC service thread 1-7) Exception during createSubject()JBAS013303: Runtime Exception:: java.lang.RuntimeException: JBAS013303: Runtime Exception:
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:56)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:317)
at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:146)
at org.jboss.security.plugins.JBossSecuritySubjectFactory.createSubject(JBossSecuritySubjectFactory.java:83)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1078)
at org.jboss.jca.deployers.common.AbstractDsDeployer$1.run(AbstractDsDeployer.java:1073)
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_51]
at org.jboss.jca.deployers.common.AbstractDsDeployer.createSubject(AbstractDsDeployer.java:1072)
at org.jboss.jca.deployers.common.AbstractDsDeployer.deployDataSource(AbstractDsDeployer.java:600)
at org.jboss.jca.deployers.common.AbstractDsDeployer.createObjectsAndInjectValue(AbstractDsDeployer.java:282)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer.deploy(AbstractDataSourceService.java:316)
at org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.start(AbstractDataSourceService.java:120)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: org.jboss.modules.ModuleNotFoundException: com.usaa.loginmodule:main
at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:240) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.as.security.plugins.SecurityActions.getModuleClassLoader(SecurityActions.java:61)
at org.jboss.as.security.plugins.ModuleClassLoaderLocator.get(ModuleClassLoaderLocator.java:47)
... 16 more
16:09:21,718 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:/usecom_sau]
16:09:21,734 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221013: Using NIO Journal
16:09:21,911 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221034: Waiting to obtain live lock
16:09:21,912 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221035: Live Server Obtained live lock
16:09:21,917 WARN [jacorb.codeset] (MSC service thread 1-4) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1
16:09:21,940 INFO [org.jboss.as.jacorb] (MSC service thread 1-4) JBAS016330: CORBA ORB Service started
16:09:22,009 INFO [org.jboss.web] (ServerService Thread Pool -- 61) JBAS018210: Register web context: /JBOSSWAR
16:09:22,035 INFO [org.jboss.as.jacorb] (MSC service thread 1-2) JBAS016328: CORBA Naming Service started
16:09:22,083 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:22,110 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:22,163 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.23 (redhat)
16:09:22,170 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:22,352 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5455 for CORE protocol
16:09:22,354 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221020: Started Netty Acceptor version 3.6.9.Final-redhat-1-4cc400c 127.0.0.1:5445 for CORE protocol
16:09:22,355 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221007: Server is now live
16:09:22,356 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221001: HornetQ Server version 2.3.20.Final (2.3.20, 123) [43f01d80-b3cb-11e4-a1e5-0d8484f2438a]
16:09:22,371 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
16:09:22,372 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 61) HQ221003: trying to deploy queue jms.queue.fooQueue
16:09:22,376 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:/queue/foo
16:09:22,377 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/foo
16:09:22,378 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
16:09:22,414 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-6) JBAS010406: Registered connection factory java:/JmsXA
16:09:22,445 INFO [org.hornetq.ra] (MSC service thread 1-6) HornetQ resource adaptor started
16:09:22,446 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-6) IJ020002: Deployed: file://RaActivatorhornetq-ra
16:09:22,447 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-4) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
16:09:22,594 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "JBOSSEAR.ear" (runtime-name : "JBOSSEAR.ear")
16:09:22,630 INFO [org.jboss.as.server] (ServerService Thread Pool -- 32) JBAS018559: Deployed "ent_securityprefs_empMemService.war" (runtime-name : "ent_securityprefs_empMemService.war")
16:09:22,631 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
16:09:22,717 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:09:22,718 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 3347ms - Started 360 of 399 services (2 services failed or missing dependencies, 75 services are lazy, passive or on-demand)
16:09:27,677 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:27,686 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 14ms
16:09:27,757 INFO [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS018558: Undeployed "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:27,759 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.jboss.as.weld.webtier.jsp.JspInitializationListener".START (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
service jboss.web.deployment."emp.example.com"./.realm (missing) dependents: [service jboss.deployment.unit."ent_securityprefs_empMemService.war".deploymentCompleteService]
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
16:09:42,782 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) JBAS015003: Found ent_securityprefs_empMemService.war in deployment directory. To trigger deployment create a file called ent_securityprefs_empMemService.war.dodeploy
16:09:42,788 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "ent_securityprefs_empMemService.war" (runtime-name: "ent_securityprefs_empMemService.war")
16:09:42,834 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016002: Processing weld deployment ent_securityprefs_empMemService.war
16:09:42,841 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: ent_securityprefs_empMemService.war
16:09:42,843 INFO [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016008: Starting weld service for deployment ent_securityprefs_empMemService.war
16:09:42,889 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.web.deployment."emp.example.com"./: org.jboss.msc.service.StartException in service jboss.web.deployment."emp.example.com"./: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1936) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]
at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:353)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)
at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)
at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.doInject(ServiceControllerImpl.java:1704) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl.access$2000(ServiceControllerImpl.java:52) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.performInjections(ServiceControllerImpl.java:1949) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1908) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
... 3 more
16:09:42,893 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "ent_securityprefs_empMemService.war" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.web.deployment.\"emp.example.com\"./" => "org.jboss.msc.service.StartException in service jboss.web.deployment.\"emp.example.com\"./: Failed to start service
Caused by: java.lang.IllegalArgumentException: JBWEB000250: Child container with name already exists"}}
16:09:42,894 INFO [org.jboss.weld.deployer] (MSC service thread 1-6) JBAS016009: Stopping weld service for deployment ent_securityprefs_empMemService.war
16:09:42,897 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment ent_securityprefs_empMemService.war (runtime-name: ent_securityprefs_empMemService.war) in 4ms
16:09:42,897 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report
JBAS014776: Newly corrected services:
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."javax.faces.webapp.FacetTag".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.catalina.servlets.DefaultServlet".START (no longer required)
service jboss.deployment.unit."ent_securityprefs_empMemService.war".component."org.apache.jasper.servlet.JspServlet".START (no longer required)
service jboss.web.deployment."emp.example.com"./.realm (no longer required)
JBAS014777: Services which failed to start: service jboss.web.deployment."emp.example.com"./
you need to specify an appropriate virtual-host definition in your jboss-web.xml descriptor.
<jboss-web>
<context-root>/</context-root>
<virtual-host>www.mydot.com</virtual-host>
</jboss-web>
Click here to read more
Related
Using Red Hat WildFly 27.0.1 I'm trying to migrate Mojarra 4.0.0.SP01 to MyFaces 4.0.
Trying to use document "7.26. Jakarta Server Faces Configuration" at:
https://docs.wildfly.org/27/Admin_Guide.html#Jakarta_Server_Faces
Also I can't run "7.26.2. Changing the default Jakarta Server Faces implementation":
./jboss-cli.sh /subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=<JSF_IMPL_NAME>-<JSF_VERSION>)
I find the document conflicts.
Also "Working of the Multi-JSF Implementation" (posted on WildFly Forum).
How can I do this? TIA.
Posted on WildFly Forum: "That support is currently not working correctly. We have an open JIRA to address that, but we've simply had higher priorities. I hope to get to that "soon", but I can't make any promises. Principal Software Engineer, Red Hat JBoss EAP"
Have upgraded to MyFaces 4.0.0-RC4. Unable to resolve "WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid":
15:00:15,485 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
15:00:17,208 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
15:00:17,223 WARN [org.jboss.as.jsf] (MSC service thread 1-8) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0-RC4'. Default version 'myfaces-impl-4.0.0' will be used instead.
15:00:17,223 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,225 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,226 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
15:00:17,244 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 17ms
Next ...
Have added to WildFly 27 with:
com/sun/jsf-impl/myfaces-impl-4.0.0/myfaces-impl-4.0.0-RC4.jar
com/sun/jsf-impl/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/module.xml
javax/faces/api/myfaces-impl-4.0.0/myfaces-api-4.0.0-RC4.jar
org/apache/commons/digester/main/commons-digester3-3.2.jar
org/apache/commons/digester/main/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/module.xml
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
org/jboss/as/jsf-injection/myfaces-impl-4.0.0/weld-jsf-5.1.0.Final.jar
Run:
./jboss-cli.sh
connect
/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-impl-4.0.0)
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
Then:
/subsystem=jsf:list-active-jsf-impls()
Deployed test WAR:
14:03:01,310 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "java-jakarta-primefaces-1.0.war" (runtime-name: "java-jakarta-primefaces-1.0.war")
14:03:03,431 INFO [org.jboss.as.jpa] (MSC service thread 1-8) WFLYJPA0002: Read persistence.xml for io.aturanj.jakarta.pu
14:03:03,455 WARN [org.jboss.as.jsf] (MSC service thread 1-2) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-impl-4.0.0'. Default version 'myfaces-impl-4.0.0' will be used instead.
14:03:03,456 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-jakarta-primefaces-1.0.war".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "java-jakarta-primefaces-1.0.war"
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:189)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc#1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads#2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
at org.jboss.as.jsf#27.0.1.Final//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,458 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "java-jakarta-primefaces-1.0.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,461 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "java-jakarta-primefaces-1.0.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"java-jakarta-primefaces-1.0.war\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"java-jakarta-primefaces-1.0.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid"}}
14:03:03,487 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0028: Stopped deployment java-jakarta-primefaces-1.0.war (runtime-name: java-jakarta-primefaces-1.0.war) in 26ms
14:08:35,964 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0009: Content /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6 is obsolete and will be removed
14:08:35,967 INFO [org.jboss.as.repository] (ServerService Thread Pool -- 86) WFLYDR0002: Content removed from location /usr/local/Cellar/wildfly-as/wildfly-preview-27.0.1.Final-MyFaces/standalone/data/content/fc/c21529f2a77775585d0b6dc2bc91c7ae02d4f6/content
Results still with:
Default Jakarta Server Faces implementation slot 'myfaces-impl-4.0.0' is invalid
Answer - MyFaces won't run/deploy on:
wildfly-preview-27.0.1.Final
Works with:
wildfly-27.0.1.Final
I'm currently upgrading my Jboss5 project to Jboss7. As of now, we still have seam2 and jsf 1.2 integrated into the project. Those will eventually be phased out/upgraded, but for now I just need the application to deploy. I've worked through a ton of bugs, but am stuck on this one:
16:53:49,285 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].
[default-host].[/xxx]] (MSC service thread 1-1) Exception sending
context initialized event to listener instance of class
com.sun.faces.config.ConfigureListener: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! org.jboss.seam.jsf.SeamApplicationFactory
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:215) [jsf-impl-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:200) [jsf-impl-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.13.Final.jar:]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.13.Final.jar:]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
Caused by: java.lang.InstantiationException: org.jboss.seam.jsf.SeamApplicationFactory
at java.lang.Class.newInstance(Class.java:364) [rt.jar:1.7.0_75]
at javax.faces.FactoryFinder.getImplGivenPreviousImpl(FactoryFinder.java:537) [jsf-api-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at javax.faces.FactoryFinder.getImplementationInstance(FactoryFinder.java:405) [jsf-api-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at javax.faces.FactoryFinder.access$400(FactoryFinder.java:135) [jsf-api-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:717) [jsf-api-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:239) [jsf-api-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at com.sun.faces.config.processor.FactoryConfigProcessor.verifyFactoriesExist(FactoryConfigProcessor.java:187) [jsf-impl-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:132) [jsf-impl-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:205) [jsf-impl-1.2_15-jbossorg-2.jar:1.2_15.jbossorg-1-20111019-SNAPSHOT]
... 9 more
16:53:49,338 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Error listenerStart
16:53:49,340 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-1) Context [/xxx] startup failed due to previous errors
16:53:49,354 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Scheduler xxxScheduler_$_NON_CLUSTERED shutting down.
16:53:49,356 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Scheduler xxxScheduler_$_NON_CLUSTERED paused.
16:53:49,361 INFO [org.quartz.core.QuartzScheduler] (MSC service thread 1-1) Scheduler xxxScheduler_$_NON_CLUSTERED shutdown complete.
16:53:49,380 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.web.deployment.default-host./xxx: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./xxx: JBAS018040: Failed to start context
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:95)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.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_75]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
I've read that the cause might be some jar conflicts, but I'm struggling to find out which ones are causing problems. The project was previously running with jsf 2.2 (I believe, definitely something over 2), but I downgraded it to 1.2 for the time being due to a conflict with Seam 2.0.
Any help would be greatly appreciated. Thanks!
Update
I should have been more specific - I am upgrading to JBoss 7.1.1
I have followed this link to install Wildfly on EC2 Linux instance. After it was installed I tried to run the server using
service wildfly start
After a while it threw an error.
It says wildfly server started with errors but the server was not started infact stopped right after it was started. This is my Log file.
2016-07-20 09:18:10,571 INFO [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
2016-07-20 09:18:11,255 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
2016-07-20 09:18:11,499 INFO [org.jboss.as] (MSC service thread 1-2) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = UTF-8
file.encoding.pkg = sun.io
file.separator = /
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = /opt/wildfly/jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/endorsed
java.ext.dirs = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
java.home = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre
java.io.tmpdir = /tmp
java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.net.preferIPv4Stack = true
java.runtime.name = OpenJDK Runtime Environment
java.runtime.version = 1.8.0_91-b14
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.util.logging.manager = org.jboss.logmanager.LogManager
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.8.0_91
java.vm.info = mixed mode
java.vm.name = OpenJDK 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.91-b14
javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder
javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory
javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory
javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory
jboss.home.dir = /opt/wildfly
jboss.host.name = ip-172-31-25-47
jboss.modules.dir = /opt/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = ip-172-31-25-47
jboss.qualified.host.name = ip-172-31-25-47
jboss.server.base.dir = /opt/wildfly/standalone
jboss.server.config.dir = /opt/wildfly/standalone/configuration
jboss.server.data.dir = /opt/wildfly/standalone/data
jboss.server.deploy.dir = /opt/wildfly/standalone/data/content
jboss.server.log.dir = /opt/wildfly/standalone/log
jboss.server.name = ip-172-31-25-47
jboss.server.persist.config = true
jboss.server.temp.dir = /opt/wildfly/standalone/tmp
line.separator =
logging.configuration = file:/opt/wildfly/standalone/configuration/logging.properties
module.path = /opt/wildfly/modules
org.jboss.boot.log.file = /opt/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 4.4.11-23.53.amzn1.x86_64
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/classes
sun.boot.library.path = /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.91-0.b14.10.amzn1.x86_64/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.standalone -Djboss.home.dir=/opt/wildfly -Djboss.server.base.dir=/opt/wildfly/standalone
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = UTF-8
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /opt/wildfly-10.0.0.Final/bin
user.home = /root
user.language = en
user.name = root
user.timezone = Etc/UTC
2016-07-20 09:18:11,502 DEBUG [org.jboss.as.config] (MSC service thread 1-2) VM Arguments: -D[Standalone] -Xms2048m -Xmx2048m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file=/opt/wildfly/standalone/log/server.log -Dlogging.configuration=file:/opt/wildfly/standalone/configuration/logging.properties
2016-07-20 09:18:16,598 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
2016-07-20 09:18:16,664 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.4.Final
2016-07-20 09:18:16,708 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.4.Final
2016-07-20 09:18:16,919 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.18.Final
2016-07-20 09:18:17,066 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem
2016-07-20 09:18:16,992 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.
2016-07-20 09:18:17,085 INFO [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem
2016-07-20 09:18:17,104 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension
2016-07-20 09:18:16,975 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]
2016-07-20 09:18:17,087 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.
2016-07-20 09:18:17,363 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 2 core threads with 16 task threads based on your 1 available processors
2016-07-20 09:18:17,433 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,849 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0003: Undertow 1.3.15.Final starting
2016-07-20 09:18:17,861 INFO [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.4.Final
2016-07-20 09:18:17,850 INFO [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)
2016-07-20 09:18:18,081 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2016-07-20 09:18:18,162 INFO [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service
2016-07-20 09:18:18,173 INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2016-07-20 09:18:18,708 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2
2016-07-20 09:18:19,244 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/opt/wildfly/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
2016-07-20 09:18:19,731 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 4 (per class), which is derived from the number of CPUs on this host.
2016-07-20 09:18:19,733 INFO [org.jboss.as.ejb3] (MSC service thread 1-2) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 16 (per class), which is derived from thread worker pool sizing.
2016-07-20 09:18:19,943 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
2016-07-20 09:18:20,327 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 0.0.0.0:28080
2016-07-20 09:18:20,328 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
2016-07-20 09:18:21,779 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)
2016-07-20 09:18:22,045 INFO [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-1) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final
2016-07-20 09:18:22,208 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory /opt/wildfly/standalone/deployments
2016-07-20 09:18:22,208 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:18:23,028 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2016-07-20 09:18:23,028 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2016-07-20 09:18:23,029 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 13530ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)
2016-07-20 09:20:40,572 INFO [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.
2016-07-20 09:20:40,617 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS]
2016-07-20 09:20:40,762 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0019: Host default-host stopping
2016-07-20 09:20:40,780 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0008: Undertow HTTP listener default suspending
2016-07-20 09:20:40,781 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0007: Undertow HTTP listener default stopped, was bound to 0.0.0.0:28080
2016-07-20 09:20:40,781 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0019: Stopped Driver service with driver-name = h2
2016-07-20 09:20:40,785 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0004: Undertow 1.3.15.Final stopping
2016-07-20 09:20:40,815 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in 206ms
Looking at this log file I am unable to comprehend the issue which causing the server to stop.
Update-1:
Thanks to #James R. Perkins I looked at /var/log/wildfly/console.log and the issue is wildfly was unable to write to its child files. Like
Caused by: java.io.FileNotFoundException: /opt/wildfly/standalone/log/server.log (Permission denied)
Caused by: java.lang.IllegalStateException: WFLYDR0006: Directory /opt/wildfly/standalone/data/content is not writable
Even though wildfly is owner of wildfly parent folder
Do I have to make it the owner of all of its sub folders?
The solution to my particular problem was the issue of permissions. Only root had permissions but all the children didn't had wildfly as owner. Applying
chown -R
did the job. Thanks to #James R. Perkins I checked my console logs that were in /var/logs/wildfly/console.log i found the issue.
I'm developing with IntelliJ IDEA 14 the JSF application which has to be run under JBoss 7.1.1
JBoss deploys and starts correctly(running in IDE):
=========================================================================
[2015-03-11 09:44:31,277] Artifact bas_jsf:war exploded: Server is not connected. Deploy is not available.
Detected server admin port: 9999
JBoss Bootstrap Environment
JBOSS_HOME: /Users/Danil/IdeaProjects/jboss-as-7.1.1.Final
JAVA: /Library/Java/JavaVirtualMachines/jdk1.7.0_75.jdk/Contents/Home/bin/java
JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
Detected server http port: 8080
=========================================================================
21:44:30,521 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
21:44:31,582 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
21:44:31,671 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
21:44:33,068 INFO [org.xnio] XNIO Version 3.0.3.GA
21:44:33,070 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
21:44:33,082 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
21:44:33,095 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
21:44:33,125 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
21:44:33,129 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem
21:44:33,160 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
21:44:33,169 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
21:44:33,199 INFO [org.jboss.as.connector] (MSC service thread 1-6) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
21:44:33,214 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
21:44:33,215 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem
21:44:33,245 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
21:44:33,259 INFO [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem
21:44:33,266 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.7.Final
21:44:33,276 INFO [org.jboss.as.mail.extension] (MSC service thread 1-7) JBAS015400: Bound mail session [java:jboss/mail/Default]
21:44:33,305 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
21:44:33,481 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-4) JBoss Web Services - Stack CXF Server 4.0.2.GA
21:44:33,676 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-7) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080
log4j:WARN No appenders could be found for logger (org.jboss.logging).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
21:44:34,213 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
21:44:34,457 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /Users/Danil/IdeaProjects/jboss-as-7.1.1.Final/standalone/deployments
21:44:34,471 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /127.0.0.1:4447
21:44:34,472 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /127.0.0.1:9999
21:44:34,623 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
21:44:34,624 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 4696ms - Started 133 of 208 services (74 services are passive or on-demand)
Connected to server
[2015-03-11 09:44:35,152] Artifact bas_jsf:war exploded: Artifact is being deployed, please wait...
21:44:35,295 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "bas_jsf_war_exploded.war"
21:44:35,595 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-7) Initializing Mojarra 2.1.7-jbossorg-1 (20120227-1401) for context '/bas_jsf_war_exploded'
21:44:36,416 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-7) Hibernate Validator 4.2.0.Final
21:44:36,612 INFO [org.jboss.web] (MSC service thread 1-7) JBAS018210: Registering web context: /bas_jsf_war_exploded
21:44:36,642 INFO [org.jboss.as.server] (management-handler-thread - 2) JBAS018559: Deployed "bas_jsf_war_exploded.war"
[2015-03-11 09:44:36,677] Artifact bas_jsf:war exploded: Artifact is deployed successfully
[2015-03-11 09:44:36,678] Artifact bas_jsf:war exploded: Deploy took 1,526 milliseconds
But page opens in browser is blank, because it is'nt rendered:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:h="http://xmlns.jcp.org/jsf/html"
xmlns:ui="http://xmlns.jcp.org/jsf/facelets"
xmlns:f="http://xmlns.jcp.org/jsf/core">
<f:view>
<h:outputLabel value="Hello, world"></h:outputLabel>
</f:view>
</html>
In project setting library Mojarra-2.2.1 scoped as compile.
In JBoss configuration JSF library jsf-api-1.2_15-jbossorg-2.jar is included
web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd"
version="3.1">
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.xhtml</url-pattern>
</servlet-mapping>
</web-app>
I've got a problem. I'm trying to run Liferay 6.2 on my JBoss 7.2. I followed the installation steps (https://www.liferay.com/de/documentation/liferay-portal/6.2/user-guide/-/ai/installing-liferay-on-jboss-7-liferay-portal-6-2-user-guide-15-en) but I'm not able to deploy/start liferay. I'm getting HornetQ exceptions all the time.
17:28:17,271 INFO [org.hornetq.core.server] (MSC service thread 1-9) HQ221004: HornetQ Server version 2.3.0.CR1 (buzzzzz!, 122) [fa28bdb6-0fc3-11e3-ad50-a3678588ef85] stopped
17:30:25,437 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122018: Can not connect to XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null] on auto-generated resource recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119026: Cannot connect to server(s). Tried with all available servers.]
at [...]
17:30:25,440 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122010: XA Recovery can not connect to any hornetq server on recovery [XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null]]
17:30:25,442 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery
at [...]
Caused by: HornetQException[errorType=NOT_CONNECTED message=null]
at [...]
... 7 more
17:30:25,443 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122018: Can not connect to XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null] on auto-generated resource recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119026: Cannot connect to server(s). Tried with all available servers.]
at [...]
17:30:25,444 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122010: XA Recovery can not connect to any hornetq server on recovery [XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null]]
17:30:25,444 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122018: Can not connect to XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null] on auto-generated resource recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119026: Cannot connect to server(s). Tried with all available servers.]
at [...]
17:30:25,445 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122010: XA Recovery can not connect to any hornetq server on recovery [XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null]]
17:30:25,446 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122018: Can not connect to XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null] on auto-generated resource recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119026: Cannot connect to server(s). Tried with all available servers.]
at [...]
17:30:25,447 WARN [org.hornetq.jms.server] (Periodic Recovery) HQ122010: XA Recovery can not connect to any hornetq server on recovery [XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=8e623d60-82ae-11e3-847c-e5da1aae7895, factory=org-hornetq-core-remoting-impl-invm-InVMConnectorFactory) ?server-id=0], discoveryConfiguration = null, username=null, password=null]]
17:30:25,447 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception XAException.XAER_RMERR: javax.transaction.xa.XAException: Error trying to connect to any providers for xa recovery
at [...]
Caused by: HornetQException[errorType=NOT_CONNECTED message=null]
at [...]
... 7 more
I know Liferay 6.2 is certified against JBoss 7.1, not 7.2 but I already had Liferay 6.1.2 CE running on JBoss 7.2 so I guess there must be a way for 6.2 EE as well.
Does anybody have an idea or can help me out?
Thy and regards
Sebastian
I did some changes to my JBoss config. Moved all Liferay-specific settings from full-ha profile to ha profile (no hornetq in ha). So there are no hornetq errors any more. But still I'm not able to deploy Liferay to my JBoss. Server tries to deploy Liferay but (seems to) stop progressing/working without any further information.
16:12:51,691 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.2.0.Final "Janus" started in 7662ms - Started 164 of 277 services (112 services are passive or on-demand)
16:17:13,699 INFO [org.jboss.as.server.deployment] (MSC service thread 1-30) JBAS015876: Starting deployment of "liferay-portal-6.2.10.1-ee-ga1.war" (runtime-name: "liferay.war")
16:17:33,174 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jaxws-api.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,174 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jsr181-api.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,174 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jsr250-api.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,175 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jsr173_api.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,175 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry sjsxp.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,175 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry woodstox.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,176 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry resolver.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,176 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jaxb-api.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,176 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry activation.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,177 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry stax-utils.jar in /content/liferay.war/WEB-INF/lib/jaxws-rt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,180 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry unoloader.jar in /content/liferay.war/WEB-INF/lib/jurt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,181 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry ../../lib/ in /content/liferay.war/WEB-INF/lib/jurt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,181 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry ../bin/ in /content/liferay.war/WEB-INF/lib/jurt.jar does not point to a valid jar for a Class-Path reference.
16:17:33,181 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry activation.jar in /content/liferay.war/WEB-INF/lib/saaj-impl.jar does not point to a valid jar for a Class-Path reference.
16:17:33,188 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry lib/ant.jar in /content/liferay.war/WEB-INF/lib/truezip.jar does not point to a valid jar for a Class-Path reference.
16:17:33,189 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry lib/lcrypto-jdk14-135.jar in /content/liferay.war/WEB-INF/lib/truezip.jar does not point to a valid jar for a Class-Path reference.
16:17:33,196 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jaxb-api.jar in /content/liferay.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:17:33,197 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry activation.jar in /content/liferay.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:17:33,197 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jsr173_1.0_api.jar in /content/liferay.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:17:33,197 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jaxb1-impl.jar in /content/liferay.war/WEB-INF/lib/jaxb-impl.jar does not point to a valid jar for a Class-Path reference.
16:17:33,200 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry asm-3.3.jar in /content/liferay.war/WEB-INF/lib/asm-xml.jar does not point to a valid jar for a Class-Path reference.
16:17:33,201 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry asm-util-3.3.jar in /content/liferay.war/WEB-INF/lib/asm-xml.jar does not point to a valid jar for a Class-Path reference.
16:17:33,201 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry asm-attrs-3.3.jar in /content/liferay.war/WEB-INF/lib/asm-xml.jar does not point to a valid jar for a Class-Path reference.
16:17:33,202 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry mchange-commons-java-0.2.3.4.jar in /content/liferay.war/WEB-INF/lib/c3p0.jar does not point to a valid jar for a Class-Path reference.
16:17:33,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry commons-cli.jar in /content/liferay.war/WEB-INF/lib/xuggle-xuggler-noarch.jar does not point to a valid jar for a Class-Path reference.
16:17:33,212 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry logback-classic.jar in /content/liferay.war/WEB-INF/lib/xuggle-xuggler-noarch.jar does not point to a valid jar for a Class-Path reference.
16:17:33,213 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry logback-core.jar in /content/liferay.war/WEB-INF/lib/xuggle-xuggler-noarch.jar does not point to a valid jar for a Class-Path reference.
16:17:33,214 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jakarta-oro.jar in /content/liferay.war/WEB-INF/lib/struts.jar does not point to a valid jar for a Class-Path reference.
16:17:33,215 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jaxp-api.jar in /content/liferay.war/WEB-INF/lib/saaj-api.jar does not point to a valid jar for a Class-Path reference.
16:17:33,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry jax-qname.jar in /content/liferay.war/WEB-INF/lib/saaj-api.jar does not point to a valid jar for a Class-Path reference.
16:17:33,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry activation.jar in /content/liferay.war/WEB-INF/lib/saaj-api.jar does not point to a valid jar for a Class-Path reference.
16:17:33,216 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015960: Class Path entry servlet.jar in /content/liferay.war/WEB-INF/lib/saaj-api.jar does not point to a valid jar for a Class-Path reference.
16:17:33,553 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
16:17:33,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'DRIVER=TRUE' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'DEFAULT=ear|jar|war|zip' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,554 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'zip=de.schlichtherle.io.archive.zip.ZipDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'ear|jar|war=de.schlichtherle.io.archive.zip.JarDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'odg|odp|ods|odt=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'otg|otp|ots|ott=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'odb|odf|odm|oth=de.schlichtherle.io.archive.zip.OdfDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,555 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'exe=de.schlichtherle.io.archive.zip.ReadOnlySfxDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'tzp|zip.rae|zip.raes=de.schlichtherle.io.archive.zip.raes.SafeZipRaesDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'tar=de.schlichtherle.io.archive.tar.TarDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'tgz|tar.gz=de.schlichtherle.io.archive.tar.TarGZipDriver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,556 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'tbz2|tar.bz2=de.schlichtherle.io.archive.tar.TarBZip2Driver' for service type 'de.schlichtherle.io.registry.properties'
16:17:33,559 WARN [org.jboss.as.server.deployment] (MSC service thread 1-22) JBAS015893: Encountered invalid class name 'org.kxml2.io.KXmlParser,org.kxml2.io.KXmlSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory'
16:17:33,583 WARN [org.jboss.as.server.deployment] (MSC service thread 1-25) JBAS015897: Could not find Extension-List entry ExtensionListEntry [name=javax.crypto, title=crypto] referenced from ResourceRoot [root="/content/liferay.war/WEB-INF/classes"]
16:17:36,766 INFO [org.jboss.web] (ServerService Thread Pool -- 74) JBAS018210: Register web context:
16:17:37,886 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/]] (ServerService Thread Pool -- 74) Initializing Spring root WebApplicationContext
16:18:03,800 INFO [org.jboss.web] (ServerService Thread Pool -- 79) JBAS018224: Unregister web context: /JvmMonitor
16:18:03,834 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003075: Coyote HTTP/1.1 pausing on: http-/10.173.121.39:8380
16:18:03,843 INFO [org.apache.coyote.http11] (MSC service thread 1-3) JBWEB003077: Coyote HTTP/1.1 stopping on : http-/10.173.121.39:8380
16:18:03,877 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:jboss/datasources/LIFERAY_TEST_DS]
16:18:03,883 INFO [org.apache.coyote.ajp] (MSC service thread 1-31) JBWEB003048: Pausing Coyote AJP/1.3 on ajp-/10.173.121.39:8309
16:18:03,884 INFO [org.apache.coyote.ajp] (MSC service thread 1-31) JBWEB003051: Stopping Coyote AJP/1.3 on ajp-/10.173.121.39:8309
16:18:03,937 INFO [org.jboss.as.server.deployment] (MSC service thread 1-24) JBAS015877: Stopped deployment JvmMonitor.war (runtime-name: JvmMonitor.war) in 150ms
And thats it ...
Solved my issues. If you intend to run Liferay 6.2 on JBoss 7.2 make sure you're using the same version of liferay.war and liferay-dependencies. Even minor differences result in a crippled JBoss Node. Sadly the logfiles don't offer much information about this other than indicating that something might be wrong.