[ https://issues.apache.org/jira/browse/KARAF-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Freeman Fang resolved KARAF-4523. --------------------------------- Resolution: Fixed Fix Version/s: 4.0.6 4.1.0 > JMXSecurityMBean bulk canInvoke should be robust even if bulkQuery contains > duplicate operations > ------------------------------------------------------------------------------------------------ > > Key: KARAF-4523 > URL: https://issues.apache.org/jira/browse/KARAF-4523 > Project: Karaf > Issue Type: Improvement > Components: karaf-management > Affects Versions: 4.0.5 > Reporter: Tadayoshi Sato > Assignee: Freeman Fang > Fix For: 4.1.0, 4.0.6 > > > {{JMXSecurityMBean#canInvoke(Map<String, List<String>>)}} method throws the > following exception in the presence of duplicate operations in the > {{bulkQuery}} parameter: > {code} > javax.management.openmbean.KeyAlreadyExistsException: Argument value's index, > calculated according to this TabularData instance's tabularType, already > refers to a value in this table. > at > javax.management.openmbean.TabularDataSupport.checkValueAndIndex(TabularDataSupport.java:898) > at > javax.management.openmbean.TabularDataSupport.internalPut(TabularDataSupport.java:358) > at > javax.management.openmbean.TabularDataSupport.put(TabularDataSupport.java:350) > at > org.apache.karaf.management.internal.JMXSecurityMBeanImpl.canInvoke(JMXSecurityMBeanImpl.java:102) > ... > {code} > There is an improvement (KARAF-1300) that addressed a similar situlation in a > different component, so why not make {{JMXSecurityMBean}} robust as well? -- This message was sent by Atlassian JIRA (v6.3.4#6332)