[JBoss JIRA] (WFCORE-319) Metrics/operations missing in platform mbean core-service
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-319?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-857 to WFCORE-319:
----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-319 (was: WFLY-857)
Component/s: Domain Management
(was: Domain Management)
> Metrics/operations missing in platform mbean core-service
> ---------------------------------------------------------
>
> Key: WFCORE-319
> URL: https://issues.jboss.org/browse/WFCORE-319
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Rupp
> Labels: rhq
>
> The platform mbean(s) exposes more metrics that what is currently available at core-service=platform-mbean
> - Active Thread Count
> - Active Thread Group Count
> - JVM Free memory
> - JVM Total memory
>
> OS metrics -- java.lang:type=OperatingSystem
> - Free Physical Memory -- FreePhysicalMemorySize
> - Free Swap Memory -- FreeSwapSpaceSize
> - Process CPU Time -- ProcessCpuTime
> - Committed Virtual Memory -- CommittedVirtualMemorySize
> - open files --OpenFileDescriptorCount
> Threading
> - SuspendedThreadCount
> - DeadLockedThreadCount
> Memory -- java.lang:type=Memory
> - operation to trigger gc -- gc
> And probably more
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-315) NPE executing domain operation
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-315?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-1997 to WFCORE-315:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-315 (was: WFLY-1997)
Component/s: Domain Management
(was: Domain Management)
> NPE executing domain operation
> ------------------------------
>
> Key: WFCORE-315
> URL: https://issues.jboss.org/browse/WFCORE-315
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Heiko Braun
> Assignee: Emanuel Muckenhuber
>
> {noformat}
> [ERROR] Request
> [ERROR] {
> [ERROR] "operation" => "composite",
> [ERROR] "address" => [],
> [ERROR] "steps" => [
> [ERROR] {
> [ERROR] "address" => [("server-group" => "*")],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] },
> [ERROR] {
> [ERROR] "address" => [
> [ERROR] ("host" => "master"),
> [ERROR] ("server" => "*")
> [ERROR] ],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] },
> [ERROR] {
> [ERROR] "address" => [("extension" => "*")],
> [ERROR] "operation" => "read-resource-description",
> [ERROR] "access-control" => "trim-descriptions",
> [ERROR] "operations" => true
> [ERROR] }
> [ERROR] ],
> [ERROR] "operation-headers" => {"roles" => "OPERATOR"}
> [ERROR] }
> {noformat}
> leads to
> {noformat}
> [Host Controller] 16:34:53,544 ERROR [org.jboss.as.controller.management-operation] (XNIO-1 task-12) JBAS014612: Operation ("composite") failed - address: ([]): java.lang.NullPointerException
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:167)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.HostControllerExecutionSupport$Factory.create(HostControllerExecutionSupport.java:181)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationSlaveStepHandler.addSteps(OperationSlaveStepHandler.java:108)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeTwoPhaseOperation(OperationCoordinatorStepHandler.java:201)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:124)
> [Host Controller] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:103)
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:610) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:488) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:277) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:272) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:257) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:142) [wildfly-controller-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:154) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:96) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler$2.run(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.7.0_17]
> [Host Controller] at javax.security.auth.Subject.doAs(Subject.java:415) [rt.jar:1.7.0_17]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:92) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at org.jboss.as.domain.http.server.security.SubjectDoAsHandler.handleRequest(SubjectDoAsHandler.java:86) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:50) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:87) [wildfly-domain-http-interface-8.0.0.Beta1-SNAPSHOT.jar:8.0.0.Beta1-SNAPSHOT]
> [Host Controller] at io.undertow.security.handlers.AuthenticationCallHandler.handleRequest(AuthenticationCallHandler.java:52) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at io.undertow.server.HttpHandlers.executeRootHandler(HttpHandlers.java:36) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:614) [undertow-core-1.0.0.Beta12.jar:1.0.0.Beta12]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_17]
> [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_17]
> [Host Controller] at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_17]
> [Host Controller]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-314) Configure child resources as mandatory or its cardinality in ResourceDefinition
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-314?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-2915 to WFCORE-314:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-314 (was: WFLY-2915)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: (was: 9.0.0.Beta1)
> Configure child resources as mandatory or its cardinality in ResourceDefinition
> -------------------------------------------------------------------------------
>
> Key: WFCORE-314
> URL: https://issues.jboss.org/browse/WFCORE-314
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Pedro Igor
>
> Currently, the ResourceDefinition does not provide a good way to configure a child resource as mandatory or even its cardinality. Instead of that, manual validations are required inside handlers.
> The idea is remove manual validations and let it be done automatically by the model.
> Considering the following example:
> {code:xml}
> <parent-resource>
> <child-resource/>
> </parent-resource>
> {code}
> Would be useful if we could mark the 'child-resource' above as mandatory. Or even:
> {code:xml}
> <parent-resource>
> <child-resource/>
> <child-resource/>
> <child-resource/>
> <child-resource/> <!-- This is invalid. Only 3 childs are supported. -->
> </parent-resource>
> {code}
> Where we can specify the cardinality for a child-resource so we can configure the min/max occurrences.
> I think the latter approach is more flexible and can be used to get a resource as mandatory or specify its number of occurrence.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-313) DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-313?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-2947 to WFCORE-313:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-313 (was: WFLY-2947)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.Beta1
(was: 9.0.0.Beta1)
> DefaultOperationDescriptionProvider uses incorrect call to create reply parameter description
> ---------------------------------------------------------------------------------------------
>
> Key: WFCORE-313
> URL: https://issues.jboss.org/browse/WFCORE-313
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management
> Reporter: Brian Stansberry
> Fix For: 1.0.0.Beta1
>
>
> When creating reply descriptions, DefaultOperationDescriptionProvider calls attributeDescriptionResolver.getOperationParameterDescription instead of attributeDescriptionResolver.getOperationReplyValueTypeDescription.
> A fix needs to not break compatibility for existing users of the incorrect behavior; i.e. call the correct method in a try block, catch any MissingResourceException, and if caught call the incorrect method.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-311) Better error message if authentication is required to connect to the master but no realm is associated on the slave
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-311?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3035 to WFCORE-311:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-311 (was: WFLY-3035)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.Beta1)
> Better error message if authentication is required to connect to the master but no realm is associated on the slave
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFCORE-311
> URL: https://issues.jboss.org/browse/WFCORE-311
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Environment: RH EL 6.3 - JBoss EAP 6.2
> Reporter: Riccardo Benvenuti
> Priority: Minor
> Fix For: 1.0.0.CR1
>
>
> In JBoss 6.2 domain environment if in the host.xml file on the slave is missing the realm in the domain-controller tag as reported below
> <domain-controller>
> <remote host="10.123.137.200" port="9999"/>
> </domain-controller>
> we get the following error:
> JBoss Bootstrap Environment
> JBOSS_HOME: /opt/jboss7/jboss-eap-6.2
> JAVA: /usr/java/jdk1.7.0_51/bin/java
> JAVA_OPTS: -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
> =========================================================================
> 16:45:58,529 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> 16:45:58,746 INFO [org.jboss.as.process.Host Controller.status] (main) JBAS012017: Starting process 'Host Controller'
> [Host Controller] 16:45:59,735 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final-redhat-2
> [Host Controller] 16:45:59,913 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
> [Host Controller] 16:46:00,023 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) starting
> [Host Controller] 16:46:00,991 INFO [org.xnio] (MSC service thread 1-1) XNIO Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,010 INFO [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
> [Host Controller] 16:46:01,033 INFO [org.jboss.as] (Controller Boot Thread) JBAS010902: Creating http management service using network interface (management) port (9990) securePort (-1)
> [Host Controller] 16:46:01,045 INFO [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 3.2.18.GA-redhat-1
> [Host Controller] 16:46:01,173 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 10.123.137.201:9999
> [Host Controller] 16:46:01,857 ERROR [org.jboss.remoting.remote.connection] (Remoting "testjb7s1:MANAGEMENT" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> [Host Controller] 16:46:01,869 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010901: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: JBAS010942: Unable to connect due to authentication failure.
> [Host Controller] 16:46:01,891 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (missing) dependents: [service jboss.server.controller.management.security_realm.ApplicationRealm]
> [Host Controller]
> [Host Controller] 16:46:01,897 INFO [org.jboss.as.controller] (MSC service thread 1-1) JBAS014774: Service status report
> [Host Controller] JBAS014775: New missing/unsatisfied dependencies:
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (missing) dependents: [service jboss.remoting.authentication_provider.management]
> [Host Controller]
> [Host Controller] 16:46:01,922 INFO [org.jboss.as.controller] (MSC service thread 1-2) JBAS014774: Service status report
> [Host Controller] JBAS014776: Newly corrected services:
> [Host Controller] service jboss.server.controller.management.security_realm.ApplicationRealm.properties_authentication (no longer required)
> [Host Controller] service jboss.server.controller.management.security_realm.ManagementRealm (no longer required)
> [Host Controller]
> [Host Controller] 16:46:01,927 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015950: JBoss EAP 6.2.0.GA (AS 7.3.0.Final-redhat-14) stopped in 28ms
> 16:46:02,245 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 99
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012016: Shutting down process controller
> 16:46:02,247 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All processes finished; exiting
> Adding the realm everything works correctly
> <domain-controller>
> <remote host="10.123.137.200" port="9999" security-realm="ManagementRealm"/>
> </domain-controller>
> Maybe a warning message could be useful to find the problem.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-312) Taking thread dumps via HC
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-312?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3025 to WFCORE-312:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-312 (was: WFLY-3025)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
> Taking thread dumps via HC
> --------------------------
>
> Key: WFCORE-312
> URL: https://issues.jboss.org/browse/WFCORE-312
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Domain Management
> Reporter: James Livingston
> Assignee: James Livingston
>
> It would be useful to be able to gather low-level per-server information such as Java thread dumps. This would best be gathered from the Host Controllers, and be available via the management model.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-310) Don't copy the contents to all hosts when assigning a deployment to a server-group
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-310?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFCORE-310:
-----------------------------------------
Emanuel, could you update the title and description of this to reflect the private comments in https://bugzilla.redhat.com/show_bug.cgi?id=1073585 ? Basically, we already have ignore-unused-configuration for this, but we need to tighten up the relationship of this to --backup, --cached-dc, etc and look into have the default behavior to be ignoring, at least in some cases. Let's use this JIRA for that work.
> Don't copy the contents to all hosts when assigning a deployment to a server-group
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-310
> URL: https://issues.jboss.org/browse/WFCORE-310
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
> Fix For: 1.0.0.CR1
>
>
> When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months
[JBoss JIRA] (WFCORE-310) Don't copy the contents to all hosts when assigning a deployment to a server-group
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFCORE-310?page=com.atlassian.jira.plugin... ]
Brian Stansberry moved WFLY-3110 to WFCORE-310:
-----------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-310 (was: WFLY-3110)
Issue Type: Enhancement (was: Bug)
Affects Version/s: (was: 8.0.0.Final)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.Beta1)
> Don't copy the contents to all hosts when assigning a deployment to a server-group
> ----------------------------------------------------------------------------------
>
> Key: WFCORE-310
> URL: https://issues.jboss.org/browse/WFCORE-310
> Project: WildFly Core
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Emanuel Muckenhuber
> Assignee: Emanuel Muckenhuber
> Fix For: 1.0.0.CR1
>
>
> When assigning a deployment to a server-group it also copies the actual deployment contents to all hosts regardless of the whether the deployment is used locally or not. This should be changed that the contents are only retrieved if they are actually needed on a local server.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 5 months