[JIRA] Created: (LBCLASSIC-142) Rolling must be thread safe
Rolling must be thread safe --------------------------- Key: LBCLASSIC-142 URL: http://jira.qos.ch/browse/LBCLASSIC-142 Project: logback-classic Issue Type: Sub-task Affects Versions: 0.9.16 Reporter: Ceki Gulcu Assignee: Logback dev list Priority: Blocker Rolling should be thread safe. Recent changes in code have undermined thread safety during rolling. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-142?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu resolved LBCLASSIC-142. ---------------------------------- Fix Version/s: 0.9.16 Resolution: Fixed Fixes as of revision 2329
Rolling must be thread safe ---------------------------
Key: LBCLASSIC-142 URL: http://jira.qos.ch/browse/LBCLASSIC-142 Project: logback-classic Issue Type: Sub-task Affects Versions: 0.9.16 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Priority: Blocker Fix For: 0.9.16
Rolling should be thread safe. Recent changes in code have undermined thread safety during rolling.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-142?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu commented on LBCLASSIC-142: -------------------------------------- The changes breaking thread safety were not visible in any distributed version of logback. "Recent changes" really means logback 0.9.16-SNAPSHOT.
Rolling must be thread safe ---------------------------
Key: LBCLASSIC-142 URL: http://jira.qos.ch/browse/LBCLASSIC-142 Project: logback-classic Issue Type: Sub-task Affects Versions: 0.9.16 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Priority: Blocker Fix For: 0.9.16
Rolling should be thread safe. Recent changes in code have undermined thread safety during rolling.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[ http://jira.qos.ch/browse/LBCLASSIC-142?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu edited comment on LBCLASSIC-142 at 7/9/09 1:53 PM: -------------------------------------------------------------- Fixed as of revision 2329 was (Author: noreply.ceki@qos.ch): Fixes as of revision 2329
Rolling must be thread safe ---------------------------
Key: LBCLASSIC-142 URL: http://jira.qos.ch/browse/LBCLASSIC-142 Project: logback-classic Issue Type: Sub-task Affects Versions: 0.9.16 Reporter: Ceki Gulcu Assignee: Ceki Gulcu Priority: Blocker Fix For: 0.9.16
Rolling should be thread safe. Recent changes in code have undermined thread safety during rolling.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
participants (1)
-
Ceki Gulcu (JIRA)