[ 
https://issues.apache.org/jira/browse/KARAF-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277709#comment-15277709
 ] 

ASF subversion and git services commented on KARAF-4523:
--------------------------------------------------------

Commit 0e8cfd9a97a54f26d7fea4f409768a538f36db1e in karaf's branch 
refs/heads/karaf-4.0.x from [~tadayosi]
[ https://git-wip-us.apache.org/repos/asf?p=karaf.git;h=0e8cfd9 ]

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

This fix is based on the original patch by Grzegorz Grzybek

(cherry picked from commit 1fff0131967ac11b0a481f503fbc952f777fc30d)


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

Reply via email to