[JBoss JIRA] (WFLY-3207) ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3207?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-3207:
--------------------------------------
Seems like a [lot of people ran into the issue|https://www.google.com/search?q=No+active+contexts+for+scope+type+j...] but I couldn't see any Jira report.
> ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3207
> URL: https://issues.jboss.org/browse/WFLY-3207
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Farah Juma
>
> Deploy JSF application and reload the server (:reload from CLI).
> {noformat}
> 14:07:53,201 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.6.jar:2.2.6]
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> 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:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> 14:07:53,208 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:218)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> ... 3 more
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189)
> ... 7 more
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303)
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108)
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187)
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163)
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296)
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294)
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253)
> ... 9 more
> 14:07:53,437 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/translator'
> 14:07:53,542 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/clusterbench'
> 14:07:53,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: /clusterbench
> 14:07:54,448 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /translator
> 14:07:54,456 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "clusterbench-ee7.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./clusterbench-passivating" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition"}}
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "translator.war" (runtime-name : "translator.war")
> 14:07:54,477 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> 14:07:54,489 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 14:07:54,493 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 14:07:54,493 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.1.Final-SNAPSHOT "WildFly" started (with errors) in 4618ms - Started 843 of 957 services (3 services failed or missing dependencies, 243 services are lazy, passive or on-demand)
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /clusterbench
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017535: Unregistered web context: /clusterbench-granular
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,712 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000029: Passivating all entries to disk
> 14:07:54,713 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,721 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar cache from ejb container
> 14:07:54,722 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) JBAS010282: Stopped default-host/clusterbench-passivating cache from web container
> 14:07:54,724 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) JBAS010282: Stopped default-host/clusterbench-granular cache from web container
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,737 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment clusterbench-ee7.ear
> 14:07:54,739 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped default-host/clusterbench cache from web container
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war) in 58ms
> 14:07:54,758 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war) in 60ms
> 14:07:54,759 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 61ms
> 14:07:54,852 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "clusterbench-ee7.ear" (runtime-name: "clusterbench-ee7.ear")
> 14:07:54,853 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacesServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."org.jboss.test.clusterbench.web.session.GranularHttpSessionServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3207) ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3207?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-3207:
--------------------------------------
Really just https://github.com/clusterbench/clusterbench does the job -- build it, deploy to server, connect via CLI and do :reload.
> ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3207
> URL: https://issues.jboss.org/browse/WFLY-3207
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Farah Juma
>
> Deploy JSF application and reload the server (:reload from CLI).
> {noformat}
> 14:07:53,201 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.6.jar:2.2.6]
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> 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:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> 14:07:53,208 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:218)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> ... 3 more
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189)
> ... 7 more
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303)
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108)
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187)
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163)
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296)
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294)
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253)
> ... 9 more
> 14:07:53,437 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/translator'
> 14:07:53,542 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/clusterbench'
> 14:07:53,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: /clusterbench
> 14:07:54,448 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /translator
> 14:07:54,456 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "clusterbench-ee7.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./clusterbench-passivating" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition"}}
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "translator.war" (runtime-name : "translator.war")
> 14:07:54,477 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> 14:07:54,489 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 14:07:54,493 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 14:07:54,493 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.1.Final-SNAPSHOT "WildFly" started (with errors) in 4618ms - Started 843 of 957 services (3 services failed or missing dependencies, 243 services are lazy, passive or on-demand)
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /clusterbench
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017535: Unregistered web context: /clusterbench-granular
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,712 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000029: Passivating all entries to disk
> 14:07:54,713 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,721 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar cache from ejb container
> 14:07:54,722 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) JBAS010282: Stopped default-host/clusterbench-passivating cache from web container
> 14:07:54,724 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) JBAS010282: Stopped default-host/clusterbench-granular cache from web container
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,737 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment clusterbench-ee7.ear
> 14:07:54,739 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped default-host/clusterbench cache from web container
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war) in 58ms
> 14:07:54,758 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war) in 60ms
> 14:07:54,759 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 61ms
> 14:07:54,852 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "clusterbench-ee7.ear" (runtime-name: "clusterbench-ee7.ear")
> 14:07:54,853 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacesServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."org.jboss.test.clusterbench.web.session.GranularHttpSessionServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3207) ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-3207?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-3207 at 4/2/14 11:18 AM:
---------------------------------------------------------------
Really just https://github.com/clusterbench/clusterbench does the job on WildFly master -- build it, deploy to server, connect via CLI and do :reload.
was (Author: rhusar):
Really just https://github.com/clusterbench/clusterbench does the job -- build it, deploy to server, connect via CLI and do :reload.
> ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-3207
> URL: https://issues.jboss.org/browse/WFLY-3207
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JSF
> Affects Versions: 8.0.0.Final
> Reporter: Radoslav Husar
> Assignee: Farah Juma
>
> Deploy JSF application and reload the server (:reload from CLI).
> {noformat}
> 14:07:53,201 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181) [weld-core-impl-2.1.2.Final.jar:2014-01-09 09:23]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108) [jboss-jsf-api_2.2_spec-2.2.6.jar:2.2.6]
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294) [wildfly-jsf-injection-8.0.1.Final-SNAPSHOT.jar:8.0.1.Final-SNAPSHOT]
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253) [jsf-impl-2.2.6-jbossorg-2.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189) [undertow-servlet-1.0.3.Final.jar:1.0.3.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> 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:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> 14:07:53,208 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0]
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:218)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:86)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:71)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.1.Final.jar:1.2.1.Final]
> ... 3 more
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:273)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:189)
> ... 7 more
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> at org.jboss.weld.manager.BeanManagerImpl.getContext(BeanManagerImpl.java:680)
> at org.jboss.weld.util.ForwardingBeanManager.getContext(ForwardingBeanManager.java:181)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.loadFlows(ApplicationAssociate.java:323)
> at com.sun.faces.application.ApplicationAssociate$PostConstructApplicationListener.processEvent(ApplicationAssociate.java:303)
> at javax.faces.event.SystemEvent.processListener(SystemEvent.java:108)
> at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2187)
> at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2163)
> at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:296)
> at org.jboss.as.jsf.injection.weld.ForwardingApplication.publishEvent(ForwardingApplication.java:294)
> at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:692)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:253)
> ... 9 more
> 14:07:53,437 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-1) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/translator'
> 14:07:53,542 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.6-jbossorg-2 20140318-1712 for context '/clusterbench'
> 14:07:53,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) JBAS017534: Registered web context: /clusterbench
> 14:07:54,448 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017534: Registered web context: /translator
> 14:07:54,456 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "clusterbench-ee7.ear")]) - failure description: {"JBAS014671: Failed services" => {"jboss.undertow.deployment.default-server.default-host./clusterbench-passivating" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: java.lang.RuntimeException: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition
> Caused by: org.jboss.weld.context.ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition"}}
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "clusterbench-ee7.ear" (runtime-name : "clusterbench-ee7.ear")
> 14:07:54,475 INFO [org.jboss.as.server] (ServerService Thread Pool -- 31) JBAS018559: Deployed "translator.war" (runtime-name : "translator.war")
> 14:07:54,477 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating: Failed to start service
> 14:07:54,489 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
> 14:07:54,493 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
> 14:07:54,493 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.0.1.Final-SNAPSHOT "WildFly" started (with errors) in 4618ms - Started 843 of 957 services (3 services failed or missing dependencies, 243 services are lazy, passive or on-demand)
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017535: Unregistered web context: /clusterbench
> 14:07:54,704 INFO [org.wildfly.extension.undertow] (MSC service thread 1-8) JBAS017535: Unregistered web context: /clusterbench-granular
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,707 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to obtain InjectionProvider from init time FacesContext. Does this container implement the Mojarra Injection SPI?
> 14:07:54,709 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 28) ISPN000030: Passivated 0 entries in 1 milliseconds
> 14:07:54,709 SEVERE [javax.faces] (MSC service thread 1-8) Unable to call @PreDestroy annotated methods because no InjectionProvider can be found. Does this container implement the Mojarra Injection SPI?
> 14:07:54,712 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000029: Passivating all entries to disk
> 14:07:54,713 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 21) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,721 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped clusterbench-ee7.ear/clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar cache from ejb container
> 14:07:54,722 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 28) JBAS010282: Stopped default-host/clusterbench-passivating cache from web container
> 14:07:54,724 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 21) JBAS010282: Stopped default-host/clusterbench-granular cache from web container
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000029: Passivating all entries to disk
> 14:07:54,728 INFO [org.infinispan.eviction.PassivationManagerImpl] (ServerService Thread Pool -- 27) ISPN000030: Passivated 0 entries in 0 milliseconds
> 14:07:54,737 INFO [org.jboss.weld.deployer] (MSC service thread 1-4) JBAS016009: Stopping weld service for deployment clusterbench-ee7.ear
> 14:07:54,739 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 27) JBAS010282: Stopped default-host/clusterbench cache from web container
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar) in 57ms
> 14:07:54,755 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war) in 58ms
> 14:07:54,758 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015974: Stopped subdeployment (runtime-name: clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war) in 60ms
> 14:07:54,759 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment clusterbench-ee7.ear (runtime-name: clusterbench-ee7.ear) in 61ms
> 14:07:54,852 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018558: Undeployed "clusterbench-ee7.ear" (runtime-name: "clusterbench-ee7.ear")
> 14:07:54,853 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-ejb-1.1.0-SNAPSHOT.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-default.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-granular.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacesServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".component."org.jboss.test.clusterbench.web.session.GranularHttpSessionServlet".START (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."clusterbench-ee7.ear".deploymentCompleteService]
> service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating (missing) dependents: [service jboss.deployment.subunit."clusterbench-ee7.ear"."clusterbench-ee7-web-1.1.0-SNAPSHOT-passivating.war".deploymentCompleteService]
> JBAS014777: Services which failed to start: service jboss.undertow.deployment.default-server.default-host./clusterbench-passivating
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (WFLY-3211) java:app resources can not be shared between ejb and appclient modules
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-3211:
---------------------------------
Summary: java:app resources can not be shared between ejb and appclient modules
Key: WFLY-3211
URL: https://issues.jboss.org/browse/WFLY-3211
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Naming
Affects Versions: 8.0.0.Final
Reporter: Jeff Mesnil
Assignee: Eduardo Martins
use case:
1 ear composed of:
1 appclient module that defines 2 JMS queues (one in java:app, the other in java:global)
1 ejb modules with 2 MDBs (one listening to the java:app queue and the other to the java:global queue)
When the ear is deployed:
1. the ejb module is deployed, the MDBs are created and wait for the creations of their respective queues (defined in the appclient module)
2. the appclient module is deployed, its 2 queues are deployed
3. the appclient main is run
When the appclient uses the java:global queue, it looks it up, sends the message and the corresponding MDB receives it fine.
When the appclient uses the java:app queue, it looks it up, sends the message but the corresponding MDB never receives it
=> the MDB was never deployed because it did not see the java:app queue deployed from the appclient module.
Note that if I move the destination definitions to the ejb module, the MDBs are correctly activated but the appclient module is no longer deployed with errors:
{noformat}
[APPCLIENT-out] {"JBAS014771: Services with missing/unavailable dependencies" => [
[APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInGlobal is missing [jboss.naming.context.java.global.jms.queu
e.queue1]",
[APPCLIENT-out] "jboss.naming.context.java.module.simple-jms-appclient-test.appclient.env.jms.queueInApp is missing [jboss.naming.context.java.app.simple-jms-app
client-test.jms.queue.queue2]"
[APPCLIENT-out] ]}
{noformat}
Steps to reproduce:
1. fetch git branch https://github.com/jmesnil/wildfly/tree/jms_appclient
2. build WildFly
3. run ./integration-tests.sh -Dts.basic -Dtest=org.jboss.as.test.integration.ee.appclient.jms.basic.SimpleJMSApplicationClientTestCase -DnoWebProfile
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1821) SEQUENCER2: new impl of total order protocol
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1821?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1821:
--------------------------------
First impl is on branch {{JGRP-1821}}
> SEQUENCER2: new impl of total order protocol
> --------------------------------------------
>
> Key: JGRP-1821
> URL: https://issues.jboss.org/browse/JGRP-1821
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.5
>
>
> When in {{SEQUENCER}} a member P wants to send a multicast message M, it unicasts it to the coordinator, who multicasts it on behalf of P.
> The new impl {{SEQUENCER2}} is different:
> * P asks the coord for a seqno
> * The coord responds with a (monotonically increasing) seqno
> * P multicasts M with that seqno
> * Everyone uses one global {{Table}} to deliver messages and weed out duplicates
> Advantages:
> # A sender sends messages itself, so the sequencer doesn't need to do sending (and potential retransmissions)
> # Compared to {{SEQUENCER}}, the data is only sent and marshalled once (better for large messages)
> # A sender grabs entire ranges of seqnos, so this should be efficient
> The edge case handling though requires some work, e.g.
> * A member B crashes after having received a seqno (e.g. 4)
> ** The sequencer will give out 5 next, but since nobody received 4, all subsequent messages will get stuck, waiting for 4
> * The sequencer (coord) dies or leaves
> ** The next-in-line probably needs to run some reconciliation protocol, asking all members for their highest received seqnos
> ** Messages like 4 would get marked as dummy, removed from table and dropped
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months
[JBoss JIRA] (JGRP-1821) SEQUENCER2: new impl of total order protocol
by Bela Ban (JIRA)
Bela Ban created JGRP-1821:
------------------------------
Summary: SEQUENCER2: new impl of total order protocol
Key: JGRP-1821
URL: https://issues.jboss.org/browse/JGRP-1821
Project: JGroups
Issue Type: Feature Request
Reporter: Bela Ban
Assignee: Bela Ban
Fix For: 3.5
When in {{SEQUENCER}} a member P wants to send a multicast message M, it unicasts it to the coordinator, who multicasts it on behalf of P.
The new impl {{SEQUENCER2}} is different:
* P asks the coord for a seqno
* The coord responds with a (monotonically increasing) seqno
* P multicasts M with that seqno
* Everyone uses one global {{Table}} to deliver messages and weed out duplicates
Advantages:
# A sender sends messages itself, so the sequencer doesn't need to do sending (and potential retransmissions)
# Compared to {{SEQUENCER}}, the data is only sent and marshalled once (better for large messages)
# A sender grabs entire ranges of seqnos, so this should be efficient
The edge case handling though requires some work, e.g.
* A member B crashes after having received a seqno (e.g. 4)
** The sequencer will give out 5 next, but since nobody received 4, all subsequent messages will get stuck, waiting for 4
* The sequencer (coord) dies or leaves
** The next-in-line probably needs to run some reconciliation protocol, asking all members for their highest received seqnos
** Messages like 4 would get marked as dummy, removed from table and dropped
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months