|
Home > Archive > IIS Server > June 2005 > IIS 6.0 and COM lockout
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
IIS 6.0 and COM lockout
|
|
|
| BACKGROUND
I have an web based application that is using ASP, SOAP and COM Objects that
reside on a web Server.
These COM objects are used to perform LIST/ADD/EDIT/DELETE items from a
database on another Server.
The SOAP technology is used by creating a SOAP object on the ASP page and
initiating it with a SOAP WSDL file, from which the API calls are executed.
The Web Server is Windows 2003 and using IIS 6.0
ISSUE:
The web based application functions correctly all day until approx 4.00pm of
the working day. (Working day: 9.00 - 5.00, Mon - Fri)
At this point, none of my COM objects will operate and the API calls are not
being sent to the Server.
The Web Application will display all other pages that do not use these COM
objects and these pages will function correctly.
I created a test Application on the Web Server machine to test the COM API's
which reside on the Web Server (therefore I am not using IIS to execute the
API) and it worked successfully. This verified that the COM API's are
functioning and the calls are executed to the DB on another Server.
If I perform an iisreset before the issue occurs at approx 4.00 pm, then the
issue does not occur that day.
This issue does not occur over the weekend when the Application is not in use.
If I perform an iisreset, then the Application starts working correctly again.
If I wait approx 2 - 2 1/2 hours, then the Application starts working
correctly again.
QUESTION:
Is there anyone aware of any issue or configuration setting with IIS 6.0
that would cause this behaviour?
Is there any logging that I could perfrom on IIS to log any issues with my
IIS processes?
Do you know of any other issue, outside of IIS, that may cause this behaviour?
| |
| Egbert Nierop \(MVP for IIS\) 2005-06-29, 2:48 am |
| So you use COM objects which are turned into SOAP objects using COM+ or what
do you use?
It sounds like a threading problem. Do you happen to 'cache' COM objects in
the Session? If so, that's the reason.
Also you can use IISState and have it attach to IIS. IT can tell you the
state of your threads.
http://www.iisfaq.com/default.aspx?view=P197
--
compatible web farm Session replacement for Asp and Asp.Net
http://www.nieropwebconsult.nl/asp_session_manager.htm
"AK" <AK@ak.com> wrote in message
news:CBFAA16E-7AFC-4CD9-8C20-A5BE64F2A59B@microsoft.com...
> BACKGROUND
> I have an web based application that is using ASP, SOAP and COM Objects
> that
> reside on a web Server.
> These COM objects are used to perform LIST/ADD/EDIT/DELETE items from a
> database on another Server.
> The SOAP technology is used by creating a SOAP object on the ASP page and
> initiating it with a SOAP WSDL file, from which the API calls are
> executed.
> The Web Server is Windows 2003 and using IIS 6.0
>
> ISSUE:
> The web based application functions correctly all day until approx 4.00pm
> of
> the working day. (Working day: 9.00 - 5.00, Mon - Fri)
> At this point, none of my COM objects will operate and the API calls are
> not
> being sent to the Server.
> The Web Application will display all other pages that do not use these COM
> objects and these pages will function correctly.
> I created a test Application on the Web Server machine to test the COM
> API's
> which reside on the Web Server (therefore I am not using IIS to execute
> the
> API) and it worked successfully. This verified that the COM API's are
> functioning and the calls are executed to the DB on another Server.
> If I perform an iisreset before the issue occurs at approx 4.00 pm, then
> the
> issue does not occur that day.
> This issue does not occur over the weekend when the Application is not in
> use.
> If I perform an iisreset, then the Application starts working correctly
> again.
> If I wait approx 2 - 2 1/2 hours, then the Application starts working
> correctly again.
>
> QUESTION:
> Is there anyone aware of any issue or configuration setting with IIS 6.0
> that would cause this behaviour?
> Is there any logging that I could perfrom on IIS to log any issues with my
> IIS processes?
> Do you know of any other issue, outside of IIS, that may cause this
> behaviour?
>
>
| |
|
| We are using the Microsoft SOAP wizard to generate WSDL files e.t.c from our
COM dlls.
We do not cache COM objects in the session.
It does appear like a threading or resource issue, however we do not know
why the application recovers after a period of time.
The application code works when it executes outside of the IIS context, is
there any way to identify if there is a resource issue inside IIS (w3wp) ?
"Egbert Nierop (MVP for IIS)" wrote:
> So you use COM objects which are turned into SOAP objects using COM+ or what
> do you use?
>
> It sounds like a threading problem. Do you happen to 'cache' COM objects in
> the Session? If so, that's the reason.
>
>
> Also you can use IISState and have it attach to IIS. IT can tell you the
> state of your threads.
> http://www.iisfaq.com/default.aspx?view=P197
>
> --
> compatible web farm Session replacement for Asp and Asp.Net
> http://www.nieropwebconsult.nl/asp_session_manager.htm
>
> "AK" <AK@ak.com> wrote in message
> news:CBFAA16E-7AFC-4CD9-8C20-A5BE64F2A59B@microsoft.com...
>
>
| |
| Egbert Nierop \(MVP for IIS\) 2005-06-30, 7:49 am |
| "AK" <AK@ak.com> wrote in message
news:5253DEAD-0358-4A38-8057-52EBA7517CBA@microsoft.com...
> We are using the Microsoft SOAP wizard to generate WSDL files e.t.c from
> our
> COM dlls.
> We do not cache COM objects in the session.
> It does appear like a threading or resource issue, however we do not know
> why the application recovers after a period of time.
Because deadlocks timeout.
Note MS statement about the Soap Toolkit 3.0 (they support on Windows 2003
or not?).
<text
src="http://www.microsoft.com/downloads/details.aspx?FamilyId=C943C0DD-CEEC-4088-9753-86F052EC8450&displaylang=en">
It is generally recommended not to use SOAP Toolkit on Windows 2003. There
is limited support for this scenario when migrating existing applications on
previous versions of Windows to Windows 2003. No new development should be
done with SOAP Toolkit. Existing applications built on SOAP Toolkit should
be migrated to a .Net based solution as quickly as possible.
</text>
> The application code works when it executes outside of the IIS context, is
> there any way to identify if there is a resource issue inside IIS (w3wp) ?
I have used the SOAP wizard as well for a VB6 component. I'm not quite sure,
if the SOAP sdk has been tested very well on IIS6. In theory, this just
should work, but the reality is that most SOAP clients/servers just use the
..NET framework.
:<
[vbcol=seagreen]
> "Egbert Nierop (MVP for IIS)" wrote:
>
My best advise, is to put your application back to Windows 2000 in a legacy
situation. You know what? Just install Virtual Server (like virtual PC) and
install Windows 2000 on your 2003 box. Your Soap environment will run well.
In the mean time, you can migrate to 2003 using the .NET framework.
|
|
|
|
|