camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Babak Vahdat (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-4938) ManagedBrowsableEndpoint are broken
Date Mon, 30 Jan 2012 15:18:10 GMT


Babak Vahdat updated CAMEL-4938:

    Attachment: org.apache.camel.component.jms.BrowsableQueueTest.jpg


thanks beforehand for providing & applying the patch which indeed resolved the problem,
however the solution
is to my understanding is not *generic* as we've now introduced SEDA Endpoint specific logic
into DefaultManagementObjectStrategy:

        } else if (endpoint instanceof SedaEndpoint) {
            ManagedSedaEndpoint me = new ManagedSedaEndpoint((SedaEndpoint) endpoint);
            return me;

And have also introduced a ManagedSedaEndpoint which is again *Endpoint specific*, IMHO not

Another note: by enableing JMX on


I see that the JMX operations are enlisted twice, causing (almost) the same behaviour (see
the attached screenshot).

Shouldn't we remove the ManagedResource & ManagedOperation annotations on JmsQueueEndpoint
as well? The same as you did for SedaEndpoint?
> ManagedBrowsableEndpoint are broken
> -----------------------------------
>                 Key: CAMEL-4938
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, jmx
>    Affects Versions: 2.9.0
>            Reporter: Vid Cheruvu
>            Assignee: Babak Vahdat
>             Fix For: 2.9.1, 2.10.0
>         Attachments: CAMEL-4938.patch, org.apache.camel.component.jms.BrowsableQueueTest.jpg
> ManagedeBrowsableEndpoint are broken which means any component that inherit ManagedBrowsableEndpoint
have errors as well. Please see the link below which will have error screen shot of queueSize
JMX operations.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message