activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQNET-51) Tracer class does not properly check enabled status flags for different output levels
Date Wed, 13 Feb 2008 00:32:35 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Gomes closed AMQNET-51.
---------------------------

    Resolution: Fixed

> Tracer class does not properly check enabled status flags for different output levels
> -------------------------------------------------------------------------------------
>
>                 Key: AMQNET-51
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-51
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ Client
>         Environment: Windows XP SP2, .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>            Priority: Minor
>   Original Estimate: 15 minutes
>  Remaining Estimate: 15 minutes
>
> In the ActiveMQ.Tracer class, the static properties for IsInfoEnabled, IsWarnEnabled,
IsErrorEnabled, IsFatalEnabled do not check their individual status flags to see if they are
enabled.  They all check the single IsDebugEnabled status flag.  This means that none of them
will be turned on unless the IsDebugEnabled flag is true.  Conversely, they will *all* be
enabled if the IsDebugEnabled flag is true.  They should each check their own status flags
to enable fine-grained control over Tracer output.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message