[JBoss JIRA] Created: (JBLOGGING-71) The JMX Bean associated with a LogContext must be made available
5:47 a.m.
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: JBLOGGING-71
URL: https://issues.jboss.org/browse/JBLOGGING-71
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Assignee: David Lloyd
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBLOGGING-71) The JMX Bean associated with a LogContext must be made available
[
https://issues.jboss.org/browse/JBLOGGING-71?page=com.atlassian.jira.plug...
]
Leonid Kosmylev edited comment on JBLOGGING-71 at 9/23/11 6:58 AM:
-------------------------------------------------------------------
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:
{code:java}
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());
}
{code}
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.
was (Author: klv_m72):
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.
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: JBLOGGING-71
URL: https://issues.jboss.org/browse/JBLOGGING-71
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Assignee: David Lloyd
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:59 a.m.
New subject: [JBoss JIRA] Updated: (JBLOGGING-71) The JMX Bean associated with a LogContext must be made available
[
https://issues.jboss.org/browse/JBLOGGING-71?page=com.atlassian.jira.plug...
]
Leonid Kosmylev updated JBLOGGING-71:
-------------------------------------
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.
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: JBLOGGING-71
URL: https://issues.jboss.org/browse/JBLOGGING-71
Project: JBoss Logging
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Assignee: David Lloyd
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9 a.m.
New subject: [JBoss JIRA] Moved: (LOGMGR-31) The JMX Bean associated with a LogContext must be made available
[
https://issues.jboss.org/browse/LOGMGR-31?page=com.atlassian.jira.plugin....
]
David Lloyd moved JBLOGGING-71 to LOGMGR-31:
--------------------------------------------
Project: JBoss Log Manager (was: JBoss Logging)
Key: LOGMGR-31 (was: JBLOGGING-71)
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: LOGMGR-31
URL: https://issues.jboss.org/browse/LOGMGR-31
Project: JBoss Log Manager
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Assignee: David Lloyd
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [JBoss JIRA] (JBAS-9467) The JMX Bean associated with a LogContext must be made available
[
https://issues.jboss.org/browse/JBAS-9467?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-9467:
------------------------------
Assignee: (was: David Lloyd)
Affects Version/s: 6.0.0.Final
Component/s: Logging
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: JBAS-9467
URL: https://issues.jboss.org/browse/JBAS-9467
Project: Application Server 3 4 5 and 6
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 6.0.0.Final
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [JBoss JIRA] (JBAS-9467) The JMX Bean associated with a LogContext must be made available
[
https://issues.jboss.org/browse/JBAS-9467?page=com.atlassian.jira.plugin....
]
David Lloyd moved LOGMGR-31 to JBAS-9467:
-----------------------------------------
Project: Application Server 3 4 5 and 6 (was: JBoss Log Manager)
Key: JBAS-9467 (was: LOGMGR-31)
The JMX Bean associated with a LogContext must be made available
----------------------------------------------------------------
Key: JBAS-9467
URL: https://issues.jboss.org/browse/JBAS-9467
Project: Application Server 3 4 5 and 6
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Logging
Affects Versions: 6.0.0.Final
Environment: JBoss AS 6.0.0
Reporter: Leonid Kosmylev
Assignee: David Lloyd
Class org.jboss.logmanager.LogContext has an associated instance of LoggingMXBeanImpl. If
per-application logging is enabled a new instances of LogContext and LoggingMXBeanImpl
are created. But the LoggingMXBeanImpl is not registered as an MBean. It is therefore not
possible to change log levels dynamically.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4678
days inactive
4796
days old
5 comments
2 participants
participants (2)
-
David Lloyd (JIRA) -
Leonid Kosmylev (JIRA)