You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by "Knut Urdalen (JIRA)" <ji...@apache.org> on 2009/05/05 22:33:36 UTC
[jira] Created: (LOG4PHP-43) Remove size restriction of MDC table
in LoggerMDC
Remove size restriction of MDC table in LoggerMDC
-------------------------------------------------
Key: LOG4PHP-43
URL: https://issues.apache.org/jira/browse/LOG4PHP-43
Project: Log4php
Issue Type: Improvement
Components: Code
Reporter: Knut Urdalen
Assignee: Knut Urdalen
Priority: Minor
Fix For: 2.0
The mapped diagnostic context is currently allowed to only store 7 context variables. Even though this should be enough in most cases, why should we do a hard limit here? Also checked MDC.java in log4j and there it seems only to be used for initializing the initial size of the HashTable which is used as storage (not limiting to how many context variables you are allowed to store).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (LOG4PHP-43) Remove size restriction of MDC table
in LoggerMDC
Posted by "Christian Grobmeier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christian Grobmeier resolved LOG4PHP-43.
----------------------------------------
Resolution: Fixed
fixed with rv 795658
> Remove size restriction of MDC table in LoggerMDC
> -------------------------------------------------
>
> Key: LOG4PHP-43
> URL: https://issues.apache.org/jira/browse/LOG4PHP-43
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Reporter: Knut Urdalen
> Assignee: Knut Urdalen
> Priority: Minor
> Fix For: 2.0
>
> Attachments: 43-LoggerMDC.patch
>
>
> The mapped diagnostic context is currently allowed to only store 7 context variables. Even though this should be enough in most cases, why should we do a hard limit here? Also checked MDC.java in log4j and there it seems only to be used for initializing the initial size of the HashTable which is used as storage (not limiting to how many context variables you are allowed to store).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LOG4PHP-43) Remove size restriction of MDC table
in LoggerMDC
Posted by "Knut Urdalen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/LOG4PHP-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Urdalen updated LOG4PHP-43:
--------------------------------
Attachment: 43-LoggerMDC.patch
> Remove size restriction of MDC table in LoggerMDC
> -------------------------------------------------
>
> Key: LOG4PHP-43
> URL: https://issues.apache.org/jira/browse/LOG4PHP-43
> Project: Log4php
> Issue Type: Improvement
> Components: Code
> Reporter: Knut Urdalen
> Assignee: Knut Urdalen
> Priority: Minor
> Fix For: 2.0
>
> Attachments: 43-LoggerMDC.patch
>
>
> The mapped diagnostic context is currently allowed to only store 7 context variables. Even though this should be enough in most cases, why should we do a hard limit here? Also checked MDC.java in log4j and there it seems only to be used for initializing the initial size of the HashTable which is used as storage (not limiting to how many context variables you are allowed to store).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.