You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2015/05/14 17:14:00 UTC

[jira] [Created] (TS-3603) Debug Assert occurs in UnixNetVConnection::set_enabled when accept_threads are disabled

Susan Hinrichs created TS-3603:
----------------------------------

             Summary: Debug Assert occurs in UnixNetVConnection::set_enabled when accept_threads are disabled
                 Key: TS-3603
                 URL: https://issues.apache.org/jira/browse/TS-3603
             Project: Traffic Server
          Issue Type: Bug
          Components: Network
            Reporter: Susan Hinrichs


This was found while tracking down TS-3597.  The assert stack is in a comment on that bug.

When you don't have a dedicated assert thread, the mutex is not locked before going into the do_io_read to process the accept event.  In the dedicated thread case, you end up exercising UnixNetVConnection::acceptEvent which does grab the mutex.

May be a relatively harmless error.  Since this is a newly created VC, there should be no race conditions on it.  But violating locking assumptions seem like a really bad idea.  Especially since grabbing a lock on a supposedly uncontended object should be cheap.

A 5.3.x patch is attached to this bug which solves the problem on my build.



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