[jboss-jira] [JBoss JIRA] Created: (JBAS-6711) if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
Ian Springer (JIRA)
jira-events at lists.jboss.org
Tue Mar 31 11:15:22 EDT 2009
if non-null values are set for ObjectName ManagedProperties (i.e. DLQ, serverPeer, or expiryQueue props) in Topic/Queue templates, applyTemplate() throws "IllegalArgumentException: Not handled value: CompositeValueSupport"
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6711
URL: https://jira.jboss.org/jira/browse/JBAS-6711
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
For example, I pass the following template, which has a non-null but valid value set for the "DLQ" prop:
Properties for DeploymentTemplateInfo [QueueTemplate]:
name=DLQ, 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.destination,keyP
ropertyList={service=Queue, name=DLQ }]
name=JNDIName, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:java.lang.String:rrr
name=clustered, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:boolean:true
name=downCacheSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=expiryQueue, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
name=fullSize, viewUse=CONFIGURATION, mandatory=false, value= SimpleMetaType:int:75000
name=maxDeliveryAttempts, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=maxSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=messageCounterHistoryDayLimit, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=pageSize, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=redeliveryDelay, viewUse=CONFIGURATION, mandatory=false, type=SimpleMetaType, value= <<<null>>>
name=securityConfig, viewUse=CONFIGURATION, mandatory=false, type=MutableCompositeMetaType, value= <<<null>>>
name=serverPeer, viewUse=CONFIGURATION, mandatory=false, type=ImmutableCompositeMetaType, value= <<<null>>>
And here's the stack trace of the IAE that applyTemplate() throws:
11:04:25,156 ERROR [ApplicationServerComponent] Unable to apply template [QueueTemplate] to create ManagedComponent of type ComponentType{type=JMSDestination, s
ubtype=Queue}.
java.lang.IllegalArgumentException: Not handled value: CompositeValueSupport: metaType=[ImmutableCompositeMetaType{javax.management.ObjectName items=[name=domai
n type=java.lang.String], [name=keyPropertyList type=java.util.Properties]}] items=[domain=SimpleMetaType:java.lang.String:jboss.messaging.destination,keyProper
tyList={service=Queue, name=DLQ }]
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.writeTemplate(JmsDestinationTemplate.java:158)
at org.jboss.profileservice.management.templates.JmsDestinationTemplate.applyTemplate(JmsDestinationTemplate.java:96)
at org.jboss.profileservice.management.AbstractTemplateCreator.applyTemplate(AbstractTemplateCreator.java:90)
at org.jboss.profileservice.management.ManagementViewImpl.applyTemplate(ManagementViewImpl.java:1017)
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 org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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)
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 org.jboss.aop.generatedproxies.AOPProxy$1.applyTemplate(AOPProxy$1.java)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createConfigurationBasedResource(ApplicationServerComponent.java:235)
at org.rhq.plugins.jbossas5.ApplicationServerComponent.createResource(ApplicationServerComponent.java:139)
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 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
More information about the jboss-jira
mailing list