Search results matching tag 'application pools'

Re: Server error in '/' Application

tilak1980 — Thu, 06 Aug 2009 09:36:57 GMT

Im also getting the same problem.......?

Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This is may have occured because all pooled connections were in use and max pool size was reached.

But i have checked in web.conf file there is no restriction for connections.

Could you please give me solution for this error, im not getting any other information like above sql connection.dat like............etc

waiting for reply

.Net Framework Version getting changed on websites but not sure how

nmwoodde — Thu, 23 Jul 2009 18:45:06 GMT

Running IIS 6 on Windows Server 2003.

Several times in the last month websites have sudden'y stopped working. After much digging we have found that somehow the version of the .Net Framework the website has been using gets changed from 1.1 to 2.0. We are running websites with both frameworks on the same server and we have set up the application pools for the different versions. I am just wondering if anyone would have any clue as to why or how this setting could get changed. Was it because someone restarted IIS or because someone configures a new website or because maybe we need some patches. I am just looking for anything to point me in a direction. As we do no have a IIS Guru to help us through this.

Nikki

ASP.Net website stops responding at regular intervals in IIS6

azpcc — Wed, 24 Jun 2009 15:50:26 GMT

Hello, I have an ASP.Net AJAX website that needs to run continuously and it's not. Originally, the website would randomly throw "ScriptResource.axd" errors, and an associate recommended adjusting the App Pool recycling settings in IIS away from the defaults. My familiarity with IIS is limited, but I managed to spend the past week adjusting settings to recycle the app pool, and no matter what I change it always stops responding (no errors this time) at 22:24 each night. Here's the troubleshooting and findings I've done so far:

The IIS logs show it stopping every night at 22:23-22:24. No errors, just completely stops. The app itself reflects the same, because it captures the current minutes on the screen for every refresh, and it always shows a 23 or 24.
Event Log shows nothing at or even close to this time, for both Application and System logs.
Our network team confirmed that there are no backups or other process-intensive tasks running on that box at that time.

I have the following settings set on the app pool properties:

Under the Recycling tab, only the “Recycle Worker Processes (in minutes)” item is checked, and set to 60 minutes. Setting this to 8 hours made no difference.
Under the Performance tab, everything is unchecked, and the “Maximum number of worker processes” item is set to 3.
Under the Health tab, “Enable Pinging” is checked and set to 30 seconds, “Enable Rapid Fail Protection” is unchecked, and both the Startup and Shutdown time limits are set to 90 seconds.
Under the Identity tab, “Predefined” is selected and set to Local System.

Likewise, under the actual website settings, I have “Enable HTTP Keep-Alives” checked, bandwidth throttling is not checked, website connections is set to unlimited, “Enable Content Expiration” is not checked, and Isolation mode is not checked (it’s IIS6). The server it’s running on is my dev server (Server 2003) and I’m the only developer, so I know nobody’s messing with the box at all, ‘cause nobody else can get to it. The goal is for the web app to run continuously. There's a Timer control built into the app that causes a postback every 10 seconds. Users will walk past the screen and see current information displayed automatically.

What else could be causing this to happen every night at the same time?

UPDATE: I apologize, I read the IIS log wrong, it actually dies between 15:23 and 16:18 every day. There's nothing running at those times that could interfere either, however.

iie6 service unavailable

adw999 — Wed, 25 Mar 2009 16:06:24 GMT

After installing php as an isapi extension into ii6 on a 64bit machine I'm getting the error 'Service unavailable'. I've tried lots of so called solutions from permission checking to running code 'required' for php to be run on a 64 bit machine but i'm still getting nowhere. The application pool seems to be the problem, it starts fine but executing a page it falls over and stops.

Any one got any solutions for what could be the problem?

Thanks

App pool is recycling on every request

vinay_iisnet — Wed, 11 Mar 2009 11:43:06 GMT

We have small ASP.NET 2.0 interface kind of appication, which redirects from one application to another by getting user credentials from parent site. After encoding it uses response.redirect to call child website.

There are 2 .aspx pages for two different child sites. Time stamp is used for encoding in both cases.
1. URL encoded and XOR encoded
2. URL encoded and HASH encoded(SHA1)

First one is working fine. However, second one fails saying "Time interval is greater than 300 seconds" between the parent and child sites. The log shows a difference of about 20 mins between the time used in encoding and time where the child site logs a error.

In event log, we have observed logs like

App Pool is recycling on every request to the child site.

A worker process with process id "XXXX" serving application pool " AppPoolName" has requested a recycle because it reached its virtual memory limit.

Virtual Mmory Limit is set to 500MB for this App Pool.

I have observed that while debugging, the Encoded URL is working fine in the local system. We donot have access to IIS in the server where application is hosted. :(

Any help will be appreciated.

Thank you,
Vinay

Thousands of w3wp.exe

LarryinHotwater — Tue, 24 Feb 2009 14:49:54 GMT

Hello,

I have a serious problem and could use some help. I have taken over an application that was written in .net 1.1 and is using Nhibernate to connect to DB2 on the AS400. The problem I have is that whenever the seesion is over or abandoned the connect stays established to the port on the AS400 port 8471. By right around 4:30 pm I actually run out of user ports on my w2k3 machine ( user ports are 1025 - 5000 by default). I have added MaxUserPort and changed it to 65534. But that does not fix my underlying problem of all these abandoned Open ports. I can get the sessionid but is there anyway to correlate the ports being opened to the sessionid so I can manually close them when the session is ended. Or is there any code I can put in my Global.asax to kill or close the ports associated with that session. I have sent weeks on this issue and it will only get bigger. I have thought about changing for inproc to stateserver or sqlserver that way I can recycle the w3wp.exe in the memory pool without kicking everone off the server, but the original programmer serialized everything within the code, and I don't klnow what will happen to Nhibernate if I remove serilization from the code and change the state . Thanks for all you help .

Cocurrency Issue in IIS for Dot NET

vinod.pol — Wed, 18 Feb 2009 17:24:47 GMT

I have prepared a webservice but when I am deploying it on IIS getting Concurrency Issue.

IIS is not able to maintain concurrent sessions for multiple users.

The response time is getting increased if the users are increased.

Is it coding Problem or IIS configuration Issue?

any help will be appreciated..

HTTPEXCEPTION: Request timed out

dhinatechno — Sat, 07 Feb 2009 17:36:39 GMT

Hi, This exception happens when our tries to access the website. This exception does not happen always. However it happens once in a day randomly. When this error happens, even i cannot access the portal for sometime, after sometime, the portal works fine, or i should do iisreset to make it work fine. We could not still reproduce this error as everything works fine after that.

Here is the event log:
Event code: 3001
Event message: The request has been aborted.
Event time: 2/4/2009 8:48:20 PM
Event time (UTC): 2/5/2009 1:48:20 AM
Event ID: 863e91c835b0419892e586a10e7899b8
Event sequence: 821
Event occurrence: 19
Event detail code: 0

Application information:
Application domain: /LM/W3SVC/1/Root/Por-3-128782652777138598
Trust level: Full
Application Virtual Path: /Por
Application Path: E:\eikd\Por
Machine name: xxxxxx1

Process information:
Process ID: 151756
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE

Exception information:
Exception type: HttpException
Exception message: Request timed out.

Request information:
Request URL: http://xxxxxx1/Por/grids/CustomerReport.aspx
Request path: Por/grids/CustomerReport.aspx
User host address: 192.168.10.11
User: xxx\yyy9911
Is authenticated: True
Authentication Type: Negotiate
Thread account name: NT AUTHORITY\NETWORK SERVICE

Thread information:
Thread ID: 1
Thread account name: NT AUTHORITY\NETWORK SERVICE
Is impersonating: False
Stack trace:

Custom event details:
For more information, see Help and Support Center at

Database connectivity does not seem to be a problem. In inetmgr, under the DefaultAppPool we have many applications configured. Each application makes use of cache. I use Windows Server 2003 and IIS 6.0.

I dont want to increase the execution timeout setting as this exception does not always happen.

Any clue on this would be highly appreciated.

Thanks very much,
Dhina

1 Site - 2 Application Pools

Ride2Live — Tue, 16 Sep 2008 16:52:36 GMT

We have a need to have some sites running both .aspx and classic .asp. The new wizbang homepage and wrapper is .NET 2.0 and many of the resources behind the scenes is classic .asp.

The homepage and wrapper aspx pulls in some classic .asp resources to fully render pages. The homepage aspx and associated files are kept in a separate directory from all the classic .asp directories/pages.

We set up a separate single application pool to handle the homepages/wrappers of all the sites and kept the old application pools to handle the rest of the sites. (each site's classic area has it's own application pool as well).

We are seeing load times for each site as longer than before, though the amount of bits is about the same.

Question: Do you think there is a performance hit to a site that has separate app pools for it's .NET and classic portions?

We didn't think we could/should run the .NET and classic .asp all under the same application pool, but that may be a misguided thinking.

application pool best practices

stevemorisseau — Tue, 02 Sep 2008 16:36:08 GMT

Procedure website creation and application pool

Application pool definition:

An application pool is a configuration that links one or more applications to a set of one or more worker processes.
Because applications in an application pool are separated from other applications by worker process boundaries,
an application in one application pool is not affected by problems caused by applications in other application pools.

By creating new application pools and assigning Web sites and applications to them, you can make your server
more efficient and reliable, as well as making your other applications always available, even when the worker
process serving the new application pool has problems.

source:http://technet2.microsoft.com/windowsserver/en/library/c7f09f1c-b238-42a4-9d57-c5732485eba91033.mspx?mfr=true

Website creation and application pool

even though IIS 6 allows you to use application pools, there is only one application pool by default.
As you create new Web sites on the server, the newly created sites are lumped into the default application pool
unless you tell IIS to do otherwise. IIS will not automatically create a separate application pool for each Web site.

For production site:

- create an individual application pool for each Web site

Naming convention: [ap]_[website name]

[ap] : stands for application pool
[website name] : stands for the name of the website

for example, the reitman website is named "reitmans.com" then the application pool name will be named "ap_reitmans.com"

For Dev sites on production server:

- create one application pool called "ap_dev" for all dev Web site on production server.

Recycle application pool period:

Recycling occurs when IIS 6.0 stops and restarts an application pool. This can occur due to a number
of events that you can configure in the Application Pool on the Recycling tab (see Figure 2) manually
or programmatically. This process, known as overlapping recycling, is designed to allow these processes
to recycle gracefully. The old worker process continues to serve existing connections while new requests
are routed to a new worker process. The process marked for recycling is kept in memory until it has no
more requests to serve or until a configurable timeout is reached.

Periodic recycling of your application pools is recommended. It helps to clean up memory fragmentation,
memory leaks, abandoned threads and other clutter. Keep in mind that when an application pool recycles,
session state information stored in-process is lost for that pool, but other pools are not affected. ASP.NET,
however, does allow you to store your session state outside the worker process, so that session information
is not lost during a recycle.

Notice that Recycle worker processes (in minutes) is set to 1740 minutes (29 hours) by default.
This will cause an automatic recycling to occur every day, five hours later than the previous day.

You may want to consider changing this to recycle at a specific time of day when your server load is the smallest.

source:http://www.microsoft.com/technet/technetmag/issues/2006/01/ServingTheWeb/

Request to Server hosting company:

If we had to create a dev and production site named "devtest.com" and "test.com", we would request like this:

- Create website "dev_test.com" link to application pool "ap_dev" <--default application pool for all dev sites
- Create website "test.com" link to new application pool named "ap_test.com"
- Automatically recycle application pool "ap_test.com" every morning at 4am

 Hope this helps

steeve

steve@sinfoca.com