Mailing-List: contact bugs-help@apr.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apr.apache.org
From: bugzilla@apache.org
To: bugs@apr.apache.org
Subject: DO NOT REPLY [Bug 43876]  - Thread pooling has thread safety/race
 condition errors
In-Reply-To: <bug-43876-43213@http.issues.apache.org/bugzilla/>
Message-Id: <20071116231800.0C97F714249@brutus.apache.org>
Date: Fri, 16 Nov 2007 15:17:59 -0800 (PST)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=43876>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=43876


------- Additional Comments From Joe.Mudd@sas.com  2007-11-16 15:17 -------
Isn't it true that the TH_PROBATION threads can wake up independently of their 
condition variable being posted?  And if so, couldn't they wake up after the 
UNSPLICE but before the TH_STOP setting, acquire the me->lock and get around to 
the top of the loop before TH_STOP is set by the code in trim_threads() that is 
running outside of the me->lock protection?

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@apr.apache.org
For additional commands, e-mail: bugs-help@apr.apache.org