Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sat, 19 Jul 2014 16:04:38 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12726107.1404833344314.2447.1405785878527@arcas>
In-Reply-To: <JIRA.12726107.1404833344314@arcas>
References: <JIRA.12726107.1404833344314@arcas>
Subject: [jira] [Updated] (CAMEL-7586) NotCompliantMBeanException :
 Attribute MessageHistory has more than one getter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CAMEL-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-7586:
-------------------------------

    Priority: Minor  (was: Major)

> NotCompliantMBeanException : Attribute MessageHistory has more than one getter
> ------------------------------------------------------------------------------
>
>                 Key: CAMEL-7586
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7586
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, jmx
>    Affects Versions: 2.12.3, 2.13.0
>            Reporter: Lefillastre Alexandre
>            Priority: Minor
>             Fix For: 2.12.5, 2.13.3, 2.14.0
>
>
> Hello, I wasn't able to subscribe on the mailing list, so I'm posting my issue directly here.
> In my project I need to use some _ManagedCamelContextMBean_, which I am trying to access through [JMX.newMBeanProxy|http://docs.oracle.com/javase/8/docs/api/javax/management/JMX.html#newMBeanProxy-javax.management.MBeanServerConnection-javax.management.ObjectName-java.lang.Class-]
> However, it is not working as I'm getting a *NotCompliantMBeanException* because the attribute _MessageHistory_ is said to have more than one getter.
> I checked the source code of newMBeanProxy, then the [JMX 1.4 specification|http://docs.oracle.com/javase/8/docs/technotes/guides/jmx/JMX_1_4_specification.pdf], and then Camel's source code, and it appears that ManagedCamelContextMBean is indeed not respecting the standard MBean.
> The problem is that two methods are defined in _ManagedCamelContextMBean_ : isMessageHistory() and getMessageHistory()
> Since the return type is boolean, isMessageHistory is considered to be a getter, which makes two getter according to the JMX specification and is blocking the newMBeanProxy() method.


--
This message was sent by Atlassian JIRA
(v6.2#6252)