[JBoss JIRA] Created: (JBAS-6688) expose ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
6:53 p.m.
expose ObjectNames as SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
-----------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently
exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:53 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer updated JBAS-6688:
-------------------------------
Summary: expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s (was: expose ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s)
Description:
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently
exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
was:
Properties representing ObjectNames in the Topic and Queue ManagedComponents are currently
exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 p.m.
New subject: [JBoss JIRA] Resolved: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBAS-6688.
---------------------------------
Resolution: Done
These destination properties are now strings
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:10 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Scott M Stark updated JBAS-6688:
--------------------------------
Fix Version/s: JBossAS-5.1.0.CR1
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 p.m.
New subject: [JBoss JIRA] Reopened: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer reopened JBAS-6688:
--------------------------------
Looks like this caused a regression. Now when I look at the ManagedComponent for an
existing topic or queue that has a DLQ, expiryQueue, and/or serverPeer defined, the
corresponding ManagedProperties have null values.
e.g.:
<mbean code="org.jboss.jms.server.destination.QueueService"
name="jboss.messaging.destination:service=Queue,name=QueueWithOwnDLQAndExpiryQueue"
xmbean-dd="xmdesc/Queue-xmbean.xml">
<annotation>(a)org.jboss.system.deployers.managed.ManagementObjectClass(code=org.jboss.jms.server.destination.QueueServiceMO)</annotation>
<depends
optional-attribute-name="ServerPeer">jboss.messaging:service=ServerPeer</depends>
<depends>jboss.messaging:service=PostOffice</depends>
<attribute
name="DLQ">jboss.messaging.destination:service=Queue,name=PrivateDLQ</attribute>
<attribute
name="ExpiryQueue">jboss.messaging.destination:service=Queue,name=PrivateExpiryQueue</attribute>
</mbean>
has ManagedProperties:
name=DLQ, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
type=SimpleMetaType, value= <<<null>>>
* name=JNDIName, viewUse=CONFIGURATION, readOnly=false, mandatory=true, removed=false,
value= SimpleMetaType:java.lang.String:/queue/QueueWithOwnDLQAndExpiryQu
eue
name=clustered, viewUse=CONFIGURATION, readOnly=true, mandatory=false, removed=false,
value= SimpleMetaType:boolean:false
name=downCacheSize, viewUse=CONFIGURATION, readOnly=false, mandatory=false,
removed=false, value= SimpleMetaType:int:2000
name=expiryQueue, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
type=SimpleMetaType, value= <<<null>>>
name=fullSize, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
value= SimpleMetaType:int:200000
name=maxDeliveryAttempts, viewUse=CONFIGURATION, readOnly=false, mandatory=false,
removed=false, value= SimpleMetaType:int:-1
name=maxSize, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
value= SimpleMetaType:int:-1
name=messageCounterHistoryDayLimit, viewUse=CONFIGURATION, readOnly=false,
mandatory=false, removed=false, value= SimpleMetaType:int:-1
* name=name, viewUse=CONFIGURATION, readOnly=true, mandatory=true, removed=false, value=
SimpleMetaType:java.lang.String:QueueWithOwnDLQAndExpiryQueue
name=pageSize, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
value= SimpleMetaType:int:2000
name=redeliveryDelay, viewUse=CONFIGURATION, readOnly=false, mandatory=false,
removed=false, value= SimpleMetaType:long:-1
name=securityConfig, viewUse=CONFIGURATION, readOnly=false, mandatory=false,
removed=false, type=MapCompositeMetaType, value= <<<null>>>
name=serverPeer, viewUse=CONFIGURATION, readOnly=false, mandatory=false, removed=false,
type=SimpleMetaType, value= <<<null>>>
name=consumerCount, viewUse=STATISTIC, readOnly=true, mandatory=false, removed=false,
value= SimpleMetaType:java.lang.Integer:0
name=createdProgrammatically, viewUse=STATISTIC, readOnly=true, mandatory=false,
removed=false, value= SimpleMetaType:java.lang.Boolean:false
name=deliveringCount, viewUse=STATISTIC, readOnly=true, mandatory=false, removed=false,
value= SimpleMetaType:java.lang.Integer:0
name=messageCount, viewUse=STATISTIC, readOnly=true, mandatory=false, removed=false,
value= SimpleMetaType:java.lang.Integer:0
name=messageCounter, viewUse=STATISTIC, readOnly=true, mandatory=false, removed=false,
value= CompositeValueSupport: metaType=[MutableCompositeMetaType{org.j
boss.jms.server.messagecounter.MessageCounter items=[name=count type=int],
[name=countDelta type=int], [name=counterAsString type=java.lang.String], [name=desti
nationDurable type=boolean], [name=destinationName type=java.lang.String],
[name=destinationSubscription type=java.lang.String], [name=destinationTopic type=boo
lean], [name=historyAsString type=java.lang.String], [name=historyLimit type=int],
[name=lastUpdate type=long], [name=messageCount type=int], [name=messageCount
Delta type=int]}]
items=[count=SimpleMetaType:int:0,countDelta=SimpleMetaType:int:0,counterAsString=SimpleMetaType:java.lang.String:Queue,Queue.QueueWithOwnDLQA
ndExpiryQueue,-,-,0,0,0,0,-,destinationDurable=SimpleMetaType:boolean:false,destinationName=SimpleMetaType:java.lang.String:Queue.QueueWithOwnDLQAndExpiryQueue,
destinationSubscription=null,destinationTopic=SimpleMetaType:boolean:false,historyAsString=SimpleMetaType:java.lang.String:1
4/5/09,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,0,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
,historyLimit=SimpleMetaType:int:-1,lastUpdate=SimpleMetaType:long:0,messageCount=SimpleMetaType:int:0,messageCountDelta=SimpleMetaType:int:0]
name=messageStatistics, viewUse=STATISTIC, readOnly=true, mandatory=false,
removed=false, value= CompositeValueSupport: metaType=[MutableCompositeMetaType{or
g.jboss.jms.server.messagecounter.MessageStatistics items=[name=asString
type=java.lang.String], [name=count type=int], [name=countDelta type=int], [name=depth
type=int], [name=depthDelta type=int], [name=durable type=boolean], [name=name
type=java.lang.String], [name=subscriptionID type=java.lang.String], [name=timeLa
stUpdate type=long], [name=topic type=boolean]}]
items=[asString=SimpleMetaType:java.lang.String:Queue,Queue.QueueWithOwnDLQAndExpiryQueue,-,-,0,0,0,0,-,count=S
impleMetaType:int:0,countDelta=SimpleMetaType:int:0,depth=SimpleMetaType:int:0,depthDelta=SimpleMetaType:int:0,durable=SimpleMetaType:boolean:false,name=SimpleM
etaType:java.lang.String:Queue.QueueWithOwnDLQAndExpiryQueue,subscriptionID=null,timeLastUpdate=SimpleMetaType:long:0,topic=SimpleMetaType:boolean:false]
name=scheduledMessageCount, viewUse=STATISTIC, readOnly=true, mandatory=false,
removed=false, value= SimpleMetaType:java.lang.Integer:0
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6688:
------------------------------------
Also, when I try to call updateComponent() with any of the ObjectName props set to null, I
get an NPE:
Failed to update Resource (see app server log for additional details):
java.lang.NullPointerException at
org.jboss.metatype.plugins.values.mappers.StringObjectNameMetaMapper.unwrapMetaValue(StringObjectNameMetaMapper.java:67)
at
org.jboss.metatype.plugins.values.mappers.StringObjectNameMetaMapper.unwrapMetaValue(StringObjectNameMetaMapper.java:42)
at
org.jboss.system.deployers.managed.ServiceMetaDataICF.setValue(ServiceMetaDataICF.java:280)
at
org.jboss.system.deployers.managed.ServiceMetaDataICF.setValue(ServiceMetaDataICF.java:58)
at
org.jboss.managed.plugins.WritethroughManagedPropertyImpl.setValue(WritethroughManagedPropertyImpl.java:102)
at
org.rhq.plugins.jbossas5.util.ConversionUtils.populateManagedPropertyFromProperty(ConversionUtils.java:277)
at
org.rhq.plugins.jbossas5.util.ConversionUtils.convertConfigurationToManagedProperties(ConversionUtils.java:248)
at
org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at
java.util.concurrent.FutureTask.run(FutureTask.java:138) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at
java.lang.Thread.run(Thread.java:619)
This happens whether the MetaValue itself is null or the wrapped Serializable is null.
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Minor
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer updated JBAS-6688:
-------------------------------
Priority: Critical (was: Minor)
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:54 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Ian Springer commented on JBAS-6688:
------------------------------------
It also fails with a different exception when a non-null value is specified for one of the
ObjectName props:
Failed to update Resource (see app server log for additional details):
java.lang.reflect.UndeclaredThrowableException: Failed to set property 'DLQ' on
component
'jboss.messaging.destination:name=MyQueueWithSecurityConfig,service=Queue' to
value
[SimpleMetaType:java.lang.String:jboss.messaging.destination:service=Queue,name=PrivateDLQ].
at
org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:92)
at
org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708) at
org.jboss.remoting.Client.invoke(Client.java:612) at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
AOPProxy$1.updateComponent(AOPProxy$1.java) at
org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174)
at
org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at
java.util.concurrent.FutureTask.run(FutureTask.java:138) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at
java.lang.Thread.run(Thread.java:619) Caused by:
javax.management.InvalidAttributeValueException: Set attribute has class class
java.lang.String loaded from null that is not assignable to attribute class class
javax.management.ObjectName loaded from null at
org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.checkAssignable(ModelMBeanAttributeInterceptor.java:229)
at
org.jboss.mx.interceptor.ModelMBeanAttributeInterceptor.invoke(ModelMBeanAttributeInterceptor.java:88)
at org.jboss.mx.interceptor.PersistenceInterceptor.invoke(PersistenceInterceptor.java:76)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at
org.jboss.mx.server.AbstractMBeanInvoker.setAttribute(AbstractMBeanInvoker.java:461) at
org.jboss.mx.server.MBeanServerImpl.setAttribute(MBeanServerImpl.java:617) at
org.jboss.system.microcontainer.ServiceControllerContext.set(ServiceControllerContext.java:182)
at
org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:79)
at
org.jboss.kernel.plugins.registry.basic.BasicKernelBus$2.dispatch(BasicKernelBus.java:83)
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.execute(BasicKernelBus.java:54)
at org.jboss.kernel.plugins.registry.basic.BasicKernelBus.set(BasicKernelBus.java:75) at
org.jboss.profileservice.management.KernelBusRuntimeComponentDispatcher.set(KernelBusRuntimeComponentDispatcher.java:88)
at
org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at
org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82)
at
org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:97)
at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at
org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106)
at org.jboss.remoting.Client.invoke(Client.java:1708) at
org.jboss.remoting.Client.invoke(Client.java:612) at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at
AOPProxy$1.updateComponent(AOPProxy$1.java) at
org.rhq.plugins.jbossas5.ManagedComponentComponent.updateComponent(ManagedComponentComponent.java:174)
at
org.rhq.plugins.jbossas5.AbstractManagedComponent.updateResourceConfiguration(AbstractManagedComponent.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
java.lang.reflect.Method.invoke(Method.java:597) at
org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:449)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at
java.util.concurrent.FutureTask.run(FutureTask.java:138) at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at
java.lang.Thread.run(Thread.java:619) at
org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72)
... 18 more
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Charles Crouch updated JBAS-6688:
---------------------------------
Priority: Blocker (was: Critical)
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:12 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-6688) expose ManagedProperties representing ObjectNames as SimpleMetaType.STRINGs rather than ImmutableCompositeMetaType{javax.management.ObjectName}s
[
https://jira.jboss.org/jira/browse/JBAS-6688?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBAS-6688.
---------------------------------
Resolution: Done
The JmsDestinationUnitTestCase is now adding DLQ and expiryQueue values in the
testCreateQueue test, and the testCreateQueueWithNullDLQ test sets a MetaValue(null) and
null for the DLQ and expiryQueue respectively.
expose ManagedProperties representing ObjectNames as
SimpleMetaType.STRINGs rather than
ImmutableCompositeMetaType{javax.management.ObjectName}s
------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6688
URL: https://jira.jboss.org/jira/browse/JBAS-6688
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Priority: Blocker
Fix For: JBossAS-5.1.0.CR1
Properties representing ObjectNames in the Topic and Queue ManagedComponents are
currently exposed as a complicated CompositeValueSupport type that contains a String and a
Properties child value, e.g.:
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, value= CompositeValueSupport:
metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items
=[name=domain type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}]
items=[domain=SimpleMetaType:java.lang.String:jboss.messaging,keyProper
tyList={service=ServerPeer}]
Items:
domain=SimpleMetaType:java.lang.String:jboss.messaging
keyPropertyList={service=ServerPeer}
I think exposing it as a simple value of type SimpleMetaType.STRING would make things
easier for Jopr/EmbJopr, as well as other clients of the management interface. As it's
exposed today, just to get it into a usable format, the client would have to write code to
convert the CompositeValue into an ObjectName, rather than being able to simply call new
ObjectName(simpleValue.getValue()).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5644
days inactive
5657
days old
9 comments
3 participants
participants (3)
-
Charles Crouch (JIRA) -
Ian Springer (JIRA)
-
Scott M Stark (JIRA)