[KARAF-4523] JMXSecurityMBean bulk canInvoke should be robust even if bulkQuery contains duplicate operations

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.5
• Fix Version/s: 4.1.0, 3.0.7, 4.0.6
• Component/s: karaf
• Assignee: Freeman Yue Fang
• Reporter: Tadayoshi Sato
• Created: 10/May/16 01:56
• Updated: 15/Sep/18 05:17
• Resolved: 10/May/16 06:54

Description

JMXSecurityMBean#canInvoke(Map<String, List<String>>) method throws the following exception in the presence of duplicate operations in the bulkQuery parameter:

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)
	...

There is an improvement (KARAF-1300) that addressed a similar situlation in a different component, so why not make JMXSecurityMBean robust as well?