• Type: Enhancement
• Resolution: Unresolved
• Priority: Major
• Fix Version/s: None
• Affects Version/s: 6.0.0.Final
• Component/s: Logging
• Labels:

  None

[JBAS-9467] The JMX Bean associated with a LogContext must be made available

Collapse comment: Leonid Kosmylev (Inactive) added a comment - 2011/09/23 6:57 AM, Edited by Leonid Kosmylev - 2011/09/23 6:58 AM

Leonid Kosmylev (Inactive) added a comment - 2011/09/23 6:57 AM - edited

There is a workaround. It is published here: http://lea-ka.blogspot.com/2011/09/dynamically-changing-app-specific.html

I guess the easiest way to fix this issue is to change class org.jboss.logging.metadata.LoggingMetaDataHelper, method createBeanMetaData.
This piece of code makes sure the required log contexts are created:

        if (defineContextMetaDataList != null) for (DefineContextMetaData defineContextMetaData : defineContextMetaDataList) {
            final String contextName = defineContextMetaData.getName();
            final BeanMetaDataBuilder builder = BeanMetaDataBuilder.createBuilder(getContextName(contextName == null ? context : contextName), LogContext.class.getName());
            builder.setFactoryMethod("create");
            beanMetaDataList.add(builder.getBeanMetaData());
        }

The fix would change the code so that not only the context is created but also its MBean is registered, more or less in line with the published workaround.

Expand comment: Leonid Kosmylev (Inactive) added a comment - 2011/09/23 6:57 AM, Edited by Leonid Kosmylev - 2011/09/23 6:58 AM

Leonid Kosmylev (Inactive) added a comment - 2011/09/23 6:57 AM - edited There is a workaround. It is published here: http://lea-ka.blogspot.com/2011/09/dynamically-changing-app-specific.html I guess the easiest way to fix this issue is to change class org.jboss.logging.metadata.LoggingMetaDataHelper, method createBeanMetaData. This piece of code makes sure the required log contexts are created: if (defineContextMetaDataList != null ) for (DefineContextMetaData defineContextMetaData : defineContextMetaDataList) { final String contextName = defineContextMetaData.getName(); final BeanMetaDataBuilder builder = BeanMetaDataBuilder.createBuilder(getContextName(contextName == null ? context : contextName), LogContext. class. getName()); builder.setFactoryMethod( "create" ); beanMetaDataList.add(builder.getBeanMetaData()); } The fix would change the code so that not only the context is created but also its MBean is registered, more or less in line with the published workaround.