[jira] [Resolved] (DAFFODIL-2510) Thread Safety: Improve Logger/Logging

["Steve Lawrence (Jira)" <ji...@apache.org>]

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

Steve Lawrence resolved DAFFODIL-2510.
--------------------------------------
    Fix Version/s: 3.2.0
       Resolution: Fixed

Fixed in commit 51b814e5b82f6d103e9d52ff22a0661e0d7c8884

Switched al logging to Log4j

> Thread Safety: Improve Logger/Logging 
> --------------------------------------
>
>                 Key: DAFFODIL-2510
>                 URL: https://issues.apache.org/jira/browse/DAFFODIL-2510
>             Project: Daffodil
>          Issue Type: Bug
>          Components: Back End, CLI, Front End, Libraries, Middle "End", TDML Runner
>    Affects Versions: 3.0.0
>            Reporter: Mike Beckerle
>            Assignee: Steve Lawrence
>            Priority: Major
>             Fix For: 3.2.0
>
>
> Every object that mixes in the Logging trait gets its own mutable vars for logWriter and logLevel, and if not set, shares a single global state in the LoggingDefaults object.
> This is not thread safe. At minimum LoggingDefaults should be a ThreadLocal.
> Furthermore, those objects don't need independent ability to specify a unique logger or logging level. They should be sharing a logger supplied by the application.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)