You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/20 20:45:20 UTC

[jira] [Work logged] (TS-4072) Diagnostic log rolling races

     [ https://issues.apache.org/jira/browse/TS-4072?focusedWorklogId=25776&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-25776 ]

ASF GitHub Bot logged work on TS-4072:
--------------------------------------

                Author: ASF GitHub Bot
            Created on: 20/Jul/16 20:44
            Start Date: 20/Jul/16 20:44
    Worklog Time Spent: 10m 
      Work Description: Github user zwoop commented on the issue:

    https://github.com/apache/trafficserver/pull/568
  
    Well, this slipped through the net. @danobi  Can you please make an update to the PR, that does not have merge conflicts?


Issue Time Tracking
-------------------

            Worklog Id:     (was: 25776)
            Time Spent: 10m
    Remaining Estimate: 0h

> Diagnostic log rolling races
> ----------------------------
>
>                 Key: TS-4072
>                 URL: https://issues.apache.org/jira/browse/TS-4072
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging
>            Reporter: James Peach
>            Assignee: Alan M. Carroll
>             Fix For: 7.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When diagnostic logs are rolled, {{Diags::diags_log}} is deleted and replaced with a new log object. Since the global {{diags}} points to a a single {{Diags}} object there is nothing to prevent a different thread logging through this object at the time it is deleted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)