Microsoft.XMLHTTP [英] Microsoft.XMLHTTP

问题描述

我一直在网上搜索除了

之外的其他方法使用Microsoft.XMLHTTP（因为它冻结服务器很多!!）但没有运气
$ b完全是$ b。


我使用服务器端ASP，有些人说使用Microsoft.ServerXMLHTTP

。不过我也尝试了它，它仍然冻结整个

的东西（即网站只是永远加载）。


我试图做一个接下来的错误恢复抓住错误的条款但是仍然没有停止页面冻结...... :(


我看到有人在这里说不要在ASP中使用XMLHTTP，因为它不是线程安全的

（这就是它冻结的原因??），并建议使用

MSXML2.ServerXMLHTTP.3.0。


所以有人知道MSXML2.ServerXMLHTTP.3.0会不会有帮助？即不冻结

页面？请帮助!!!!!!


Vanessa

解决方案

=？Utf-8？B？VmFuZXNzYQ ==？=写于2007年7月12日

microsoft.public.inetserver.asp.general：

我一直在网上搜索，找到另一种方法

除了使用Microsoft.XMLHTTP（因为它冻结服务器很多!!）

但是没有运气。

它是否真的冻结了服务器，因此没有其他用户可以访问它，

并且服务器必须重新启动，或者它会冻结浏览器吗？

我使用服务器端ASP，

在您自己的机器上通过localhost：//或在网上？

和一些人说使用

Microsoft.ServerXMLHTTP代替。不过我也尝试了这个，但它仍然冻结整个事情（即网站只保持

永远加载）。

那不是因为你在代码中犯了一些错误吗？


为什么不显示你的代码，只是做你所说的最小化的例子。


我用asp-vbscript很好地管理 ：


Set objXMLHTTP = Server.CreateObject（" Microsoft.XMLHTTP"）

（即网站永远保持加载）。

网站'不加载，也许服务器没有，或浏览器，

但是在Microsoft.XMLHTTP的情况下，

你怎么知道服务器的假定冻结？是由那引起的？

我试图做一个开启错误恢复下一个抓住错误的子句但

仍然没有阻止页面冻结.. :(

所以这是页面这是冻结，而不是服务器？

浏览器，而不是服务器？


在接下来的错误恢复时禁止显示错误ASP的标准

错误页面，并且稍后会被你自己的代码捕获，它不会记录不会发出信号的
错误。
< blockquote class =post_quotes>
我看到有人在这里说不要在ASP中使用XMLHTTP，因为它不是线程

安全（这就是为什么它会冻结？），并建议使用

MSXML2.ServerXMLHTTP.3.0。

我认为错误的approch首先找到诊断，然后是治疗。


从什么是冻结？开始？

所以有人知道MSXML2.ServerXMLHTTP.3.0是否会有所帮助？即没有

冻结p年龄？请帮忙!!!!!!

再次，显示一个简单的代码来说明你所说的伤害。


-

Evertjan。

荷兰。

（请将我的电子邮件地址中的x'更改为点数）

" Vanessa" < Va ***** @ discuss.microsoft.com写信息

新闻：0B *********************** *********** @ microsof t.com ...

我一直在网上搜索，找到另一种方法

除了

使用Microsoft.XMLHTTP（因为它冻结服务器很多!!）但没有

运气

。


我正在使用服务器端ASP，有人说使用Microsoft.ServerXMLHTTP

代替。不过我也试过了，它还冻结了

整个

的东西（即网站只是永远加载。


我试图做一个on next resume next抓住错误的条款但是仍然没有停止页面冻结...... :(


我看到有人在这里说不要在ASP中使用XMLHTTP，因为它不是线程安全的

（这就是它冻结的原因??），并建议使用

MSXML2.ServerXMLHTTP.3.0。


所以有人知道MSXML2.ServerXMLHTTP.3.0会不会有帮助？即不冻结

页面？请帮助!!!!!!


Vanessa

是的，你应该使用ServerXMLHTTP。你还应该使用版本

特定的MSXML。 ServerXMLHTTP.3.0。


您是否向自己的服务器发出请求？如果是这样，它很容易发生僵局。如果你有ASP调试的话你不能从ASP请求你自己的服务器上的另一个ASP页面。

-

Anthony Jones - MVP ASP /ASP.NET

" Evertjan。"写道：

=？Utf-8？B？VmFuZXNzYQ ==？=于2007年7月12日写在

microsoft.public.inetserver.asp.general：

我一直在网上到处寻找另一种方法

除了使用Microsoft.XMLHTTP（因为它冻结服务器很多!!）

但没有运气。

它是否真的冻结了服务器，因此没有其他用户可以访问它，

并且服务器必须重新启动，或者是冻结浏览器？

我不确定它是否冻结服务器或浏览器，但是当发生

死锁时，我试图访问来自不同车站的网站和所有

浏览器显示''loading ......''并且它永远不会响应。但奇怪的是，b $ b这个网站的其他部分并没有调用任何XMLHTTP

方法仍在运行并回应。那么冻结在

浏览器或服务器上？


在这种情况下，我必须重新启动IIS Admin服务并恢复网站
正常。


有一件事我忘了提到 - 它并没有一直冻结，大部分是

它运行正常，能够通过XMLHTTP读/写数据。

>

我正在使用服务器端ASP，

在您自己的机器上通过localhost：//或者网络？

在我公司的网站上。

>

和一些人说使用

Microsoft.ServerXMLHTTP代替。不过我也尝试了这个，但它仍然冻结整个事情（即网站只保持

永远加载）。

那不是因为你在代码中犯了一些错误吗？


为什么不显示你的代码，只是做你所说的最小化的例子。


我用asp-vbscript很好地管理 ：


Set objXMLHTTP = Server.CreateObject（" Microsoft.XMLHTTP"）

这是我脚本的一部分：


PostURL = linkhome& " NAV / GetCustomer.asp客户id = QUOT; & CustomerID

设置xml = Server.CreateObject（" Microsoft.XMLHTTP"）

xml.Open" POST"，PostURL，false，""， "

xml.Send

getcustomXML = xml.responseText

设置xml = Nothing


似乎它被困在xml.Send中line

>

（即网站永远保持加载）。

网站'不加载，也许服务器没有，或浏览器，

但是在Microsoft.XMLHTTP的情况下，

你怎么知道服务器的假定冻结？是由它引起的？

实际上我还是不能算确切的冻结原因:(所以

请帮忙！

I试图做一个on error resume next子句来捕捉错误，但

仍然没有阻止页面冻结...... :(

所以它是冻结的页面，而不是服务器？

浏览器，而不是服务器？


" on错误恢复下一步禁止ASP的标准

错误页面显示错误，并且稍后由您自己的代码捕获，它没有

捕获错误否则不会发出信号。

我看到有人在这里说不要在ASP中使用XMLHTTP因为它不是线程

安全（这就是为什么它会冻结？），并建议使用

MSXML2.ServerXMLHTTP.3.0。

错误的approch，我认为，首先找到诊断，然后是治疗。


以什么是冷冻开头up？"

所以有人知道MSXML2.ServerXMLHTTP.3.0会有帮助吗？即不是

冻结页面？请帮忙！！！！！！

再次，显示一个简单的代码来说明你所说的伤害。


-

Evertjan。

荷兰。

（请在我的电子邮件地址中将x'变为点数）

I''ve been searching everywhere online to find an alternative method besides
using Microsoft.XMLHTTP (as it freezes the server up alot!!) but with no luck
at all.

I am using server side ASP, and some said to use Microsoft.ServerXMLHTTP
instead. However I have tried that as well and it still freezes up the whole
thing (i.e. the site just keeps loading forever).

I tried to do a "on error resume next" clause to catch the error but still
doesn''t stop the page being freezing up.. :(

I saw someone here said don''t use XMLHTTP in ASP as it is not thread safe
(is that why it is freezing up??), and suggest to use
MSXML2.ServerXMLHTTP.3.0.

so do anyone know if MSXML2.ServerXMLHTTP.3.0 will help? i.e. not freezing
up the page? Please help!!!!!!

Vanessa

解决方案

=?Utf-8?B?VmFuZXNzYQ==?= wrote on 12 jul 2007 in
microsoft.public.inetserver.asp.general:

I''ve been searching everywhere online to find an alternative method
besides using Microsoft.XMLHTTP (as it freezes the server up alot!!)
but with no luck at all.

Does it really freeze the server, so no other users can access it,
and the server has to be restarted, or does it freeze the browser?

I am using server side ASP,

On your own machine via localhost:// or on the web?

and some said to use
Microsoft.ServerXMLHTTP instead. However I have tried that as well
and it still freezes up the whole thing (i.e. the site just keeps
loading forever).

Wouldn''t that be because you made some error in your code?

Why not show your code, just an minimized example that does what you say.

I manage quite well with asp-vbscript:

Set objXMLHTTP = Server.CreateObject("Microsoft.XMLHTTP")

(i.e. the site just keeps loading forever).

Site''s do not load, perhaps the server does, or the browser,
but in the case of Microsoft.XMLHTTP,
how do you know the supposed freezeup [of the server?] is caused by that?

I tried to do a "on error resume next" clause to catch the error but
still doesn''t stop the page being freezing up.. :(

So it is the page that is freezing up, not the server?
The browser, not the server?

"on error resume next" prohibits an error to be shown by the standard
error page of ASP, and to be later catched by your own code, it does not
catch errors that would not be signalled otherwise.

I saw someone here said don''t use XMLHTTP in ASP as it is not thread
safe (is that why it is freezing up??), and suggest to use
MSXML2.ServerXMLHTTP.3.0.

Wrong approch, I think, first find the diagnosis, then the therapy.

Start with "What is freezing up?"

so do anyone know if MSXML2.ServerXMLHTTP.3.0 will help? i.e. not
freezing up the page? Please help!!!!!!

Again, show a simple code that does the harm you say.

--
Evertjan.
The Netherlands.
(Please change the x''es to dots in my emailaddress)

"Vanessa" <Va*****@discussions.microsoft.comwrote in message
news:0B**********************************@microsof t.com...

I''ve been searching everywhere online to find an alternative method

besides

using Microsoft.XMLHTTP (as it freezes the server up alot!!) but with no

luck

at all.

I am using server side ASP, and some said to use Microsoft.ServerXMLHTTP
instead. However I have tried that as well and it still freezes up the

whole

thing (i.e. the site just keeps loading forever).

I tried to do a "on error resume next" clause to catch the error but still
doesn''t stop the page being freezing up.. :(

I saw someone here said don''t use XMLHTTP in ASP as it is not thread safe
(is that why it is freezing up??), and suggest to use
MSXML2.ServerXMLHTTP.3.0.

so do anyone know if MSXML2.ServerXMLHTTP.3.0 will help? i.e. not freezing
up the page? Please help!!!!!!

Vanessa

Yes you should be using ServerXMLHTTP. You should also be using the version
specific MSXML.ServerXMLHTTP.3.0.

Are you making a request back to your own server? If so it is prone to
deadlock. If you have ASP debugging on then you can''t make a request to
another ASP page on your own server from ASP.
--
Anthony Jones - MVP ASP/ASP.NET

"Evertjan." wrote:

=?Utf-8?B?VmFuZXNzYQ==?= wrote on 12 jul 2007 in
microsoft.public.inetserver.asp.general:

I''ve been searching everywhere online to find an alternative method
besides using Microsoft.XMLHTTP (as it freezes the server up alot!!)
but with no luck at all.

Does it really freeze the server, so no other users can access it,
and the server has to be restarted, or does it freeze the browser?

I am not sure if it is freezing up the server or the browser, but when the
deadlock happened, I tried to access the site from different stations and all
browers are showing ''loading......'' and it never responds. But the weird
thing is the other sections of the site which doesn''t call any XMLHTTP
methods are still running and responding back. So is that freeze on the
browser or server?

At this case, I have to restart the IIS Admin Service and the site is back
to normal.

One thing I forgot to mention is -- it doesn''t freeze all the times, most of
the time it is running fine and able to read/write data via XMLHTTP.

>

I am using server side ASP,

On your own machine via localhost:// or on the web?

On my company''s website.

>

and some said to use
Microsoft.ServerXMLHTTP instead. However I have tried that as well
and it still freezes up the whole thing (i.e. the site just keeps
loading forever).

Wouldn''t that be because you made some error in your code?

Why not show your code, just an minimized example that does what you say.

I manage quite well with asp-vbscript:

Set objXMLHTTP = Server.CreateObject("Microsoft.XMLHTTP")

Here is one section of my script:

PostURL = linkhome & "nav/GetCustomer.asp?CustomerID=" &CustomerID
Set xml = Server.CreateObject("Microsoft.XMLHTTP")
xml.Open "POST", PostURL, false,"",""
xml.Send
getcustomXML = xml.responseText
Set xml = Nothing

It seems like it got stuck at "xml.Send" line

>

(i.e. the site just keeps loading forever).

Site''s do not load, perhaps the server does, or the browser,
but in the case of Microsoft.XMLHTTP,
how do you know the supposed freezeup [of the server?] is caused by that?

Actually I still can''t figure out the exact cause of the freezeup :( so
please help!

I tried to do a "on error resume next" clause to catch the error but
still doesn''t stop the page being freezing up.. :(

So it is the page that is freezing up, not the server?
The browser, not the server?

"on error resume next" prohibits an error to be shown by the standard
error page of ASP, and to be later catched by your own code, it does not
catch errors that would not be signalled otherwise.

I saw someone here said don''t use XMLHTTP in ASP as it is not thread
safe (is that why it is freezing up??), and suggest to use
MSXML2.ServerXMLHTTP.3.0.

Wrong approch, I think, first find the diagnosis, then the therapy.

Start with "What is freezing up?"

so do anyone know if MSXML2.ServerXMLHTTP.3.0 will help? i.e. not
freezing up the page? Please help!!!!!!

Again, show a simple code that does the harm you say.

--
Evertjan.
The Netherlands.
(Please change the x''es to dots in my emailaddress)

这篇关于Microsoft.XMLHTTP的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！