-
Bug
-
Resolution: Fixed
-
P2
-
6
Let's say we have two MBean classes A and B.
The AMBean exposes a method "delete" than when invoked calls unregisterMBean
on the 1 and 2 instances of the BMBean and then calls registerMBean on a new
instance 3 of the BMBean.
First of all, the agent registers in the MBeanServer three MBean instances
named as follows:
test:type=A
test:type=B,name=1
test:type=B,name=2
We connect to the agent with JConsole and see that the MBean tree displays:
test
|
|---> A
|
|---> B
|
|---> 1
|
|---> 2
then we call the "delete" method on the AMBean singleton.
After the invocation the MBeanServer contents look like:
test:type=A
test:type=B,name=3
But in JConsole the only MBean we can see is:
test
|
|---> A
The MBean tree hasn't been correctly refreshed and the instance 3 of the
BMBean is missing.
The AMBean exposes a method "delete" than when invoked calls unregisterMBean
on the 1 and 2 instances of the BMBean and then calls registerMBean on a new
instance 3 of the BMBean.
First of all, the agent registers in the MBeanServer three MBean instances
named as follows:
test:type=A
test:type=B,name=1
test:type=B,name=2
We connect to the agent with JConsole and see that the MBean tree displays:
test
|
|---> A
|
|---> B
|
|---> 1
|
|---> 2
then we call the "delete" method on the AMBean singleton.
After the invocation the MBeanServer contents look like:
test:type=A
test:type=B,name=3
But in JConsole the only MBean we can see is:
test
|
|---> A
The MBean tree hasn't been correctly refreshed and the instance 3 of the
BMBean is missing.