471,330 Members | 1,074 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,330 software developers and data experts.

Very odd beahvior of web application

We have a C# application running under ASP.NET. It wasn't written using any
VS.NET magic; all of the call the System.Web are made explicitly. It uses
..NET 1.1; no other version of the framework is present on the machine.
There are two web.config files: the one at the top level specifies an
HttpModule, one in a subdirectory specifies an HttpHandler.

On some machines only, we see this odd behavior, and only after the app has
been running for some (variable) period of time: the HttpModule stops being
called. All requests for the vdir are still processed by ASP.NET, and URLs
including the subdirectory are still processed by its HttpHandler, but no
requests are processed by the HttpModule. Restarting IIS always fixes the
problem (temporarily).

First, has anyone seen anything like this. or has any ideas what might be
causing it?

Second, does anyone have ideas about how to debug it? We haven't found any
tracing to turn on, or any way to inquire of IIS/ASP.Net what it thinks the
state of the vdir or module is.
Dec 14 '05 #1
4 1040
Your first approach should be combing thru the application event logs to see
if something funny turns up. I suspect your module is failing.

I've never seen this before, but then again, i'm fresh here.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Mike Schilling" <ms*************@hotmail.com> wrote in message
news:#h*************@TK2MSFTNGP12.phx.gbl...
We have a C# application running under ASP.NET. It wasn't written using any VS.NET magic; all of the call the System.Web are made explicitly. It uses
.NET 1.1; no other version of the framework is present on the machine.
There are two web.config files: the one at the top level specifies an
HttpModule, one in a subdirectory specifies an HttpHandler.

On some machines only, we see this odd behavior, and only after the app has been running for some (variable) period of time: the HttpModule stops being called. All requests for the vdir are still processed by ASP.NET, and URLs including the subdirectory are still processed by its HttpHandler, but no
requests are processed by the HttpModule. Restarting IIS always fixes the
problem (temporarily).

First, has anyone seen anything like this. or has any ideas what might be
causing it?

Second, does anyone have ideas about how to debug it? We haven't found any tracing to turn on, or any way to inquire of IIS/ASP.Net what it thinks the state of the vdir or module is.

Dec 14 '05 #2

"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> wrote in message
news:eD**************@TK2MSFTNGP11.phx.gbl...
Your first approach should be combing thru the application event logs to
see
if something funny turns up. I suspect your module is failing.


We haven't seen anything funny in the logs. What would "failing" mean here?
When a module throws exceptions, that will cause processing to be aborted
for the current message, but as far as I know it has no effect on other
threads. Or do you mean throwing an exception from Init() ?
Dec 14 '05 #3
You'd need to assemble a test case. I suspect your module is dead. Here's
how to test that scenario. First clear your application logs. Add some code
in your module that writes an event to the event log every hour or so. Let
the application run. Examine the logs to see if the messages are continuous.
I suspect they stop after a while. Find out what the while is and if there
are any incidents that cause that action. That would be my first step.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ www.lulu.com/owc
Forth-coming VSTO.NET - Wrox/Wiley 2006
-------------------------------------------------------

"Mike Schilling" <ms*************@hotmail.com> wrote in message
news:uS**************@TK2MSFTNGP09.phx.gbl...

"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> wrote in message
news:eD**************@TK2MSFTNGP11.phx.gbl...
Your first approach should be combing thru the application event logs to
see
if something funny turns up. I suspect your module is failing.
We haven't seen anything funny in the logs. What would "failing" mean

here? When a module throws exceptions, that will cause processing to be aborted
for the current message, but as far as I know it has no effect on other
threads. Or do you mean throwing an exception from Init() ?

Dec 15 '05 #4

"Alvin Bruney - ASP.NET MVP" <www.lulu.com/owc> wrote in message
news:eO**************@TK2MSFTNGP15.phx.gbl...
You'd need to assemble a test case. I suspect your module is dead. Here's
how to test that scenario. First clear your application logs. Add some
code
in your module that writes an event to the event log every hour or so. Let
the application run. Examine the logs to see if the messages are
continuous.
I suspect they stop after a while. Find out what the while is and if there
are any incidents that cause that action. That would be my first step.


Can you give me any hints about what sorts of things can kill modules? My
(possibly naive) view is that a module is an object created by the ASP.NET
runtime in response to configuration, that ASP.NET calls at defined times
during message processing. It doesn't have an associated thread that can
exit; it's called on the message-processing threads, possibly many at one
time. And as a managed object, it can't be manually deallocated. So what
does it mean that the module "dies", and how does that happen?

By the way, we've already put in tracing that shows that Dispose() isn't
being called on it.
Dec 15 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Søren Johansen | last post: by
6 posts views Thread by Greg | last post: by
3 posts views Thread by Trapulo | last post: by
9 posts views Thread by Vito DeCarlo | last post: by
3 posts views Thread by schiefaw | last post: by
8 posts views Thread by pamelafluente | last post: by
50 posts views Thread by diffuser78 | last post: by
4 posts views Thread by garyusenet | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.