[JBoss JIRA] (WFCORE-2169) ProcessStateListener receives first running state transition from SUSPENDED to NORMAL when start-mode=suspend
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2169?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet moved JBEAP-8151 to WFCORE-2169:
--------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-2169 (was: JBEAP-8151)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
(was: Domain Management)
Affects Version/s: 3.0.0.Alpha16
(was: 7.1.0.DR10)
> ProcessStateListener receives first running state transition from SUSPENDED to NORMAL when start-mode=suspend
> -------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-2169
> URL: https://issues.jboss.org/browse/WFCORE-2169
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 3.0.0.Alpha16
> Reporter: ehsavoie Hugonnet
> Assignee: Brian Stansberry
>
> When server is started with start-mode=suspend.
> First received transition is from SUSPENDED to NORMAL. It should be something -> SUSPENDED. Probably STARTING -> SUSPENDED, but now listener always receives first transition from SUSPENDED
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2168) Remove CredentialStoreClient in favour of CredentialSource
by Peter Skopek (JIRA)
Peter Skopek created WFCORE-2168:
------------------------------------
Summary: Remove CredentialStoreClient in favour of CredentialSource
Key: WFCORE-2168
URL: https://issues.jboss.org/browse/WFCORE-2168
Project: WildFly Core
Issue Type: Task
Components: Security
Affects Versions: 3.0.0.Alpha16
Reporter: Peter Skopek
Assignee: Peter Skopek
With recent changes to Elytron Authentication Client make credential referencing use CredentialSource instead of CredentialStoreClient.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2087) Possible deadlock on server start
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2087?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet commented on WFCORE-2087:
-------------------------------------------
yes, exactly the same
> Possible deadlock on server start
> ---------------------------------
>
> Key: WFCORE-2087
> URL: https://issues.jboss.org/browse/WFCORE-2087
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Stuart Douglas
> Assignee: ehsavoie Hugonnet
>
> I observed a deadlock on start when attempting to run the test suite with standalone-elytron.xml.
> Some MSC threads were stuck:
> {code}
> "MSC service thread 1-4" #17 prio=5 os_prio=31 tid=0x00007f820a1f6800 nid=0x5f03 waiting on condition [0x000070000b3ec000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000007bd8a8e80> (a java.util.concurrent.FutureTask)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)
> at java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.toSecurityDomain(AccessIdentityResourceDefinition.java:187)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.access$300(AccessIdentityResourceDefinition.java:71)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler.lambda$performRuntime$12(AccessIdentityResourceDefinition.java:165)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler$$Lambda$260/422594057.get(Unknown Source)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:54)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:39)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1207)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:854)
> at org.infinispan.jmx.JmxUtil.findJmxDomain(JmxUtil.java:126)
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:49)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:657)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.lambda$build$46(CacheContainerBuilder.java:106)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder$$Lambda$311/1536655574.get(Unknown Source)
> at org.wildfly.clustering.service.SuppliedValueService.lambda$new$2(SuppliedValueService.java:42)
> at org.wildfly.clustering.service.SuppliedValueService$$Lambda$313/1532240932.apply(Unknown Source)
> at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:67)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It looks like the root cause is IdentityService not starting probably due to
> {code}
> 2016-12-06 11:04:02,406 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.security-realm.ApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ApplicationRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185)
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2087) Possible deadlock on server start
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2087?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet reassigned WFCORE-2087:
-----------------------------------------
Assignee: ehsavoie Hugonnet (was: Darran Lofthouse)
> Possible deadlock on server start
> ---------------------------------
>
> Key: WFCORE-2087
> URL: https://issues.jboss.org/browse/WFCORE-2087
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Stuart Douglas
> Assignee: ehsavoie Hugonnet
>
> I observed a deadlock on start when attempting to run the test suite with standalone-elytron.xml.
> Some MSC threads were stuck:
> {code}
> "MSC service thread 1-4" #17 prio=5 os_prio=31 tid=0x00007f820a1f6800 nid=0x5f03 waiting on condition [0x000070000b3ec000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000007bd8a8e80> (a java.util.concurrent.FutureTask)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)
> at java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.toSecurityDomain(AccessIdentityResourceDefinition.java:187)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.access$300(AccessIdentityResourceDefinition.java:71)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler.lambda$performRuntime$12(AccessIdentityResourceDefinition.java:165)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler$$Lambda$260/422594057.get(Unknown Source)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:54)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:39)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1207)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:854)
> at org.infinispan.jmx.JmxUtil.findJmxDomain(JmxUtil.java:126)
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:49)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:657)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.lambda$build$46(CacheContainerBuilder.java:106)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder$$Lambda$311/1536655574.get(Unknown Source)
> at org.wildfly.clustering.service.SuppliedValueService.lambda$new$2(SuppliedValueService.java:42)
> at org.wildfly.clustering.service.SuppliedValueService$$Lambda$313/1532240932.apply(Unknown Source)
> at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:67)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It looks like the root cause is IdentityService not starting probably due to
> {code}
> 2016-12-06 11:04:02,406 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.security-realm.ApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ApplicationRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185)
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months
[JBoss JIRA] (WFCORE-2087) Possible deadlock on server start
by ehsavoie Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2087?page=com.atlassian.jira.plugi... ]
ehsavoie Hugonnet resolved WFCORE-2087.
---------------------------------------
Resolution: Duplicate Issue
> Possible deadlock on server start
> ---------------------------------
>
> Key: WFCORE-2087
> URL: https://issues.jboss.org/browse/WFCORE-2087
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Stuart Douglas
> Assignee: ehsavoie Hugonnet
>
> I observed a deadlock on start when attempting to run the test suite with standalone-elytron.xml.
> Some MSC threads were stuck:
> {code}
> "MSC service thread 1-4" #17 prio=5 os_prio=31 tid=0x00007f820a1f6800 nid=0x5f03 waiting on condition [0x000070000b3ec000]
> java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0x00000007bd8a8e80> (a java.util.concurrent.FutureTask)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at java.util.concurrent.FutureTask.awaitDone(FutureTask.java:429)
> at java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.toSecurityDomain(AccessIdentityResourceDefinition.java:187)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition.access$300(AccessIdentityResourceDefinition.java:71)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler.lambda$performRuntime$12(AccessIdentityResourceDefinition.java:165)
> at org.jboss.as.domain.management.access.AccessIdentityResourceDefinition$AccessIdentityAddHandler$$Lambda$260/422594057.get(Unknown Source)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:54)
> at org.jboss.as.controller.access.management.ManagementSecurityIdentitySupplier.get(ManagementSecurityIdentitySupplier.java:39)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.authorizeMBeanOperation(PluggableMBeanServerImpl.java:1207)
> at org.jboss.as.jmx.PluggableMBeanServerImpl.queryNames(PluggableMBeanServerImpl.java:854)
> at org.infinispan.jmx.JmxUtil.findJmxDomain(JmxUtil.java:126)
> at org.infinispan.jmx.JmxUtil.buildJmxDomain(JmxUtil.java:49)
> at org.infinispan.jmx.CacheManagerJmxRegistration.updateDomain(CacheManagerJmxRegistration.java:79)
> at org.infinispan.jmx.CacheManagerJmxRegistration.buildRegistrar(CacheManagerJmxRegistration.java:73)
> at org.infinispan.jmx.AbstractJmxRegistration.registerMBeans(AbstractJmxRegistration.java:37)
> at org.infinispan.jmx.CacheManagerJmxRegistration.start(CacheManagerJmxRegistration.java:41)
> at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:657)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.lambda$build$46(CacheContainerBuilder.java:106)
> at org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder$$Lambda$311/1536655574.get(Unknown Source)
> at org.wildfly.clustering.service.SuppliedValueService.lambda$new$2(SuppliedValueService.java:42)
> at org.wildfly.clustering.service.SuppliedValueService$$Lambda$313/1532240932.apply(Unknown Source)
> at org.wildfly.clustering.service.FunctionalValueService.start(FunctionalValueService.java:67)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> It looks like the root cause is IdentityService not starting probably due to
> {code}
> 2016-12-06 11:04:02,406 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service org.wildfly.security.security-realm.ApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.security.security-realm.ApplicationRealm: WFLYELY00025: Referenced property file is invalid: ELY01006: No realm name found in password property file
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:185)
> at org.wildfly.extension.elytron.PropertiesRealmDefinition$1$1.get(PropertiesRealmDefinition.java:164)
> at org.wildfly.extension.elytron.TrivialService.start(TrivialService.java:53)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1963)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1896)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 3 months