不知道在controller里面钩上init all vuser before execution是否可以解决这个问题？ Zee。作者: Zee 时间: 2007-4-9 18:29
我在做过样的测试的时候，跑多个vuser，没有关系的。
你勾上init all vuser before execution也和后面的执行时间没有关系。你也控制不了每个vuser的迭代时间呀。作者: guxingyun 时间: 2007-4-13 13:47
我的action中只录制一个动作，即发送100字节的数据给服务器，lr_think_time(0.1);然后我在运行时设置中将think的设置*0.1，这样子理论上可以保证1秒100条数据的发送，不知这样子是否正确？然后我将脚本复制10份，将其中的vuser_init设置为存在的客户连接，然后将这些脚本添加到controller中，且quantity都为1，这样子我在运行的时候就可以看到服务器端存在10个连接，且每个连接100/s的速度上传数据，当运行时间长了以后，就出现连接reset。这应该与服务器不能处理这么多数据的原因引起的，然后后续的数据积压，到一定阶段的时候就被reset了。不知理解的对否？作者: leoomo 时间: 2007-7-6 12:30
原帖由 Zee 于 2007-4-9 15:04 发表
把所有脚本都放在action里。
放了
还是没有用！sdlkfj9作者: shanxi 时间: 2007-7-6 12:57
Problem Description: Error: "-27780: read to host failed: [10054] Connection reset by peer"
The user gets the following error messages during replay of a Web script:
"Error -27780: read to host <host name> failed: [10054] Connection reset by peer"
"Error -27790: Failed to read data from server <host name>"
Diagnosis: The client sends a POST request to the server and gets a response with HTTP status 200, connection close and redirection using both JS code and meta-refresh. There is no content-length, so the client is supposed to decide when to close the connection. Internet Explorer closes the connection before sending the request to the redirection URL. But, LoadRunner does not; later the server closes the connection, and the result is the error message.
不知道,这个是什么问题作者: tiannianyong 时间: 2009-5-30 22:53
经常出现的Connection reset by peer: 原因可能是多方面的，不过更常见的原因是：①：服务器的并发连接数超过了其承载量，服务器会将其中一些连接Down掉；②：客户关掉了浏览器，而服务器还在给客户端发送数据；③：浏览器端按了Stop
[10054] Connection reset by peer
Connection reset by peer is a tough one because it can be caused by so many things. In all cases, the server determines that the socket is no longer good and closes it from its side.
Read Error
Scenario: Mary couldn't make out what Joe was saying anymore, so she hung up rather than lose his messages (data).
A read error occurs when a server cannot successfully read from a user's client. Servers gather information from the client by text, setup, and other items.When the server receives an error when reading from a client, it then disconnects the user, resulting in a read error quit message.
Write Error
Scenario: Mary was trying to talk to Joe but didn't think she was getting through, so she hung rather than lose his messages (data).
A write error occurs when a server cannot successfully write to a user's client. When the server receives information, it usually responds with information of its own. When the server receives an error when writing to a client, it then disconnects the user, resulting in a write error quit message similar to the read error format.
Ping Timeout Error
Scenario: Mary, having been raised in a household with too many kids and always craving attention, keeps asking to make sure that Joe is still on the line and listening. If he doesn't reply fast enough to suit her, she hangs up.
Servers automatically ping users at a preset time. The reason for this is to ensure the client is still connected to the server. When you see "PING? PONG!" results in your status window, it means the server has pinged your client, and it has responded back with a pong to ensure the server that you are still connected. When this does not happen and you disconnect without the server's knowledge, the server will automatically disconnect the user when it does not receive a response, resulting in a ping timeout. Ping timeouts occur to EVERYONE.
Broken pipe Error
Scenario: Mary had picked up a sticky note with a message she needed to relay to Joe, but somehow between her hand and her mouth, the message got misplaced. Mary was trying to talk to Joe but didn't think she was getting through, so she hung up rather than lose his messages (data).
A broken pipe error occurs when the server knows it has a message but can't seem to use its internal data link to get the data out to the socket.
Miscellaneous
Scenario: Lots of other reasons; perhaps the operator broke in and gave Mary a message that made her doubt the validity of the call so she hung up.作者: hongbo 时间: 2009-12-17 13:28
我也遇到过这样的问题,没有找到解决问题的办法!作者: renquande 时间: 2009-12-17 16:50 标题: 回复 10# 的帖子 这个应该是参数的问题，说明用户没有登录成功，请查看参数是否正确且设置是否正确作者: zymint 时间: 2010-10-22 11:06
碰到相同的问题，求解作者: yxd2006 时间: 2011-8-22 15:37
关注中......作者: zhang.yuandong 时间: 2011-8-23 15:22
........作者: shu123 时间: 2011-11-17 11:16
有解决的没？俺也遇到了这种问题。。。作者: test7 时间: 2011-12-20 17:01
我也遇到这个问题了，用zee 的方法解决了作者: 491623644 时间: 2012-6-1 09:22
我觉得应该是服务器还在送数据的时候客户端就已经关闭了作者: 让爱一起飞 时间: 2012-8-17 11:47
看到zee版主来帮助回答问题，好欣喜啊，他的方法准没错！作者: insight 时间: 2012-9-13 15:04
我试了放到Action还是没有解决啊
