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

Michael Prieß updated CAMEL-6297:
---------------------------------

    Description: 
Hi, 

the latest implementation used the fixed default domain which doesn't work if 
you specify a custom agent. I removed the fixed default domain name and used 
the method ManagementAgent.getMBeanObjectDomainName() instead.

In addition I added the attribute InflightExchanges to the route-info command 
because i really missed. Would be great if the patch could be integrated into 
2.12.

Cheers,

Michael

  was:
Hi, 

the latest implementation used the fixed default domain which doesn't work if 
you specify a custom agent. I removed the fixed default domain name and used 
the method ManagementAgent.getMBeanObjectDomainName() instead.

In addition I added the attribute InflightExchanges to the route-info command 
because i missed it a little bit. Would be great if the patch could be 
integrated into 2.12.

Cheers,

Michael

    
> Commands doesn't support a custom JMX Agent
> -------------------------------------------
>
>                 Key: CAMEL-6297
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6297
>             Project: Camel
>          Issue Type: Bug
>          Components: karaf
>    Affects Versions: 2.10.4
>            Reporter: Michael Prieß
>             Fix For: 2.12.0
>
>         Attachments: agent_bug.diff, route.xml
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Hi, 
> the latest implementation used the fixed default domain which doesn't work if 
> you specify a custom agent. I removed the fixed default domain name and used 
> the method ManagementAgent.getMBeanObjectDomainName() instead.
> In addition I added the attribute InflightExchanges to the route-info command 
> because i really missed. Would be great if the patch could be integrated into 
> 2.12.
> Cheers,
> Michael

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to