473,378 Members | 1,427 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

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

AppDomain Resetting

Hello all;

I have an ASP.NET application which I run part of it in a new thread. The
part running is very processor and time intensive and takes an hour plus to
complete.

The problem I am experiencing is after the thread has been running for about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on IIS
and in the machine.config, increasing all values from the default value of
20 min to 120 min in the hopes it would work. I did get the process to run
for 60 min one time AFTER increasing the timeout to 120 min but the process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet
Nov 18 '05 #1
8 1284
In the IIS MMC, check the "Shutdown worker process if idle for X
minutes setting". Go to Application pools, right click and select
Properties for the pool your application runs in. This setting is the
first on the Performance tab.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:19:51 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:
Hello all;

I have an ASP.NET application which I run part of it in a new thread. The
part running is very processor and time intensive and takes an hour plus to
complete.

The problem I am experiencing is after the thread has been running for about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on IIS
and in the machine.config, increasing all values from the default value of
20 min to 120 min in the hopes it would work. I did get the process to run
for 60 min one time AFTER increasing the timeout to 120 min but the process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet


Nov 18 '05 #2
Scott,

Well, the setting is 20 min., which is the magic number but....it is
indicating idle time and I wouldn't think the worker process would be idle
at this point. Am I interpreting this setting incorrectly??? If I start
my process and watch utilization on w3wp.exe it is running at about 70-80%
the entire time. What am I missing??

Thanks,
Rob

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:ka********************************@4ax.com...
In the IIS MMC, check the "Shutdown worker process if idle for X
minutes setting". Go to Application pools, right click and select
Properties for the pool your application runs in. This setting is the
first on the Performance tab.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:19:51 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:
Hello all;

I have an ASP.NET application which I run part of it in a new thread. The
part running is very processor and time intensive and takes an hour plus
to
complete.

The problem I am experiencing is after the thread has been running for
about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on
IIS
and in the machine.config, increasing all values from the default value of
20 min to 120 min in the hopes it would work. I did get the process to
run
for 60 min one time AFTER increasing the timeout to 120 min but the
process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet

Nov 18 '05 #3
idle means no requests

-- bruce (sqlwork.com)
"Rob Bazinet" <rb********@hotmail.com> wrote in message
news:u3**************@TK2MSFTNGP10.phx.gbl...
| Scott,
|
| Well, the setting is 20 min., which is the magic number but....it is
| indicating idle time and I wouldn't think the worker process would be idle
| at this point. Am I interpreting this setting incorrectly??? If I start
| my process and watch utilization on w3wp.exe it is running at about 70-80%
| the entire time. What am I missing??
|
| Thanks,
| Rob
|
| "Scott Allen" <bitmask@[nospam].fred.net> wrote in message
| news:ka********************************@4ax.com...
| > In the IIS MMC, check the "Shutdown worker process if idle for X
| > minutes setting". Go to Application pools, right click and select
| > Properties for the pool your application runs in. This setting is the
| > first on the Performance tab.
| >
| > --
| > Scott
| > http://www.OdeToCode.com/blogs/scott/
| >
| > On Mon, 22 Nov 2004 14:19:51 -0500, "Rob Bazinet"
| > <rb********@hotmail.com> wrote:
| >
| >>Hello all;
| >>
| >>I have an ASP.NET application which I run part of it in a new thread.
The
| >>part running is very processor and time intensive and takes an hour plus
| >>to
| >>complete.
| >>
| >>The problem I am experiencing is after the thread has been running for
| >>about
| >>20 min it stops. I am running this app on a Windows 2003 server and SQL
| >>Server 2000 on the backend. I suspect it may be a SessionState time out
| >>issue and I have played with the settings at the server and app level on
| >>IIS
| >>and in the machine.config, increasing all values from the default value
of
| >>20 min to 120 min in the hopes it would work. I did get the process to
| >>run
| >>for 60 min one time AFTER increasing the timeout to 120 min but the
| >>process
| >>is stopping at about 20 min again.
| >>
| >>Anyone have any insight into this and can help it would be appreciated.
| >>
| >>Thanks in advance,
| >> Rob Bazinet
| >>
| >
|
|
Nov 18 '05 #4
As bruce pointed out, you'll need incoming requests to keep the app
alive (or change / disable the setting).

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:44:45 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:
Scott,

Well, the setting is 20 min., which is the magic number but....it is
indicating idle time and I wouldn't think the worker process would be idle
at this point. Am I interpreting this setting incorrectly??? If I start
my process and watch utilization on w3wp.exe it is running at about 70-80%
the entire time. What am I missing??

Thanks,
Rob

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:ka********************************@4ax.com.. .
In the IIS MMC, check the "Shutdown worker process if idle for X
minutes setting". Go to Application pools, right click and select
Properties for the pool your application runs in. This setting is the
first on the Performance tab.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:19:51 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:
Hello all;

I have an ASP.NET application which I run part of it in a new thread. The
part running is very processor and time intensive and takes an hour plus
to
complete.

The problem I am experiencing is after the thread has been running for
about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on
IIS
and in the machine.config, increasing all values from the default value of
20 min to 120 min in the hopes it would work. I did get the process to
run
for 60 min one time AFTER increasing the timeout to 120 min but the
process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet


Nov 18 '05 #5
Thank you to both of you for the replies. It worked great. I had never had
a long running process like this and it was a learning experience.

-Rob

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:bi********************************@4ax.com...
As bruce pointed out, you'll need incoming requests to keep the app
alive (or change / disable the setting).

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:44:45 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:
Scott,

Well, the setting is 20 min., which is the magic number but....it is
indicating idle time and I wouldn't think the worker process would be idle
at this point. Am I interpreting this setting incorrectly??? If I start
my process and watch utilization on w3wp.exe it is running at about 70-80%
the entire time. What am I missing??

Thanks,
Rob

"Scott Allen" <bitmask@[nospam].fred.net> wrote in message
news:ka********************************@4ax.com. ..
In the IIS MMC, check the "Shutdown worker process if idle for X
minutes setting". Go to Application pools, right click and select
Properties for the pool your application runs in. This setting is the
first on the Performance tab.

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 22 Nov 2004 14:19:51 -0500, "Rob Bazinet"
<rb********@hotmail.com> wrote:

Hello all;

I have an ASP.NET application which I run part of it in a new thread.
The
part running is very processor and time intensive and takes an hour plus
to
complete.

The problem I am experiencing is after the thread has been running for
about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on
IIS
and in the machine.config, increasing all values from the default value
of
20 min to 120 min in the hopes it would work. I did get the process to
run
for 60 min one time AFTER increasing the timeout to 120 min but the
process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet

Nov 18 '05 #6
Hi Rob,

I see that Scott and Bruce have pointed you in the right direction for the
actual problem.

But I would suggest that you think about some async mechanism to actually
run your requests if they are taking this long. Start up a new thread or an
Async HTTP Handler, or better yet run this operation in a separate
process/machine.

Long Web Requests, because of the ASP.NET thread pool, are ggenerally not a
good idea as they can cause a variety of problems including these timeouts.
If somebody hits that request more than once you're going to kill the
machine most likely for example.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
http://www.west-wind.com/wwThreads/
----------------------------------
Making waves on the Web
"Rob Bazinet" <rb********@hotmail.com> wrote in message
news:uq**************@TK2MSFTNGP12.phx.gbl...
Hello all;

I have an ASP.NET application which I run part of it in a new thread. The
part running is very processor and time intensive and takes an hour plus to complete.

The problem I am experiencing is after the thread has been running for about 20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on IIS and in the machine.config, increasing all values from the default value of
20 min to 120 min in the hopes it would work. I did get the process to run for 60 min one time AFTER increasing the timeout to 120 min but the process is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet

Nov 18 '05 #7
Rick,

Great suggestions. Do you have an resources you can point me to? I wasn't
sure what approach to take with my long running process and the thread
seemed to be a solution but if you have something better I would be glad to
try it.

Thanks,
Rob

"Rick Strahl [MVP]" <ri********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi Rob,

I see that Scott and Bruce have pointed you in the right direction for the
actual problem.

But I would suggest that you think about some async mechanism to actually
run your requests if they are taking this long. Start up a new thread or
an
Async HTTP Handler, or better yet run this operation in a separate
process/machine.

Long Web Requests, because of the ASP.NET thread pool, are ggenerally not
a
good idea as they can cause a variety of problems including these
timeouts.
If somebody hits that request more than once you're going to kill the
machine most likely for example.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
http://www.west-wind.com/wwThreads/
----------------------------------
Making waves on the Web
"Rob Bazinet" <rb********@hotmail.com> wrote in message
news:uq**************@TK2MSFTNGP12.phx.gbl...
Hello all;

I have an ASP.NET application which I run part of it in a new thread.
The
part running is very processor and time intensive and takes an hour plus

to
complete.

The problem I am experiencing is after the thread has been running for

about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on

IIS
and in the machine.config, increasing all values from the default value
of
20 min to 120 min in the hopes it would work. I did get the process to

run
for 60 min one time AFTER increasing the timeout to 120 min but the

process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet


Nov 18 '05 #8
Rick,

Actually, I am starting a new thread for my long running process. Are you
referring to some other approach?

I am not familiar with Async Handlers but I will look into them.

Thanks,
Rob

"Rick Strahl [MVP]" <ri********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP14.phx.gbl...
Hi Rob,

I see that Scott and Bruce have pointed you in the right direction for the
actual problem.

But I would suggest that you think about some async mechanism to actually
run your requests if they are taking this long. Start up a new thread or
an
Async HTTP Handler, or better yet run this operation in a separate
process/machine.

Long Web Requests, because of the ASP.NET thread pool, are ggenerally not
a
good idea as they can cause a variety of problems including these
timeouts.
If somebody hits that request more than once you're going to kill the
machine most likely for example.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/weblog/
http://www.west-wind.com/wwThreads/
----------------------------------
Making waves on the Web
"Rob Bazinet" <rb********@hotmail.com> wrote in message
news:uq**************@TK2MSFTNGP12.phx.gbl...
Hello all;

I have an ASP.NET application which I run part of it in a new thread.
The
part running is very processor and time intensive and takes an hour plus

to
complete.

The problem I am experiencing is after the thread has been running for

about
20 min it stops. I am running this app on a Windows 2003 server and SQL
Server 2000 on the backend. I suspect it may be a SessionState time out
issue and I have played with the settings at the server and app level on

IIS
and in the machine.config, increasing all values from the default value
of
20 min to 120 min in the hopes it would work. I did get the process to

run
for 60 min one time AFTER increasing the timeout to 120 min but the

process
is stopping at about 20 min again.

Anyone have any insight into this and can help it would be appreciated.

Thanks in advance,
Rob Bazinet


Nov 18 '05 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Satinderpal Singh | last post by:
Hi All, I have an EXE, I load the DLL from that exe in a seperate AppDomain. (I have not given reference to that DLL from the EXE). Now, i call some commands of that dll from the EXE, and in...
5
by: Chris | last post by:
Hi I have a scenario where I've created another AppDomain to dynamically load a DLL(s) into. In this newly loaded DLL I want to call a static method on a class. The problem arise is that I have...
4
by: stu_pb | last post by:
I am designing a plugin system for a window application using .NET(C# specifically). One of the requirements of the plugin system is to be able to dynamically load/unload plugins. My initial...
1
by: MatthewRoberts | last post by:
Howdy All, I am having difficulty with two-way communication across AppDomains in an attempt to dynamically script applications. Everything works as expected, except when using ByRef parameters....
4
by: Chris Lacey | last post by:
Hi, I'm currently writing a scheduling service which starts a number DotNet executables, each within a new AppDomain, every ten seconds. The guts of the code is as follows: // For each...
8
by: A. Elamiri | last post by:
Hello, I created a small app which acts as a services manager. I basically drop a DLL in a Services folder and set the frequency through the application for how often do I want the code in the...
6
by: Wal Turner | last post by:
Hi there. There are various snippets on forums regarding issues with AppDomain.Unload and how it just doesnt work. Fortunately, I got it working with the base case, after much fiddling. Consider...
1
by: Andrew Ducker | last post by:
I'm trying to load an assembly into a temporary AppDomain rather than my main AppDomain, so that it can be unloaded later on. However, it's also loading into my main AppDomain at the same time. ...
12
by: John | last post by:
I have a AppDomain ID, how do I get the instance of the AppDomain Object? Please advice. Thanks in advance. John
4
by: illegal.prime | last post by:
Hi all, I'm getting unexpected results when trying to preload assemblies into an AppDomain I'm creating. Upon creation of the AppDomain - I attach an AssemblyResolve to both my current AppDomain...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
by: Charles Arthur | last post by:
How do i turn on java script on a villaon, callus and itel keypad mobile phone
0
by: ryjfgjl | last post by:
If we have dozens or hundreds of excel to import into the database, if we use the excel import function provided by database editors such as navicat, it will be extremely tedious and time-consuming...
0
by: ryjfgjl | last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
0
BarryA
by: BarryA | last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
1
by: nemocccc | last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
1
by: Sonnysonu | last post by:
This is the data of csv file 1 2 3 1 2 3 1 2 3 1 2 3 2 3 2 3 3 the lengths should be different i have to store the data by column-wise with in the specific length. suppose the i have to...
0
by: Hystou | last post by:
There are some requirements for setting up RAID: 1. The motherboard and BIOS support RAID configuration. 2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...

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.