WildFly 9 application server deployment errors on Intellij IDEA 14 - jsf

When I am creating a web project deploy on WildFly application server, I'm getting following errors.
Server logs:
2015-10-29 14:23:20,060 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment "JavaEEFirstProject.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:95)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
... 5 more
Caused by: java.io.FileNotFoundException: C:\Users\mert\IdeaProjects\JavaEEFirstProject\out\artifacts\JavaEEFirstProject\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:146)
at org.jboss.vfs.spi.RootFileSystem.openInputStream(RootFileSystem.java:51)
at org.jboss.vfs.VirtualFile.openStream(VirtualFile.java:254)
at org.jboss.vfs.VFS.mountZipExpanded(VFS.java:533)
at org.jboss.as.server.deployment.DeploymentMountProvider$Factory$ServerDeploymentRepositoryImpl.mountDeploymentContent(DeploymentMountProvider.java:108)
at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:91)
... 6 more
2015-10-29 14:23:20,066 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "JavaEEFirstProject.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"JavaEEFirstProject.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\mert\\IdeaProjects\\JavaEEFirstProject\\out\\artifacts\\JavaEEFirstProject\\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)"}}
2015-10-29 14:23:20,069 ERROR [org.jboss.as.server] (management-handler-thread - 2) WFLYSRV0021: Deploy of deployment "JavaEEFirstProject.war" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"JavaEEFirstProject.war\".STRUCTURE: WFLYSRV0153: Failed to process phase STRUCTURE of deployment \"JavaEEFirstProject.war\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYSRV0160: Failed to mount deployment content
Caused by: java.io.FileNotFoundException: C:\\Users\\mert\\IdeaProjects\\JavaEEFirstProject\\out\\artifacts\\JavaEEFirstProject\\JavaEEFirstProject.war (Sistem belirtilen yolu bulamıyor)"}}
2015-10-29 14:23:20,078 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment JavaEEFirstProject.war (runtime-name: JavaEEFirstProject.war) in 7ms
2015-10-29 14:23:20,080 INFO [org.jboss.as.controller] (management-handler-thread - 2) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."JavaEEFirstProject.war".STRUCTURE
On Intellij IDEA 14 has artifacts for deployed files. And I think I have a problem on this artifacts section because i am getting artifacts path errors with FileNotFoundException named. I am sharing artifacts print on following.
How can I add .war file with artifacts pages?

Call "Build > Build Artifacts" and make sure (via Windows Explorer for example) that in the the JavaEEFirstProject folder there is a file called "JavaEEFirstProject.war". Then redeploy it from IDEA.

Related

How do I change JSF impl of WildFly 27.0.1 from Mojarra 4.0.0.SP01 to MyFaces 4.0

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

Migrate WildFly 26.x/27.x Mojarra to Jakarta 10 MyFaces 4.0.0.RC2

Using: WildFly 26.1.2.Final & Preview-27.0.0.Beta1 with Jakarta 10.0.
As an issue I have with PrimeFaces 'TabView' (7.x - 12.x) using Mojarra (now 4.0.0.SP01) with WildFly 26.1.2.Final/Preview-27.0.0.Beta1. It has been suggested I migrate to MyFaces.
I've followed the guides at:
https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.2/html/configuration_guide/javaserver_faces_jsf_configuration#doc-wrapper
&
https://docs.wildfly.org/26/Admin_Guide.html#Jakarta_Server_Faces
Set & run:
./jboss-cli.sh -c "/subsystem=jsf/:write-attribute(name=default-jsf-impl-slot,value=myfaces-4.0.0-RC2)"
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
{"outcome" => "success"}
Using MyFaces 4.0.0-RC2 I deploy my EAR & I get:
14:34:28,769 WARN [org.jboss.as.jsf] (MSC service thread 1-2) WFLYJSF0005: Unknown Jakarta Server Faces version 'myfaces-4.0.0-RC2'. Default version 'myfaces-4.0.0-RC2' will be used instead.
14:34:28,770 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."NOTiFYmoto.ear".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."NOTiFYmoto.ear".DEPENDENCIES: WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment "NOTiFYmoto.ear"
at org.jboss.as.server#19.0.0.Beta18//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-4.0.0-RC2' is invalid
at org.jboss.as.jsf#27.0.0.Beta1//org.jboss.as.jsf.deployment.JSFDependencyProcessor.deploy(JSFDependencyProcessor.java:94)
at org.jboss.as.server#19.0.0.Beta18//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
... 8 more
14:34:28,772 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "NOTiFYmoto.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"NOTiFYmoto.ear\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"NOTiFYmoto.ear\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-4.0.0-RC2' is invalid"}}
14:34:28,773 ERROR [org.jboss.as.controller.management-operation] (External Management Request Threads -- 1) WFLYCTL0013: Operation ("add") failed - address: ([("deployment" => "NOTiFYmoto.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"NOTiFYmoto.ear\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"NOTiFYmoto.ear\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-4.0.0-RC2' is invalid"}}
14:34:28,775 ERROR [org.jboss.as.server] (External Management Request Threads -- 1) WFLYSRV0021: Deploy of deployment "NOTiFYmoto.ear" was rolled back with the following failure message:
{"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"NOTiFYmoto.ear\".DEPENDENCIES" => "WFLYSRV0153: Failed to process phase DEPENDENCIES of deployment \"NOTiFYmoto.ear\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJSF0014: Default Jakarta Server Faces implementation slot 'myfaces-4.0.0-RC2' is invalid"}}
(2) Also both:
/usr/local/Cellar/wildfly-as/wildfly-preview-27.0.0.Beta1.MyFaces/modules/system/layers/base/org/wildfly/extension/clustering/web
References 'mojarra':
<module name="org.wildfly.clustering.faces.mojarra"/>
and:
/usr/local/Cellar/wildfly-as/wildfly-preview-27.0.0.Beta1.MyFaces/modules/system/layers/base/org/wildfly/extension/clustering
also references 'mojarra':
<module name="org.wildfly.clustering.faces.mojarra" xmlns="urn:jboss:module:1.9">
<properties>
<property name="jboss.api" value="private"/>
</properties>
<resources>
<resource-root path="wildfly-clustering-faces-mojarra-27.0.0.Beta1.jar"/>
This error when I follow the "Jakarta Server Faces Configuration".
Any pointers or ideas etc? TIA.

Pentaho 7 CE System Error 0014

I have download Pentaho 7 CE edition and I have not been able to make it work. I have noticed that there is System Error 0014 that pops up in the log.
I have also downloaded Java jre1.8.0_131 and I am using Windows 10 machine. The following is a snippet of the error log in the tomcat.
20:39:08,993 ERROR [OSGIBoot] Error starting Karaf
java.lang.RuntimeException: Could not resolve mvn:org.apache.felix/org.apache.felix.framework/4.2.1
at org.apache.karaf.main.util.SimpleMavenResolver.resolve(SimpleMavenResolver.java:59)
at org.apache.karaf.main.Main.createClassLoader(Main.java:309)
at org.apache.karaf.main.Main.launch(Main.java:229)
at org.pentaho.platform.osgi.KarafBoot$4.run(KarafBoot.java:239)
at java.lang.Thread.run(Unknown Source)
at org.pentaho.platform.osgi.KarafBoot.startup(KarafBoot.java:247)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:443)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:84)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:365)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:332)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:228)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:162)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1834)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
20:39:09,001 ERROR [Logger] Error: Pentaho
20:39:09,005 ERROR [Logger] misc-org.pentaho.platform.engine.core.system.PentahoSystem: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
org.pentaho.platform.api.engine.PentahoSystemException: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:370)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:332)
at org.pentaho.platform.engine.core.system.PentahoSystem.init(PentahoSystem.java:228)
at org.pentaho.platform.web.http.context.SolutionContextListener.contextInitialized(SolutionContextListener.java:162)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4853)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5314)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:145)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:753)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:729)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1092)
at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1834)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:452)
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:434)
at org.pentaho.platform.engine.core.system.PentahoSystem.access$000(PentahoSystem.java:84)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:365)
at org.pentaho.platform.engine.core.system.PentahoSystem$1.call(PentahoSystem.java:362)
at org.pentaho.platform.engine.core.system.PentahoSystem.runAsSystem(PentahoSystem.java:413)
at org.pentaho.platform.engine.core.system.PentahoSystem.notifySystemListenersOfStartup(PentahoSystem.java:362)
... 16 more
Caused by: org.pentaho.platform.api.engine.PentahoSystemException: PentahoSystem.ERROR_0014 - Error while trying to execute startup sequence for org.pentaho.platform.osgi.OSGIBoot
at org.pentaho.platform.engine.core.system.PentahoSystem$2.call(PentahoSystem.java:444)
... 24 more
20:39:09,009 ERROR [Logger] Error end:
20:39:09,009 INFO [PeriodicStatusLogger] Warning, one or more errors occurred during the initialization process.
Pentaho BI Platform server failed to properly initialize. The system will not be available for requests. (pentaho-platform-core 7.1.0.0-12) Fully Qualified Server Url = http://localhost:8080/pentaho/, Solution Path = C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\pentaho-solutions
10-Jul-2018 20:39:29.970 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho has finished in 295,164 ms
10-Jul-2018 20:39:29.970 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho-style
10-Jul-2018 20:39:30.894 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:30.910 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\pentaho-style has finished in 940 ms
10-Jul-2018 20:39:30.910 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\ROOT
10-Jul-2018 20:39:31.640 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:31.656 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\ROOT has finished in 730 ms
10-Jul-2018 20:39:31.656 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\sw-style
10-Jul-2018 20:39:32.398 INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
10-Jul-2018 20:39:32.414 INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory C:\Program Files\Pentaho_BI\pentaho-server-ce-7.1.0.0-12\pentaho-server\tomcat\webapps\sw-style has finished in 758 ms
10-Jul-2018 20:39:32.445 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-apr-8080"]
10-Jul-2018 20:39:32.632 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["ajp-apr-8009"]
10-Jul-2018 20:39:32.632 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 298043 ms
I would appreciate anyone help in resolving my issue.

Android Studio 3.0 Gradle Build Failed

I’ve recently come across a problem with Android Studio 3.0 and Gradle builds. This wasn’t happening a few days ago. I keep getting the following Gradle build errors:
Error:java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:com.android.build.gradle.tasks.ResourceException: Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Error:java.lang.RuntimeException: No server to serve request. Check logs for details.
Stack trace throws the following information, but I’m not exactly sure where my problem is:
FAILURE: Build failed with an exception.
What went wrong:
Execution failed for task ‘:app:mergeDebugResources’.
Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
Try:
Run with --info or --debug option to get more log output.
Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ‘:app:mergeDebugResources’.
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:63)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:124)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:80)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:105)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:99)
at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625)
at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
Caused by: com.android.build.gradle.tasks.ResourceException: Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
at com.android.build.gradle.tasks.MergeResources.doFullTaskAction(MergeResources.java:269)
at com.android.build.gradle.internal.tasks.IncrementalTask.taskAction(IncrementalTask.java:109)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java:173)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:121)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:122)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)
… 27 more
Caused by: Error: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
at com.android.ide.common.res2.MergedResourceWriter.postWriteAction(MergedResourceWriter.java:622)
at com.android.ide.common.res2.MergeWriter.end(MergeWriter.java:46)
at com.android.ide.common.res2.MergedResourceWriter.end(MergedResourceWriter.java:238)
at com.android.ide.common.res2.DataMerger.mergeData(DataMerger.java:301)
at com.android.ide.common.res2.ResourceMerger.mergeData(ResourceMerger.java:412)
at com.android.build.gradle.tasks.MergeResources.doFullTaskAction(MergeResources.java:258)
… 39 more
Suppressed: java.lang.RuntimeException: No slave process to process jobs, aborting
at com.android.builder.tasks.WorkQueue.shutdown(WorkQueue.java:168)
at com.android.builder.internal.aapt.QueuedResourceProcessor.end(QueuedResourceProcessor.java:147)
at com.android.builder.internal.aapt.v2.QueueableAapt2.close(QueueableAapt2.java:117)
at com.android.build.gradle.tasks.MergeResources.doFullTaskAction(MergeResources.java:266)
at com.android.build.gradle.internal.tasks.IncrementalTask.taskAction(IncrementalTask.java:109)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$IncrementalTaskAction.doExecute(DefaultTaskClassInfoStore.java:173)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)
at org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:121)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:122)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:111)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:92)
at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:63)
at org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:197)
at org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:107)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:124)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:80)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:105)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:99)
at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:625)
at org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.executeWithTask(DefaultTaskExecutionPlan.java:580)
at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.run(DefaultTaskPlanExecutor.java:99)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:482)
at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:79)
at com.android.ide.common.res2.MergedResourceWriter.postWriteAction(MergedResourceWriter.java:593)
… 44 more
Caused by: java.util.concurrent.ExecutionException: java.lang.RuntimeException: No server to serve request. Check logs for details.
at com.google.common.util.concurrent.AbstractFuture.getDoneValue(AbstractFuture.java:503)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:462)
at com.google.common.util.concurrent.AbstractFuture$TrustedFuture.get(AbstractFuture.java:79)
at com.android.builder.internal.aapt.v2.QueueableAapt2.lambda$compile$0(QueueableAapt2.java:149)
Caused by: java.lang.RuntimeException: No server to serve request. Check logs for details.
at com.android.builder.tasks.WorkQueue.run(WorkQueue.java:236)
I have tried nearly every solution I’ve found (rebuilding/clean project). Even went so far as to do a complete Android Studio clean reinstall, but it seems the problem is not actually related to the Android Studio installation itself. Unless there is a cache of some sort that is hiding from me.
UPDATE:
Alright, so upon further testing, it seems like half the time I'll get the previous message, but the other half the compile process gets stuck on an endless loop with the following debug output (which keeps repeating itself until I cancel the build):
22:18:17.169 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
22:18:17.169 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
22:18:17.169 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
22:18:17.169 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Waiting to acquire shared lock on daemon addresses registry.
22:18:17.169 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Lock acquired on daemon addresses registry.
22:18:17.170 [DEBUG] [org.gradle.cache.internal.DefaultFileLockManager] Releasing lock on daemon addresses registry.
22:18:20.368 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 34292412416, Free: 23154110464}
22:18:20.368 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 34292412416, Free: 23154110464}
22:18:20.368 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 1431830528, Committed: 754974720}
22:18:25.367 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting OS memory status event {Total: 34292412416, Free: 23159189504}
22:18:25.367 [DEBUG] [org.gradle.launcher.daemon.server.health.LowMemoryDaemonExpirationStrategy] Received memory status update: {Total: 34292412416, Free: 23159189504}
22:18:25.367 [DEBUG] [org.gradle.process.internal.health.memory.MemoryManager] Emitting JVM memory status event {Maximum: 1431830528, Committed: 754974720}
22:18:27.168 [DEBUG] [org.gradle.launcher.daemon.server.Daemon] DaemonExpirationPeriodicCheck running
(Posted on behalf of the question author).
I had to pull the trigger since I have work to get to, so I went ahead and made a clean reinstall of Windows. That fixed the issue.
Seems like I was right about some files being kept in another place, whose location I don't know. This is pretty much proven by the huge difference in install times between clean OS and a simple reinstall on an OS that already had Android Studio installed previously.

jboss7 upgrade + seam + jsf Configuration Failed error on deployment

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

Resources