For an ISAPI filter you need to assume that you can have multiple threads
entering any given function at a time. The filter is responsible for it's
internal data structures and ensuring that synchronization (via whatever
locking mechanism is appropriate). A filter may also create it's own thread
pool and post work to those threads, but if it does so then it must also
handle the re-synching of the response.
I think you need to debug the filter and determine the root cause of the
load problem. There is no indication that the problem is with threading or
locking or what have you any more than any other possible cause - potential
corruption that only manifests itself after 'X' hits where X is reached much
faster under load.
Pat
"Chandra Sekhar" <darbha.sekhar.TakeThisOut@gmail.com> wrote in message
news:1140611238.017490.20050@g43g2000cwa.googlegroups.com...
> Hi,
>
> I have created a simple ISAPI filter which will do a 302 Redirect to a
> new URL generated by manipulating the requested URL. When i test this
> ISAPI on IIS under Load testing then the test clients are showing
> 'zero' response time after first three minutes. At this point of time i
> also tried to check manually doubting whether that is because of any
> error. when i browsed manually i received an "Internal Server Error".
>
> I have done locking in the ISAPI using Critical Sections as i have seen
> some mixing of request URLs when it performs the manipulation on the
> requested URL.
>
> Should we make our own locking or threading mechanism or IIS will take
> care of this threading?
>
> I felt the ISAPI filter might have got crashed. Is this the reason or
> something else. Can somebody tell me how to diagnose this problem ?
>
> Thanks in advance.
>
FAQ
Search
Profile
Private Messages
Log in/Register/Password
