[JBoss JIRA] (WFLY-3207) ContextNotActiveException: WELD-001303: No active contexts for scope type javax.faces.flow.builder.FlowDefinition on reload
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-3207?page=com.atlassian.jira.plugin.... ]
Farah Juma commented on WFLY-3207:
----------------------------------
Please attach a reproducer app (just tried reproducing this but I wasn't able to).
> 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
11 years, 8 months
[JBoss JIRA] (WFLY-3209) CLI NullPointerException for Ctrl+D when prompted for username.
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-3209:
--------------------------------------
Summary: CLI NullPointerException for Ctrl+D when prompted for username.
Key: WFLY-3209
URL: https://issues.jboss.org/browse/WFLY-3209
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CLI
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 9.0.0.CR1
{code}
[standalone@localhost:9990 /] [darranl@localhost bin]$ ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
Username: java.lang.NullPointerException
at org.jboss.aesh.console.Console.pushToStdOut(Console.java:227)
at org.jboss.as.cli.impl.Console$Factory$1.print(Console.java:160)
at org.jboss.as.cli.impl.CommandContextImpl.printLine(CommandContextImpl.java:704)
at org.jboss.as.cli.impl.CommandContextImpl.error(CommandContextImpl.java:722)
at org.jboss.as.cli.impl.CommandContextImpl.handleSafe(CommandContextImpl.java:647)
at org.jboss.as.cli.impl.CommandContextImpl.interact(CommandContextImpl.java:1272)
at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:254)
at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.modules.Module.run(Module.java:312)
at org.jboss.modules.Main.main(Main.java:460)
{code}
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-3198) Reenabling an application prevents it from deployement after a restart
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-3198?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-3198:
----------------------------------------
A thought for future improvement (not required to resolve this issue):
We should look into using the management API notification stuff Jeff Mesnil has done/is doing. The scanner subsystem can register listeners and the deployment ops can emit events. This can be used to keep the scanner aware of changes to the deployments part of the management model independent of the periodic scans.
This would close a gap that exists where the scan could be configured to run infrequently (say 10 mins), the .undeployed app gets deployed via console, and then before the scanner runs again and cleans out the .undeployed, the server is reloaded/restarted.
> Reenabling an application prevents it from deployement after a restart
> ----------------------------------------------------------------------
>
> Key: WFLY-3198
> URL: https://issues.jboss.org/browse/WFLY-3198
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ConfigAdmin
> Affects Versions: 8.0.0.Final
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
>
> After disabling and then re-enabling the application, I don't see Application.war.deployed; I still see Application.war.undeployed.
> That explains why it doesn't get deployed after restart.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-3208) Revisit error message for an authentication failure.
by Darran Lofthouse (JIRA)
Darran Lofthouse created WFLY-3208:
--------------------------------------
Summary: Revisit error message for an authentication failure.
Key: WFLY-3208
URL: https://issues.jboss.org/browse/WFLY-3208
Project: WildFly
Issue Type: Task
Security Level: Public (Everyone can see)
Components: CLI, Domain Management, Remoting, Security
Affects Versions: 8.0.0.Final
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 9.0.0.CR1
After authentication fails in the CLI the following error message is output: -
{code}
Unable to authenticate against controller at localhost:9990: Authentication failed: the server presented no authentication mechanisms
{code}
This text is a bit misleading, what it actually means is all mechanisms presented have either been excluded or attempted and now no further mechanisms are available to try.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-3205) For xa-datasource testConnection should account for deployment classloader
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/WFLY-3205?page=com.atlassian.jira.plugin.... ]
Jesper Pedersen reassigned WFLY-3205:
-------------------------------------
Assignee: Stefano Maestri (was: Jesper Pedersen)
> For xa-datasource testConnection should account for deployment classloader
> --------------------------------------------------------------------------
>
> Key: WFLY-3205
> URL: https://issues.jboss.org/browse/WFLY-3205
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCA
> Affects Versions: 8.0.1.Final
> Environment: All
> Reporter: Jay Kumar SenSharma
> Assignee: Stefano Maestri
>
> - The fix mentioned in https://issues.jboss.org/browse/WFLY-2047 is resolves the issue for plain Non-XA dataSources. However if an XA-DataSource is configured with the "ldap" based database connection URL then it fails with the following Error:
> {code}
> 13:49:41,399 ERROR [org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl] (Periodic Recovery) IJ000906: Error during crash recovery: java:/OracleXA_DS (Could not create connection): javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:461)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.createManagedConnection(XAManagedConnectionFactory.java:398)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.open(XAResourceRecoveryImpl.java:343)
> at org.jboss.jca.core.tx.jbossts.XAResourceRecoveryImpl.getXAResources(XAResourceRecoveryImpl.java:170)
> at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.resourceInitiatedRecoveryForRecoveryHelpers(XARecoveryModule.java:516) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:743) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> at com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:371) [narayana-jts-jacorb-5.0.0.Final.jar:5.0.0.Final (revision: 9aa71)]
> Caused by: java.sql.SQLRecoverableException: Io exception: JNDI Package failurejavax.naming.NamingException: JBAS011843: Failed instantiate InitialContextFactory com.sun.jndi.ldap.LdapCtxFactory from classloader ModuleClassLoader for Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base)) [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.ldap.LdapCtxFactory from [Module "org.jboss.jts:main" from local module loader @3b70c (finder: local module finder @1e6a820 (roots: /home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules,/home/userone/XA_DS/wildfly-8.0.1.Final-SNAPSHOT/modules/system/layers/base))]]
> at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:101)
> at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:112)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:173)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:229)
> at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:458)
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:411)
> at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:490)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:202)
> at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:33)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:474)
> at oracle.jdbc.pool.OracleDataSource.getPhysicalConnection(OracleDataSource.java:275)
> at oracle.jdbc.xa.client.OracleXADataSource.getPooledConnection(OracleXADataSource.java:454)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:159)
> at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:130)
> at org.jboss.jca.adapters.jdbc.xa.XAManagedConnectionFactory.getXAManagedConnection(XAManagedConnectionFactory.java:444)
> ... 8 morec
> {code}
> - The XA dataSource configuration looks like following:
> {code}
> <subsystem xmlns="urn:jboss:domain:datasources:2.0">
> <datasources>
> <xa-datasource jndi-name="java:/OracleXA_DS" pool-name="OracleXA_DS" enabled="true">
> <xa-datasource-property name="ServerName">
> example.com
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> TestDB
> </xa-datasource-property>
> <xa-datasource-property name="URL">
> jdbc:oracle:thin:@ldap://example.com:3060/test,cn=OracleA,dc=worldA
> </xa-datasource-property>
> <xa-datasource-class>oracle.jdbc.xa.client.OracleXADataSource</xa-datasource-class>
> <driver>oracle</driver>
> <security>
> <user-name>jboss</user-name>
> <password>jboss</password>
> </security>
> </xa-datasource>
> <drivers>
> <driver name="oracle" module="com.oracle.jdbc6"/>
> </drivers>
> </datasources>
> </subsystem>
> {code}
> - When the above datasource is tested via CLI like following then aht above mentioned error is noticed:
> {code}
> /subsystem=datasources/xa-data-source=OracleXA_DS:test-connection-in-pool
> {code}
--
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
11 years, 8 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)
Radoslav Husar created WFLY-3207:
------------------------------------
Summary: 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
11 years, 8 months
[JBoss JIRA] (WFLY-951) It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-951?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson commented on WFLY-951:
------------------------------------
I think we should expose this via the subsystem configuration. [~maeste], are you OK to take a look at it for us please?
> It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
> -----------------------------------------------------------------
>
> Key: WFLY-951
> URL: https://issues.jboss.org/browse/WFLY-951
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transactions
> Environment: JBoss EAP 6.01
> Reporter: Tom Ross
> Assignee: Stefano Maestri
>
> It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below:
> {noformat}
> <system-properties>
> <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner\\s+com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/>
> </system-properties>
> {noformat}
> Unfortunately the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no easy way of removing transaction manager debris from object store.
--
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
11 years, 8 months
[JBoss JIRA] (WFLY-951) It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
by Tom Jenkinson (JIRA)
[ https://issues.jboss.org/browse/WFLY-951?page=com.atlassian.jira.plugin.s... ]
Tom Jenkinson updated WFLY-951:
-------------------------------
Assignee: Stefano Maestri (was: Amos Feng)
> It is not possible to enable AtomicActionExpiryScanner in EAP 6.x
> -----------------------------------------------------------------
>
> Key: WFLY-951
> URL: https://issues.jboss.org/browse/WFLY-951
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transactions
> Environment: JBoss EAP 6.01
> Reporter: Tom Ross
> Assignee: Stefano Maestri
>
> It should be possible to add AtomicActionExpiryScanner to the EAP 6 configuration as outline below:
> {noformat}
> <system-properties>
> <property name="RecoveryEnvironmentBean.expiryScannerClassNames" value="com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner\\s+com.arjuna.ats.internal.arjuna.recovery.AtomicActionExpiryScanner"/>
> </system-properties>
> {noformat}
> Unfortunately the value of the RecoveryEnvironmentBean.expiryScannerClassNames seems to be overwritten in the ArjunaRecoveryManagerService class. As a result there is no easy way of removing transaction manager debris from object store.
--
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
11 years, 8 months