You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2007/07/04 15:30:55 UTC
DO NOT REPLY [Bug 11997] - NT MPM assertion "(rv >= 0) && (rv < threads_created)" failed
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=11997>.
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=11997
------- Additional Comments From stephen.johnston@guildlaunch.com 2007-07-04 06:30 -------
We are seeing the same problem with 2.0.59. We have been encountering steadily
bloating threads on Windows. This seems to make sense if you consider that
Apache threads grow to the size of what they server and do not release the
memory.
In an attempt to manage that problem we set MaxRequestsPerChild to 100
temporarily so we could watch the effect on the server before setting it to a
more reasonable number. Upon the first "exit due to maxrequestsperchild" this
error was thrown and the server stopped serving threads.
While the bloat may be a bug or a design with unintended consquences, the real
issue is that now on Windows there seems to be no effective way to recycle the
server and free up the memory short of regular service restarts.
--
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@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org