Back to bug 1031221
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Kyle Lape | 2013-11-15 23:51:35 UTC | Blocks | 1031229 | |
| Brian Stansberry | 2013-12-10 22:48:16 UTC | CC | brian.stansberry | |
| Brad Maxwell | 2014-01-09 04:36:54 UTC | Depends On | 1050779 | |
| Brad Maxwell | 2014-01-09 04:38:42 UTC | Blocks | 1050779 | |
| Depends On | 1050779 | |||
| Brad Maxwell | 2014-01-09 04:51:54 UTC | Status | NEW | MODIFIED |
| CC | bmaxwell | |||
| Brad Maxwell | 2014-01-09 04:52:20 UTC | Target Release | --- | EAP 6.2.1 |
| mark yarborough | 2014-01-13 13:21:52 UTC | CC | myarboro | |
| Summary | LogContext's root logger is not created with a strong child hash map when strong=true | [GSS] (6.2.x) LogContext's root logger is not created with a strong child hash map when strong=true | ||
| Brad Maxwell | 2014-01-13 13:27:09 UTC | Blocks | 1027004 | |
| Brad Maxwell | 2014-01-13 13:30:39 UTC | Depends On | 1052198 | |
| Brad Maxwell | 2014-01-13 13:37:49 UTC | Blocks | 1050779 | |
| Carlo de Wolf | 2014-01-16 15:13:40 UTC | CC | marc.balsys | |
| Target Milestone | --- | CR1 | ||
| Vaclav Tunka | 2014-01-20 22:17:45 UTC | Status | MODIFIED | ON_QA |
| Scott Mumford | 2014-01-21 03:26:59 UTC | CC | smumford | |
| Scott Mumford | 2014-01-24 01:20:12 UTC | Version | TBD EAP 6 | 6.2.0 |
| Scott Mumford | 2014-01-28 00:31:34 UTC | CC | jperkins | |
| Doc Text | Cause: ??? Consequence: LogContext loses the reference and the configuration for the custom logger is lost. Fix: ??? Result: Custom loggers are now honored as expected. | |||
| Flags | needinfo?(jperkins) | |||
| James Perkins | 2014-01-28 01:06:36 UTC | Doc Text | Cause: ??? Consequence: LogContext loses the reference and the configuration for the custom logger is lost. Fix: ??? Result: Custom loggers are now honored as expected. | Cause: Loggers are sometimes garbage collected early resulting in loss of the loggers and configuration. For example if a logger had an appender assigned, when the logger is garbage collected a new logger would have been created without the appender attached. Consequence: LogContext loses the reference and the configuration for the custom logger is lost. Fix: The map of loggers was changed to use a strong reference rather than a weak reference. This causes the loggers not to get garbage collected and things to work as they should. Result: Custom loggers are now honored as expected. |
| Flags | needinfo?(jperkins) | |||
| Scott Mumford | 2014-01-28 03:54:25 UTC | Doc Text | Cause: Loggers are sometimes garbage collected early resulting in loss of the loggers and configuration. For example if a logger had an appender assigned, when the logger is garbage collected a new logger would have been created without the appender attached. Consequence: LogContext loses the reference and the configuration for the custom logger is lost. Fix: The map of loggers was changed to use a strong reference rather than a weak reference. This causes the loggers not to get garbage collected and things to work as they should. Result: Custom loggers are now honored as expected. | In previous versions of JBoss EAP 6, it was found that loggers were sometimes garbage collected early resulting in loss of the loggers and configuration. For example, if a logger had an appender assigned, when the logger is garbage collected a new logger would have been created without the appender attached. In this release of the product, the map of loggers has been changed to use a strong reference rather than a weak reference. This causes the loggers not to get garbage collected and things to work as they should. As a result custom loggers are now honored as expected. |
| Petr Kremensky | 2014-01-31 08:18:26 UTC | Status | ON_QA | VERIFIED |
| CC | pkremens | |||
| mark yarborough | 2014-02-24 20:15:42 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-02-24 15:15:42 UTC |
Back to bug 1031221