The hex-number is the instanceId to avoid the name conflict.
If you want to get ride of it, you need to make sure the service is a StaticService which means you have only one instance per Camel Context.

You can find the below code in the DefaultManagementNamingStrategy.

public ObjectName getObjectNameForService(CamelContext context, Service service) throws MalformedObjectNameException {
        StringBuilder buffer = new StringBuilder();
        buffer.append(KEY_CONTEXT + "=").append(getContextId(context)).append(",");
        buffer.append(KEY_TYPE + "=" + TYPE_SERVICE + ",");
        buffer.append(KEY_NAME + "=").append(service.getClass().getSimpleName());
        if (!(service instanceof StaticService)) {
        return createObjectName(buffer);

Willem Jiang

Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On March 17, 2015 at 12:31:06 AM, dermoritz (tanteanni@hotmail.com) wrote:
I created some custom MBeans (implementing Service). they work as they should
but for some reason their names have some hexadecimal number at the end e.g.
"JmxController (0x32e652b6)". Is there a way to get rid of this number? What
does this number mean - only my custom "Services" have such a number?

View this message in context: http://camel.465427.n5.nabble.com/Names-of-custom-MBeans-contain-hex-number-at-the-end-tp5764226.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 3 | next ›
Discussion Overview
groupusers @
postedMar 16, '15 at 4:31p
activeMar 17, '15 at 7:59a

2 users in discussion

Dermoritz: 2 posts Willem Jiang: 1 post



site design / logo © 2022 Grokbase