Unless IIS 6 is set in IIS 5 isolation mode, changes like disabling or stopping a worker using the JK Status Manager do not appear to "hold" or persist across multiple browser sessions.
Environment: Server 2003, Tomcat 4.1.27, jk1.2.14 Scenario: open jkstatus page in any browser (tested IE5, IE6, Netscape 8, Firefox 1.0.6) click on the worker name, complete the "Disabled" check box and click Update Worker. Worker status changes to Disabled as expected. Click on the same worker name a second time and the worker status reverts to OK. This behavior is also seen if you open the same jkstatus page in another browser. This appears to be an offshoot of the ""worker process isolation mode" that is a part of IIS 6 in a Server 2003 environment. Changing to IIS 5's isolation mode seems to resolve the "problem", at least for me. For more information, refer to bug #36102. This issue is being posted on Tomcat-Dev at the Connector developer's request.
