Serguei
March 7th, 2001, 09:24 AM
Hi, guys:
while testing our new ASP app got a terrible problem. ASP is working with one of our client com components; the latter is making a call into one of the server components. The server component submits a message to another freethreaded out-of-proc guy. The guy calls back into the asp client component( the one that initiated the whole procedure ). Well, can you imagine that this last call happens at the same time when the call from client to server is still not finished and...it blocks it( in fact we are having a dead lock ). After 3 minutes everything is done properly only we obviously get a message in the browser that our script expired. In the process of debugging we got a "new" HRESULT message that reads "The component is configured to use synchronization and a thread has timed out waiting to ented the context". Could not find any information on this one. This HRESULT we get from the method that is trying to access client causing call from the client to server to hang. Any ideas? Needless to say that the same stuff with clients written in VB or C++ works great.
Thank you,
Serguei
while testing our new ASP app got a terrible problem. ASP is working with one of our client com components; the latter is making a call into one of the server components. The server component submits a message to another freethreaded out-of-proc guy. The guy calls back into the asp client component( the one that initiated the whole procedure ). Well, can you imagine that this last call happens at the same time when the call from client to server is still not finished and...it blocks it( in fact we are having a dead lock ). After 3 minutes everything is done properly only we obviously get a message in the browser that our script expired. In the process of debugging we got a "new" HRESULT message that reads "The component is configured to use synchronization and a thread has timed out waiting to ented the context". Could not find any information on this one. This HRESULT we get from the method that is trying to access client causing call from the client to server to hang. Any ideas? Needless to say that the same stuff with clients written in VB or C++ works great.
Thank you,
Serguei