August 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1715) HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode

by Yeray Santana Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1715?page=com.atlassian.jira.plugi... ] Yeray Santana Borges reassigned WFCORE-1715: -------------------------------------------- Assignee: Yeray Santana Borges > HostProcessReloadHandler does not reset the HostRunningModeControl's restartMode > -------------------------------------------------------------------------------- > > Key: WFCORE-1715 > URL: https://issues.jboss.org/browse/WFCORE-1715 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.2.0.Final, 3.0.0.Alpha5 > Reporter: Yeray Santana Borges > Assignee: Yeray Santana Borges > Fix For: 3.0.0.Alpha6 > > > The ReloadContext created by HostProcessReloadHandler sets the HostRunningModeControl's restartMode but then it never gets restored to the default value. The doReload() method of the ReloadContext should restore it. This ensures the ServerInventoryService.stop() only uses the value set by HostProcessReloadHandler once, for that one reload. > A concern here is that ServerInventoryService only goes into its "shutdownServers" logic if the restartMode == RestartMode.SERVERS. Which, due to this bug, it will be following any HC reload. But if we restore the default value of restartMode, that is null, and null != RestartMode.SERVERS. So the ""shutdownServers" logic will no longer kick in. But should it? Should the default value of restartMode be "null"? Or should it be RestartMode.SERVERS? If we change the default from null, then the behavior when no reload has happened will change. > Basically we need to decide whether the "shutdownServers" logic should happen by default. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7008) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.sar-deployment

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-7008?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-7008: ----------------------------------- Description: $subject says it all. Update: I decided to drop 'extension' from the name as no other cap uses that naming convention. was:$subject says it all. > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.extension.sar-deployment > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-7008 > URL: https://issues.jboss.org/browse/WFLY-7008 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all. > Update: I decided to drop 'extension' from the name as no other cap uses that naming convention. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1737) rrd on data-source=*/statistics=pool throws NPE

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1737?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-1737: ------------------------------------------ I moved this to core, as the NPE is definitely in kernel logic and poking around in how the DS subsystem responds to requests there's nothing that seems amiss there. > rrd on data-source=*/statistics=pool throws NPE > ----------------------------------------------- > > Key: WFCORE-1737 > URL: https://issues.jboss.org/browse/WFCORE-1737 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > > Run the following command in CLI it throws a NullPointerException > As it is a rrd it should not require a resolved wildcard > {code} > /subsystem=datasources/data-source=*/statistics=pool:read-resource-description > {code} > Results > {code} > { > "outcome" => "failed", > "result" => [], > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > The exception throws at server.log > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("resolve") failed - address: ([]): java.lang.NullPointerException > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:422) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeMultiTargetChildren(GlobalOperationHandlers.java:895) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:440) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:337) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > This op works > {code} > /subsystem=datasources/data-source=*:read-resource-description > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1737) rrd on data-source=*/statistics=pool throws NPE

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1737?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-7013 to WFCORE-1737: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1737 (was: WFLY-7013) Component/s: Domain Management (was: Domain Management) > rrd on data-source=*/statistics=pool throws NPE > ----------------------------------------------- > > Key: WFCORE-1737 > URL: https://issues.jboss.org/browse/WFCORE-1737 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > > Run the following command in CLI it throws a NullPointerException > As it is a rrd it should not require a resolved wildcard > {code} > /subsystem=datasources/data-source=*/statistics=pool:read-resource-description > {code} > Results > {code} > { > "outcome" => "failed", > "result" => [], > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > The exception throws at server.log > {code} > ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("resolve") failed - address: ([]): java.lang.NullPointerException > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:422) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeMultiTargetChildren(GlobalOperationHandlers.java:895) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:440) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$RegistrationAddressResolver.executeSingleTargetChild(GlobalOperationHandlers.java:903) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:442) > at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractAddressResolver.execute(GlobalOperationHandlers.java:337) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:951) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:694) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:389) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1363) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:410) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:232) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:213) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.access$300(ModelControllerClientOperationHandler.java:136) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:157) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1$1.run(ModelControllerClientOperationHandler.java:153) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:149) > at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:153) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$1.doExecute(ManagementRequestContextImpl.java:70) > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:160) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {code} > This op works > {code} > /subsystem=datasources/data-source=*:read-resource-description > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1735) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1735?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1735: ------------------------------------- Description: $subject says it all (was: Missing are: org.wildfly.domain.socket-binding-group org.wildfly.domain.profile org.wildfly.domain.server-group org.wildfly.domain.server-config) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1735 > URL: https://issues.jboss.org/browse/WFCORE-1735 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1736) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.request-controller

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1736: ---------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.request-controller Key: WFCORE-1736 URL: https://issues.jboss.org/browse/WFCORE-1736 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry $subject says it all -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1735) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-1735: ---------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.network.interface Key: WFCORE-1735 URL: https://issues.jboss.org/browse/WFCORE-1735 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Missing are: org.wildfly.domain.socket-binding-group org.wildfly.domain.profile org.wildfly.domain.server-group org.wildfly.domain.server-config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1734) Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1734?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-1734: ------------------------------------- Description: Missing are: org.wildfly.domain.socket-binding-group org.wildfly.domain.profile org.wildfly.domain.server-group org.wildfly.domain.server-config was:$subject says it all. Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities (was: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group) > Missing https://github.com/wildfly/wildfly-capabilities entry for managed domain capabilities > ---------------------------------------------------------------------------------------------- > > Key: WFCORE-1734 > URL: https://issues.jboss.org/browse/WFCORE-1734 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > Missing are: > org.wildfly.domain.socket-binding-group > org.wildfly.domain.profile > org.wildfly.domain.server-group > org.wildfly.domain.server-config -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1734) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1734?page=com.atlassian.jira.plugi... ] Brian Stansberry moved WFLY-7014 to WFCORE-1734: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-1734 (was: WFLY-7014) Component/s: Domain Management (was: Domain Management) > Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group > -------------------------------------------------------------------------------------------------------------------- > > Key: WFCORE-1734 > URL: https://issues.jboss.org/browse/WFCORE-1734 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7014) Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-7014: -------------------------------------- Summary: Missing https://github.com/wildfly/wildfly-capabilities entry for capability org.wildfly.domain.socket-binding-group Key: WFLY-7014 URL: https://issues.jboss.org/browse/WFLY-7014 Project: WildFly Issue Type: Bug Components: JMX Reporter: Brian Stansberry Assignee: Brian Stansberry $subject says it all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2016