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=40877>. 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=40877 ------- Additional Comments From [EMAIL PROTECTED] 2006-11-15 15:15 ------- (In reply to comment #5) > Created an attachment (id=19133) --> (http://issues.apache.org/bugzilla/attachment.cgi?id=19133&action=view) [edit] > WIN64/AMD64 ISAPI Redirect > > isapi_redirect 1.2.20 with shared memory patch Hi Mladen, We are having similar sort of issue on Win32 Platform. I will explain in detail. Environment We are running MS Application Center Load Balanced Web Server Farm with 3 nodes running IIS 6 in Worker Process Isolation mode. The Tomcat/JBoss runs on two separate Servers (again Load Balanced via Application Center). The Web Server Farm is running 5 Websites. The JK ISAPI redirector version is 1.2.19 and is configured on per site basis. Problem Everything works fine except when the application pool undergoes recycling, the website using that application pool wouldn't work. Recycling application pool again, restarting website wouldn't help. The request to that website gets 404.2 and 404.3 in IIS logs. The 404.2 indicates that JK ISAPI is locked or access is denied to the JK ISAPI. The only way to get it working again is to do an IISRESET which affects all other websites and disconnects all the users connected to those websites. Its very frustrating as the whole purpose of IIS 6 running in worker process isolation mode is defeated. The JK Logs shows the following [Wed Nov 15 17:25:41 2006] [1228:4924] [error] jk_worker.c (256): failed to create worker lbworker [Wed Nov 15 17:49:24 2006] [2332:2232] [error] jk_worker.c (146): factory for lb failed for lbworker [Wed Nov 15 17:49:24 2006] [2332:2232] [error] jk_worker.c (256): failed to create worker lbworker [Wed Nov 15 18:31:12 2006] [4756:4804] [error] jk_worker.c (146): factory for lb failed for lbworker [Wed Nov 15 18:31:12 2006] [4756:4804] [error] jk_worker.c (256): failed to create worker lbworker [Wed Nov 15 18:57:02 2006] [4044:6564] [error] jk_worker.c (146): factory for lb failed for lbworker [Wed Nov 15 18:57:02 2006] [4044:6564] [error] jk_worker.c (256): failed to create worker lbworker [Wed Nov 15 18:57:24 2006] [0324:6956] [error] jk_worker.c (146): factory for lb failed for lbworker [Wed Nov 15 18:57:24 2006] [0324:6956] [error] jk_worker.c (256): failed to create worker lbworker [Wed Nov 15 18:57:32 2006] [3660:5948] [error] jk_worker.c (146): factory for lb failed for lbworker [Wed Nov 15 18:57:32 2006] [3660:5948] [error] jk_worker.c (256): failed to create worker lbworker The windows eventlog would show the following: Event Type: Information Event Source: W3SVC Event Category:None Event ID: 1074 Date: 15.11.2006 Time: 06:56:36 User: N/A Computer: xxxxxxxxxxxxx Description: A worker process with process id of '6308' serving application pool 'xxxxx' has requested a recycle because the worker process reached its allowed processing time limit. We didn't have any issues with the earlier version of JK which was 1.2.08. I have a strong feeling that this has to do with the shared memory problem. Please let me know if you need any further information, config files or log files. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
