Hi Guys (Konstantin, Mladen), goo d work, sorry caught me on a Sunday, else I would have chipped in.
Just wondering (thinking a bit left field), but question was asked of me. Any reason to have a shm across processes. We already have threading inside each worker process. What are the benefits of connection pool sharing across process, compared to just keeping them in process. Alex > -----Original Message----- > From: Mladen Turk [mailto:mt...@apache.org] > Sent: Monday, 19 March 2012 4:39 AM > To: users@tomcat.apache.org > Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI > redirector 1.2.33 > > On 03/18/2012 03:11 PM, Konstantin Preißer wrote: > > Hi Mladen, > > > >> -----Original Message----- > >> From: Mladen Turk [mailto:mt...@apache.org] > >> Sent: Sunday, March 18, 2012 2:54 PM > >> To: Tomcat Users List > >> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling > >> since ISAPI redirector 1.2.33 > >> > >> > >> Please use isapi_redirect_1.2.34_3-dev_winXX.zip instead. > > > > Thank you. > > > > I tried with isapi_redirect_1.2.34_3-dev_win32.zip, but unfortunately > > it seems that it causes w3wp.exe to crash again :( > > > > Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip > If this one crashes we'll have to add some override to shared memory so we > can fallback to heap one and bypass memory corruption which seems to > occur at IIS worker recycle. > > > Regards > -- > ^TM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org
