allwoojm
Registered: 04/08/07
Posts: 42
|
|
|
Reply with quote | #1 |
I deployed my first ISD app to a production server at DiscountASP earlier today. On add and edit pages that were ISD-generated and not modified, I was able to add 4-5 records and would then be knocked out of the app and re-directed to the login page. Everything would work well for awhile and then I'd see a consistent pattern of instability.
I'm using the most current version of ISD and NetAdvantage (menubar) and my database is SQL Server 2005. Additionally, I'm using session view state storage (is that possibly my issue?). Has anyone else experienced this behavior? Is there an IIS parameter that I need to modify, additional memory allocation, etc.?
Thanks in advance.
|
| |
miles
MVP Consultant
Registered: 10/15/03
Posts: 2,254
| |
allwoojm
Registered: 04/08/07
Posts: 42
|
|
|
Reply with quote | #3 |
Hi Miles:
What type of problem? What should I look for? Is it something that can be resolved? The problem doesn't manifest itslef on my local, development machine (only the production server).
Thanks,
Joe
|
| |
porphi
Registered: 09/07/05
Posts: 1,050
|
|
|
Reply with quote | #4 |
Joe,
From discountasp.com's web site;
Quote: Recycle App Pool (This tool is recommended for use by advanced users only)
The Application Pool Recycle Tool allows you to shut down the process hosting your web application and spawn a new process. Think of it as a sort of "reboot" for your web applications. DiscountASP.NET hosts each web site in its own isolated application pool, so this tool can be used without affecting other user's web sites. The Recycle App Pool tool is useful for:
- Recycling a hung application
- Releasing locked files or databases
- Resetting session variables and clearing server cache Note: When the application pool is recycled, all session variables are deleted. More information on application pools can be found in these articles: Working With Application Pools in Internet Information Server
IIS and ASP.NET: The Application Pool
Phil
|
| |
timt
Iron Speed MVP
Consulting Organization
Registered: 08/06/05
Posts: 1,113
|
|
|
Reply with quote | #5 |
Hi
I have also had apps that reset themselves (not via discount.asp) and appear to behave erratically (session lost etc)
It boils down to the app being recyled by the runtime for whatever reason. Throwing memory at the problem ususally works. I also have changed the recyling to happen at 3am rather than after so many hours (IIS - Application Pools - Recycling) and have had no further problems.
__________________
Tim Titchmarsh
UK Iron Speed MVP
Dot Net Architect
+44 (0)1621 857758
http://www.dotnetarchitect.co.uk
timt@dotnetarchitect.co.uk |
| |
Charax
Registered: 11/15/08
Posts: 40
|
|
|
Reply with quote | #6 |
I have just wrestled with this problem on a DiscountASP.net server with an SQL Server 2005 db. I have been using Page view state with InProc session state, but DiscountASP forces a recycle when memory usage is above 200 MB. Even with my modest size application, I was constantly getting recycled by the server due to memory usage (according to tech support at DiscountASP.net).
Tech support is great, but they could not change the memory limit that causes the recycle.
Below is the information they provided.
Cheers,
Charax
Quote: Dear Customer, We host each website in its unique application pool / process as mentioned earlier. To conserve memory, we recycle the application if any of the following condition is met 1) More than 20 minutes of idle time (no http request in 20 minutes) 2) The application uses more than 200MB memory 3) The application uses more than 75% of CPU time By default, the session information is stored in memory and recycling the application will also destroy the session variables. Your application is been recycled because of condition #2 I recommend you switch to use SQL server session which you have. This will at least back the session before been recycled. We saw the recycle after the 12 coin. See http://kb.discountasp.net/article.aspx?id=10350 for more details. thank you DiscountASP.NET
|
| |
davidnowens
Registered: 09/01/08
Posts: 29
|
|
|
Reply with quote | #7 |
Hi,
I have a few apps hosted with Discount ASP.NET - and to get around this problem, you need to store Session State in a database.
Basically - buy another database instance from Discount AsP.NET and ask them to set it up with a ASPState database. Then you edit your web config to save state to the new database. If you need assistance settingt this up, I can script in the ASPState database and change your web config.
This will resolve the problem and allow your app to only timeout, based on when you decide and not due to RECYCLED MEMORY or IIS WORKER PROCESS.
Hope this helps.
KR
Dave
|
| |
JimiJ
MVP Developer
Registered: 03/30/05
Posts: 3,648
|
|
|
Reply with quote | #8 |
If you want to have more freedom from session issues or want to overcome critical demands, Mosso or RackSpace could be the answer. This hosting provider however is implementing Medium Trust setting on all their shared sites.
Jimi
__________________
Jaime Jegonia
JimiTron Software
JimiTron.Net | JimiTron.Com |
| |
RSS(.NETCodeGenerationIsHere).gif)
