]
Brian Stansberry moved WFLY-53 to WFCORE-406:
---------------------------------------------
Project: WildFly Core (was: WildFly)
Key: WFCORE-406 (was: WFLY-53)
Component/s: Domain Management
(was: Domain Management)
Fix Version/s: 1.0.0.CR1
(was: 9.0.0.Beta1)
Resource description for platform mbean properties that throw
UnsupportedOperationException should say nillable="true"
----------------------------------------------------------------------------------------------------------------------
Key: WFCORE-406
URL:
https://issues.jboss.org/browse/WFCORE-406
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Environment: FreeBSD, OpenJDK 1.6
Reporter: Brian Stansberry
Priority: Minor
Fix For: 1.0.0.CR1
Some platform mbean getters are documented to throw a UOE on some VMs. The read-resource
handler will catch the UOE and leave the attribute undefined, but the description says
it's not nillable.
Specifically, PlatformMBeanDescriptions.getThreadingResource()'s
THREAD_CPU_TIME_ENABLED attribute, although there may well be others.
This leads to this unit test failure on jvms where the UOE is thrown:
failure message="thread-cpu-time-enabled is undefined"
type="junit.framework.AssertionFailedError">junit.fra
mework.AssertionFailedError: thread-cpu-time-enabled is undefined
at junit.framework.Assert.fail(Assert.java:50)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.validateResource(PlatformMBeanResourceUn
itTestCase.java:595)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.basicResourceTest(PlatformMBeanResourceUnitTestCase.java:563)
at
org.jboss.as.platform.mbean.PlatformMBeanResourceUnitTestCase.testThreadingMXBean(PlatformMBeanResourceUnitTestCase.java:340)