[JBoss JIRA] (WFLY-4160) ConcurrentModificationException while deploy JSF application (8.2.0)
by Devendra Bargujar (JIRA)
[ https://issues.jboss.org/browse/WFLY-4160?page=com.atlassian.jira.plugin.... ]
Devendra Bargujar updated WFLY-4160:
------------------------------------
Description:
While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
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_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
Caused by: java.lang.NullPointerException
at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:77) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:170) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:866) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:327) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:410) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:251) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:437) [jsf-impl-2.2.8-jbossorg-1.jar:]
... 10 more
was:
While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
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_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
> ConcurrentModificationException while deploy JSF application (8.2.0)
> --------------------------------------------------------------------
>
> Key: WFLY-4160
> URL: https://issues.jboss.org/browse/WFLY-4160
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: WildFly (8.2.0 - Final)
> Reporter: Devendra Bargujar
> Assignee: Farah Juma
> Labels: new_and_noteworthy
>
> While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
> 11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
> 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_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
> Caused by: java.lang.NullPointerException
> at com.sun.faces.facelets.impl.DefaultResourceResolver.resolveUrl(DefaultResourceResolver.java:77) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.facelets.impl.DefaultFaceletFactory.init(DefaultFaceletFactory.java:170) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.ApplicationAssociate.createFaceletFactory(ApplicationAssociate.java:866) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.ApplicationAssociate.initializeFacelets(ApplicationAssociate.java:327) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.ApplicationAssociate.getCompiler(ApplicationAssociate.java:410) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:251) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:437) [jsf-impl-2.2.8-jbossorg-1.jar:]
> ... 10 more
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFLY-4160) ConcurrentModificationException while deploy JSF application (8.2.0)
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-4160?page=com.atlassian.jira.plugin.... ]
Farah Juma updated WFLY-4160:
-----------------------------
Priority: Major (was: Blocker)
> ConcurrentModificationException while deploy JSF application (8.2.0)
> --------------------------------------------------------------------
>
> Key: WFLY-4160
> URL: https://issues.jboss.org/browse/WFLY-4160
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: WildFly (8.2.0 - Final)
> Reporter: Devendra Bargujar
> Assignee: Farah Juma
> Labels: new_and_noteworthy
>
> While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
> 11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
> 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_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFLY-4160) ConcurrentModificationException while deploy JSF application (8.2.0)
by Farah Juma (JIRA)
[ https://issues.jboss.org/browse/WFLY-4160?page=com.atlassian.jira.plugin.... ]
Farah Juma updated WFLY-4160:
-----------------------------
Fix Version/s: (was: 8.2.0.Final)
> ConcurrentModificationException while deploy JSF application (8.2.0)
> --------------------------------------------------------------------
>
> Key: WFLY-4160
> URL: https://issues.jboss.org/browse/WFLY-4160
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: WildFly (8.2.0 - Final)
> Reporter: Devendra Bargujar
> Assignee: Farah Juma
> Priority: Blocker
> Labels: new_and_noteworthy
>
> While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
> 11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
> 11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
> 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_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Caused by: java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
> at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
> at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFLY-4160) ConcurrentModificationException while deploy JSF application (8.2.0)
by Devendra Bargujar (JIRA)
Devendra Bargujar created WFLY-4160:
---------------------------------------
Summary: ConcurrentModificationException while deploy JSF application (8.2.0)
Key: WFLY-4160
URL: https://issues.jboss.org/browse/WFLY-4160
Project: WildFly
Issue Type: Bug
Components: JSF
Affects Versions: 8.2.0.Final
Environment: WildFly (8.2.0 - Final)
Reporter: Devendra Bargujar
Assignee: Farah Juma
Priority: Blocker
Fix For: 8.2.0.Final
While deploying 2 JSF application getting ConcurrentModificationException on NavigationHandlerImpl$NavigationMap$. App also uses seam 3.1.0. Please refer below stack trace.
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/com'
11:57:21,898 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-6) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/sof'
11:57:26,218 SEVERE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-2) Critical error during deployment: : com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! null
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:449) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:221) [jsf-impl-2.2.8-jbossorg-1.jar:]
at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:173) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:193) [undertow-servlet-1.1.0.Final.jar:1.1.0.Final]
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:87)
at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:72)
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_25]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
Caused by: java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(HashMap.java:1429) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1463) [rt.jar:1.8.0_25]
at java.util.HashMap$EntryIterator.next(HashMap.java:1461) [rt.jar:1.8.0_25]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1523) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.application.NavigationHandlerImpl$NavigationMap$4$1.next(NavigationHandlerImpl.java:1511) [jsf-impl-2.2.8-jbossorg-1.jar:]
at java.util.AbstractMap.get(AbstractMap.java:185) [rt.jar:1.8.0_25]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationCasesForRule(NavigationConfigProcessor.java:323) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.addNavigationRules(NavigationConfigProcessor.java:224) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.NavigationConfigProcessor.process(NavigationConfigProcessor.java:167) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.RenderKitConfigProcessor.process(RenderKitConfigProcessor.java:196) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ManagedBeanConfigProcessor.process(ManagedBeanConfigProcessor.java:270) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ValidatorConfigProcessor.process(ValidatorConfigProcessor.java:120) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ConverterConfigProcessor.process(ConverterConfigProcessor.java:126) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ComponentConfigProcessor.process(ComponentConfigProcessor.java:117) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:344) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:152) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:239) [jsf-impl-2.2.8-jbossorg-1.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:435) [jsf-impl-2.2.8-jbossorg-1.jar:]
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-208) Expose 'singleton' type information in read-children-types
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-208?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFCORE-208:
-------------------------------------
Affects Version/s: 1.0.0.Alpha13
> Expose 'singleton' type information in read-children-types
> ----------------------------------------------------------
>
> Key: WFCORE-208
> URL: https://issues.jboss.org/browse/WFCORE-208
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha13
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Fix For: 1.0.0.Beta1
>
>
> Management clients need a mechanism to disambiguate between cases where a management resource registration exists for a a wildcard PathElement (e.g. PathElement.pathElement("service"), represented in CLI syntax as service=*) versus for a fully specified PathElement (e.g. PathElement.pathElement("service", "remote"), represented as service=remote). In the fully specified case they need to be able to see the full path element when querying for types using the read-children-types operation.
> The term we have reached consensus on for describing registrations against a non-wildcard PathElement is a 'singleton'. The registration represents a type, and since within the context of its parent only one address will be valid for that type, that type has a singleton nature.
> The task here is to add a new boolean parameter to the read-children-types operation, "include-singletons". The parameter will be optional, default value of 'false', which will result in unchanged default behavior from what exists in WF 8.x and earlier.
> If the "include-singletons" parameter is set to "true", the operation result will include the full key/value pair for any singleton registration. So, if a parent registration had children registered under "service=remote" and "service=async", the result for the existing operation would be:
> {code}
> "result"=> ["service"]
> {code}
> If the "include-singletons" parameter was set to 'true' it would be:
> {code}
> "result"=> ["service=remote", "service=async"]
> {code}
> Note that the elements in the above result list are not ModelType.PROPERTY. They are STRING. The result type for read-children-types is always LIST of STRING.
> The '=' char is illegal in the key portion of a PathElement, so a client invoking read-children-types can safely assume that the presence of an '=' char in an element in the result denotes a singleton type, and that the first such char in any element represents the end of the 'key' portion of the registration's PathElement and the portion after that first char represents the value portion of the PathElement.
> Note also that there is no simple element "service" in the above result. *If "include-singletons" is "true" a non-fully-qualified type (i.e. just key instead of key=value) will only appear in the result if there is a wildcard registration for that key.*
> However, it is possible to have both "key" and one or more "key=xxx" in the same result. This can occur in the case of override registrations, for example what we use with datasources. There is a base type for datasources, but then additional datasource-specific registrations get added to support exposing additional vendor-specific metrics. In such situations, the response with "include-singletons=true" will look like this:
> {code}
> "result"=> ["datasource", "datasource=ExampleDS"]
> {code}
> A client that sees both "key" and "key=xxx" in a result can safely assume that "key=xxx" represents an override registration, overriding the basic type registered under "key=*".
> Note there is no guarantee as to ordering in the list, i.e. the above example could also look like this:
> {code}
> "result"=> ["datasource=ExampleDS", "datasource"]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-208) Expose 'singleton' type information in read-children-types
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-208?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFCORE-208:
-------------------------------------
Fix Version/s: 1.0.0.Alpha14
> Expose 'singleton' type information in read-children-types
> ----------------------------------------------------------
>
> Key: WFCORE-208
> URL: https://issues.jboss.org/browse/WFCORE-208
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha13
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Fix For: 1.0.0.Alpha14, 1.0.0.Beta1
>
>
> Management clients need a mechanism to disambiguate between cases where a management resource registration exists for a a wildcard PathElement (e.g. PathElement.pathElement("service"), represented in CLI syntax as service=*) versus for a fully specified PathElement (e.g. PathElement.pathElement("service", "remote"), represented as service=remote). In the fully specified case they need to be able to see the full path element when querying for types using the read-children-types operation.
> The term we have reached consensus on for describing registrations against a non-wildcard PathElement is a 'singleton'. The registration represents a type, and since within the context of its parent only one address will be valid for that type, that type has a singleton nature.
> The task here is to add a new boolean parameter to the read-children-types operation, "include-singletons". The parameter will be optional, default value of 'false', which will result in unchanged default behavior from what exists in WF 8.x and earlier.
> If the "include-singletons" parameter is set to "true", the operation result will include the full key/value pair for any singleton registration. So, if a parent registration had children registered under "service=remote" and "service=async", the result for the existing operation would be:
> {code}
> "result"=> ["service"]
> {code}
> If the "include-singletons" parameter was set to 'true' it would be:
> {code}
> "result"=> ["service=remote", "service=async"]
> {code}
> Note that the elements in the above result list are not ModelType.PROPERTY. They are STRING. The result type for read-children-types is always LIST of STRING.
> The '=' char is illegal in the key portion of a PathElement, so a client invoking read-children-types can safely assume that the presence of an '=' char in an element in the result denotes a singleton type, and that the first such char in any element represents the end of the 'key' portion of the registration's PathElement and the portion after that first char represents the value portion of the PathElement.
> Note also that there is no simple element "service" in the above result. *If "include-singletons" is "true" a non-fully-qualified type (i.e. just key instead of key=value) will only appear in the result if there is a wildcard registration for that key.*
> However, it is possible to have both "key" and one or more "key=xxx" in the same result. This can occur in the case of override registrations, for example what we use with datasources. There is a base type for datasources, but then additional datasource-specific registrations get added to support exposing additional vendor-specific metrics. In such situations, the response with "include-singletons=true" will look like this:
> {code}
> "result"=> ["datasource", "datasource=ExampleDS"]
> {code}
> A client that sees both "key" and "key=xxx" in a result can safely assume that "key=xxx" represents an override registration, overriding the basic type registered under "key=*".
> Note there is no guarantee as to ordering in the list, i.e. the above example could also look like this:
> {code}
> "result"=> ["datasource=ExampleDS", "datasource"]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFCORE-208) Expose 'singleton' type information in read-children-types
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-208?page=com.atlassian.jira.plugin... ]
Emmanuel Hugonnet updated WFCORE-208:
-------------------------------------
Fix Version/s: (was: 1.0.0.Beta1)
> Expose 'singleton' type information in read-children-types
> ----------------------------------------------------------
>
> Key: WFCORE-208
> URL: https://issues.jboss.org/browse/WFCORE-208
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 1.0.0.Alpha13
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Fix For: 1.0.0.Alpha14
>
>
> Management clients need a mechanism to disambiguate between cases where a management resource registration exists for a a wildcard PathElement (e.g. PathElement.pathElement("service"), represented in CLI syntax as service=*) versus for a fully specified PathElement (e.g. PathElement.pathElement("service", "remote"), represented as service=remote). In the fully specified case they need to be able to see the full path element when querying for types using the read-children-types operation.
> The term we have reached consensus on for describing registrations against a non-wildcard PathElement is a 'singleton'. The registration represents a type, and since within the context of its parent only one address will be valid for that type, that type has a singleton nature.
> The task here is to add a new boolean parameter to the read-children-types operation, "include-singletons". The parameter will be optional, default value of 'false', which will result in unchanged default behavior from what exists in WF 8.x and earlier.
> If the "include-singletons" parameter is set to "true", the operation result will include the full key/value pair for any singleton registration. So, if a parent registration had children registered under "service=remote" and "service=async", the result for the existing operation would be:
> {code}
> "result"=> ["service"]
> {code}
> If the "include-singletons" parameter was set to 'true' it would be:
> {code}
> "result"=> ["service=remote", "service=async"]
> {code}
> Note that the elements in the above result list are not ModelType.PROPERTY. They are STRING. The result type for read-children-types is always LIST of STRING.
> The '=' char is illegal in the key portion of a PathElement, so a client invoking read-children-types can safely assume that the presence of an '=' char in an element in the result denotes a singleton type, and that the first such char in any element represents the end of the 'key' portion of the registration's PathElement and the portion after that first char represents the value portion of the PathElement.
> Note also that there is no simple element "service" in the above result. *If "include-singletons" is "true" a non-fully-qualified type (i.e. just key instead of key=value) will only appear in the result if there is a wildcard registration for that key.*
> However, it is possible to have both "key" and one or more "key=xxx" in the same result. This can occur in the case of override registrations, for example what we use with datasources. There is a base type for datasources, but then additional datasource-specific registrations get added to support exposing additional vendor-specific metrics. In such situations, the response with "include-singletons=true" will look like this:
> {code}
> "result"=> ["datasource", "datasource=ExampleDS"]
> {code}
> A client that sees both "key" and "key=xxx" in a result can safely assume that "key=xxx" represents an override registration, overriding the basic type registered under "key=*".
> Note there is no guarantee as to ordering in the list, i.e. the above example could also look like this:
> {code}
> "result"=> ["datasource=ExampleDS", "datasource"]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months
[JBoss JIRA] (WFLY-4008) MBean deployment causes javax.naming.NameNotFoundException: java:comp/BeanManager
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-4008?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on WFLY-4008:
---------------------------------
I have sent a PR https://github.com/wildfly/wildfly-core/pull/380 to fix it and [~swd847] can you take a look ? Also it looks like the similar issue in the wildfly/sar/src/main/java/org/jboss/as/service/AbstractService.java, I has a fix https://github.com/zhfeng/jboss-as/commit/38fdb8fa9b9a20e5b6e106a23fc528b...
Thanks a lot!
> MBean deployment causes javax.naming.NameNotFoundException: java:comp/BeanManager
> ----------------------------------------------------------------------------------
>
> Key: WFLY-4008
> URL: https://issues.jboss.org/browse/WFLY-4008
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JMX, Naming
> Affects Versions: 8.1.0.Final
> Reporter: Darryl Miles
> Assignee: Stuart Douglas
> Labels: mbean
>
> If you create an MBean in your EJB and deploy the EJB.
> <pre>
> @SuppressWarnings("serial")
> public class Monitor implements MonitorMXBean, Serializable {
> private static final Logger log = LoggerFactory.getLogger(Monitor.class);
> private Boolean enabled = Boolean.FALSE;
> private Long valueOne;
> public Monitor() {
> log.debug("CTOR");
> }
> @Override
> public Boolean isEnabled() {
> return enabled;
> }
> @Override
> public void setEnabled(Boolean enabled) {
> this.enabled = enabled;
> }
> @Override
> public Long getValueOne() {
> return valueOne;
> }
> @Override
> public void setValueOne(Long valueOne) {
> this.valueOne = valueOne;
> }
> }
> </pre>
> And JMX MXBean
> <pre>
> import javax.management.MXBean;
> @MXBean
> public interface MonitorMXBean {
> void setEnabled(Boolean enabled);
> Boolean isEnabled();
> void setValueOne(Long valueOne);
> Long getValueOne();
> }
> </pre>
> 17:34:42,455 ERROR [org.jboss.as.weld] (MSC service thread 1-1) JBAS016001: Failed to tear down Weld contexts: javax.naming.NameNotFoundException: java:comp/BeanManager
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:187)
> at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:231)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:188)
> at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_25]
> at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_25]
> at org.jboss.as.weld.arquillian.WeldContextSetup.teardown(WeldContextSetup.java:108)
> at org.jboss.as.jmx.MBeanRegistrationService.stop(MBeanRegistrationService.java:132) [wildfly-jmx-8.1.0.Final.jar:8.1.0.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_25]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_25]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_25]
> Is this related to: https://issues.jboss.org/browse/WFLY-822 ?
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 11 months