https://issues.apache.org/bugzilla/show_bug.cgi?id=47750
--- Comment #5 from robert.ma...@capita.co.uk 2009-09-01 12:15:31 PDT --- (In reply to comment #1) > I can easily prevent that efect (the > zeroing of the shared memory), but it would be more correct, if the second > process actually got the right data from the already existing shared memory. I did try zeroing the data to start with, but yes, it's not ideal for the worker status/changes to not be persistent when the second process starts! > Are you using web gardens and/or application pools? Which one of those and how > are they configured? Just running it out of the DefaultAppPool. Recycle worker processes set to 1740 minutes; Shutdown idle worker processes after being idle for 20 minutes; Limit kernel requests to 100; Maximum number of worker processes in the webgarden is set to 1. Pinging is enabled and set to 30 seconds. Rapid-fail protection is set to 5 failures in 5 minutes. Startup and shutdown time limits are set to 90 seconds. Process is running as Network Service. There are other applications running in the DefaultAppPool - I'm not sure if these could be influencing the second process starting? > Could you please also provide your workers.properties and > uriworkermap.properties as well as the isapi_redirect.properties. Have attached these to the bug report. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
