生活在ASP.NET Web App中的经典ASP页面 [英] Classic ASP pages living among a ASP.NET Web App
问题描述
我已经使用CSLA框架构建了一个新的ASP.NET Web应用程序。该网站
可以在少量用户的情况下正常运行，但一旦有任何流量
，CPU就会达到100％的峰值。我经历了很多更新，以便插入各种内存泄漏。很高兴我这样做了，它可能帮助了一些，但问题仍然存在。该应用程序构建了
适当的可扩展架构，但似乎无法处理负载。我已经看了性能计数器，而负载测试用来计算物品
out但到目前为止还没有。
我的问题是在.NET网络应用程序中使用经典的ASP页面。
我已将我的DotNet应用程序池与其他经典的ASP
网站隔离开来，因为它们应该是。但是我需要在ASP.NET应用程序中使用一些经典的ASP页面
来重定向书签和
其他硬编码的.asp页面引用。
既然他们建议您将Classic ASP网站放在任何.NET池的单独的
应用程序池中，这是一个小问题吗？ b我的.NET应用程序中有多少经典页面？两个不同的ISAPI处理程序之间的争夺内存是否可以导致100％的CPU使用率？
如果建议经典的ASP页面不应该存在于内部
ASP.NET Web应用程序，如何保存我的经典ASP页面
用于书签等等？
谢谢
I''ve built a new ASP.NET web app with the CSLA framework. The site
runs fine with a small number of users, but once there is any traffic
the CPU spikes at 100%. I went through and made many updates to plug
various memory leaks. Glad that I did that and it probably helped out
some, but the issues still exists. The application was built the
proper scalable architecture but can''t seem to handle the load. I''ve
been watching performance counters while load testing to figure things
out but have gotten no where so far.
My question is around using classic ASP pages inside the .NET web app.
I have isolated my DotNet application pool from other classic ASP-only
sites, as they should be. But I need to have some classic ASP pages
living among the ASP.NET application for redirecting bookmarks and
other hard-coded references to .asp pages.
Since they recommend that you keep Classic ASP web sites on separate
application pools from any .NET pools, is it a problem that a small
amount of classic pages live in my .NET app? Could the fight for
memory between the two different ISAPI handlers cause 100% CPU usage?
If it is recommended that classic ASP pages should not live inside an
ASP.NET web application, how can I keep my classic ASP pages available
for bookmarks and such?
Thanks
推荐答案
Hello mase，
EventLog中的任何条目？
---
WBR，Michael Nemtsev [.NET / C＃MVP]。
我的博客： http://spaces.live.com/laflour
团队博客： http://devkids.blogspot.com/
对大多数人来说是最大的危险我们并不是说我们的目标太高而且我们错过了它，但它太低了我们就达不到它了。 （c）米开朗基罗
我已经用CSLA框架构建了一个新的ASP.NET Web应用程序。该站点
可以与少量用户一起使用，但是一旦有任何流量，那么CPU的峰值将达到100％。我经历了许多更新以插入
各种内存泄漏。很高兴我做到了这一点，它可能有助于支持
msome，但问题仍然存在。该应用程序构建了
mproper可扩展的架构，但似乎无法处理负载。我已经看了性能计数器看了性能计数器，而且负载测试数字很多，但是到目前为止还没有到位。
m>
mMy问题是在.NET网站中使用经典的ASP页面
mapp。我已将DotNet应用程序池与其他经典
仅限mASP的站点隔离开来。但我需要在ASP.NET应用程序中使用一些经典的
mASP页面来重定向
mbookmarks和其他对.asp页面的硬编码引用。
m>
m因为他们建议您将Classic ASP网站保存在任何.NET池的单独的
应用程序池中，这是一个小问题吗？ br />
经典页面的数量存在于我的.NET应用程序中？在两个不同的ISAPI处理程序之间争夺
mmemory会导致100％的CPU使用率吗？
m如果建议经典ASP页面不应该存在于
中
mASP.NET网络应用程序，如何保存我的经典ASP页面
可用于书签等等？
m>
mThanks
m>
Hello mase,
Any entries in EventLog?
---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog: http://spaces.live.com/laflour
Team blog: http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
mI''ve built a new ASP.NET web app with the CSLA framework. The site
mruns fine with a small number of users, but once there is any traffic
mthe CPU spikes at 100%. I went through and made many updates to plug
mvarious memory leaks. Glad that I did that and it probably helped out
msome, but the issues still exists. The application was built the
mproper scalable architecture but can''t seem to handle the load. I''ve
mbeen watching performance counters while load testing to figure
mthings out but have gotten no where so far.
m>
mMy question is around using classic ASP pages inside the .NET web
mapp. I have isolated my DotNet application pool from other classic
mASP-only sites, as they should be. But I need to have some classic
mASP pages living among the ASP.NET application for redirecting
mbookmarks and other hard-coded references to .asp pages.
m>
mSince they recommend that you keep Classic ASP web sites on separate
mapplication pools from any .NET pools, is it a problem that a small
mamount of classic pages live in my .NET app? Could the fight for
mmemory between the two different ISAPI handlers cause 100% CPU usage?
mIf it is recommended that classic ASP pages should not live inside an
mASP.NET web application, how can I keep my classic ASP pages
mavailable for bookmarks and such?
m>
mThanks
m>
7月3日上午9:50，mase< mase .... @ gmail.comwrote：
On Jul 3, 9:50 am, mase <mase....@gmail.comwrote:
我已经使用CSLA框架构建了一个新的ASP.NET Web应用程序。该网站
可以在少量用户的情况下正常运行，但一旦有任何流量
，CPU就会达到100％的峰值。我经历了很多更新，以便插入各种内存泄漏。很高兴我这样做了，它可能帮助了一些，但问题仍然存在。该应用程序构建了
适当的可扩展架构，但似乎无法处理负载。我已经看了性能计数器，而负载测试用来计算物品
out但到目前为止还没有。
我的问题是在.NET网络应用程序中使用经典的ASP页面。
我已将我的DotNet应用程序池与其他经典的ASP
网站隔离开来，因为它们应该是。但是我需要在ASP.NET应用程序中使用一些经典的ASP页面
来重定向书签和
其他硬编码的.asp页面引用。
既然他们建议您将Classic ASP网站放在任何.NET池的单独的
应用程序池中，这是一个小问题吗？ b我的.NET应用程序中有多少经典页面？两个不同的ISAPI处理程序之间的争夺内存是否可以导致100％的CPU使用率？
如果建议经典的ASP页面不应该存在于内部
ASP.NET Web应用程序，如何保存我的经典ASP页面
用于书签等等？
谢谢
I''ve built a new ASP.NET web app with the CSLA framework. The site
runs fine with a small number of users, but once there is any traffic
the CPU spikes at 100%. I went through and made many updates to plug
various memory leaks. Glad that I did that and it probably helped out
some, but the issues still exists. The application was built the
proper scalable architecture but can''t seem to handle the load. I''ve
been watching performance counters while load testing to figure things
out but have gotten no where so far.
My question is around using classic ASP pages inside the .NET web app.
I have isolated my DotNet application pool from other classic ASP-only
sites, as they should be. But I need to have some classic ASP pages
living among the ASP.NET application for redirecting bookmarks and
other hard-coded references to .asp pages.
Since they recommend that you keep Classic ASP web sites on separate
application pools from any .NET pools, is it a problem that a small
amount of classic pages live in my .NET app? Could the fight for
memory between the two different ISAPI handlers cause 100% CPU usage?
If it is recommended that classic ASP pages should not live inside an
ASP.NET web application, how can I keep my classic ASP pages available
for bookmarks and such?
Thanks
为什么你认为这是因为ASP，也许是因为ASP.NET？
试着找到什么是最关键的活动
Why do you think it''s because of ASP, maybe it''s because of ASP.NET?
Try to find what is the most critical activity
并不多。一些OutOfMemory异常和一些其他看似简单的.NET异常。其中一个特别奇怪：
异常类型：HttpException
异常消息：路径''OPTIONS''被禁止。
任何想法？
7月3日凌晨1点03分，Michael Nemtsev< nemt ... @ msn.comwrote：
Not much. Some OutOfMemory exceptions and a few other seemingly
trivial .NET exceptions. One in particular that seems weird:
Exception type: HttpException
Exception message: Path ''OPTIONS'' is forbidden.
Any ideas?
On Jul 3, 1:03 am, Michael Nemtsev <nemt...@msn.comwrote:
Hello mase，
EventLog中的任何条目？
---
WBR，Michael Nemtsev [.NET / C＃MVP]。
我的博客： http://spaces.live.com/laflour
团队博客： http://devkids.blogspot.com/
对我们大多数人来说，最大的危险并不是我们的目标太高而且我们
想念它，但它太低了我们达到了它 （c）米开朗基罗
Hello mase,
Any entries in EventLog?
---
WBR, Michael Nemtsev [.NET/C# MVP].
My blog:http://spaces.live.com/laflour
Team blog:http://devkids.blogspot.com/
"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo
这篇关于生活在ASP.NET Web App中的经典ASP页面的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
