I recently ran into this when I went to 1.1-SP1. There is an overload for Server.Transfer that tells the runtime to/not clear the Request object after the transfer operation. For a formerly-working 1.1 app, I did
Server.Transfer( "mypage.aspx" , true ) but with 1.1-SP1, I needed to change it to Server.Transfer( "mypage.aspx" , false ) If you are not using the overload for Server.Transfer, or if you are, just change it to the opposite. I am lucky enough to use UltraEdit, so I did a "Search/Replace in Files" and rebuild and I was done. It turns out the 1.1-SP1 is the same behavior that 1.0 had in the first place, but IIRC it was changed from 1.0->1.1 in the name of ASP.NET security; now it has changed from 1.1->SP1 (to work like v1.0) in the name of ASP.NET security. ;) A recent app of mine used Server.Transfer to add an event-laden control dynamically when needed without round-tripping to the client. When I went to 1.1, the page transferred to itself so many times in 20 seconds (because the web server CPU was so fast?), that the CLR actually curled up and died. Not trapped by ASP.NET with the standard error message, not an Event Log entry stating that the worker process needed recycling, the whole thing. All I got in the Event Log was an "Error 0" in mscorlib.dll and no response at the web browser. I thought the Framework generally handled things better than that. HTH. -----Original Message----- -------------------------- Date: Fri, 17 Sep 2004 09:30:06 -0500 From: Christopher Reed <[EMAIL PROTECTED]> Subject: Server.Transfer and Service Pack 1 (1.1) We have come across a very bizarre issue and I wanted to see if anyone else has experienced it. We have two separate applications that use a submit button to process the data entered on the page and then uses Server.Transfer on itself. This was working fine until we installed SP1 for Framework 1.1 onto our servers. What happens now is that the Click methods appear to go into an infinite loop where it repeats itself. In both cases, this results in thousands of new records within the database plus on of the applications also generates emails to the same tune of thousands and thousands. It also appears that there is no postback, so we suspect that the worker process is in full control and is not relinquishing the process back to the client (browser). You cannot stop the application by simply closing the browser; you have to cause the ASP.NET worker process to restart. I know that there have been changes (fixes) made to the way Server.Transfer works. We still trying to understanding this, but I do not see why this would be happening unless this was a bug in the worker process. Any input and/or insight will be greatly appreciated! =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
