tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 36102] - jk 1.2.14 - Worker actions do not persist
Date Tue, 16 Aug 2005 23:26:05 GMT
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=36102>.
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=36102





------- Additional Comments From rainer.jung@kippdata.de  2005-08-17 01:26 -------
No solution but a remark: The observation, that you don't see the problem when
reloading/refreshing the page might come from the fact, that he chang i done via
 GET request, so refreshing the page again sends the request including all
parameters, so the change is applied a second time.

I don't know much about IIS, but maybe you can limit the number of threads to
some low count (e.g. 5 or 10) and then check the status of the stopped worker
not only once or twice but 10 to 20 times and check, if it is non-stopped all
the time, or sporadically stopped.

-- 
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: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message