您的位置:首页 > 其它

使用Control 产生压力后,生成的Analysis中提示错误,无法生成完整的graph的解决办法

2010-01-25 17:17 971 查看
在使用Loadrunner的Control 产生压力后,生成的Analysis中提示如下:

The following graph(s) were not created:
1. Hit per second
2. Throughput
3. Transaction Summary
4. Average Transaction Response Time
Possible reason:
The graph, as defined, results in no data.

同时,还生成了一个错误日志analysislog.log,里面显示的内容摘要如下:

Analysis Error log: <2010-1-25 15:04:43>
75003 Transaction : <vuser_init_Transaction> InstanceID: 8589934593. Vuser not found
Data Point : <HTTP_302>. Vuser:10 Group: 05 not found
Data Point : <HTTP_404>. Vuser:10 Group: 05 not found
75003 Transaction : <vuser_init_Transaction> InstanceID: 4294967297. Vuser not found
Data Point : <HTTP_404>. Vuser:10 Group: 05 not found
Data Point : <HTTP_404>. Vuser:10 Group: 05 not found
75003 Transaction : <Action_Transaction> InstanceID: 8589934594. Vuser not found
Data Point : <HTTP_200>. Vuser:10 Group: 05 not found
Data Point : <tcp_connection_count>. Vuser:10 Group: 05 not found
Data Point : <tcp_connect>. Vuser:10 Group: 05 not found
Data Point : <tcp_shutdown>. Vuser:10 Group: 05 not found
Data Point : <HTTP_302>. Vuser:10 Group: 05 not found
Data Point : <HTTP_404>. Vuser:10 Group: 05 not found
Data Point : <HTTP_302>. Vuser:2 Group: 05 not found
75003 Transaction : <http://10.8.101.106:8682/lndm/login.do?method=login> InstanceID: 4294967300. Vuser not found
75003 Transaction : <http://10.8.101.106:8682/lndm/portal.jsp;jsessionid=ED7D8F9136CD837B3DDD3B6E0B9AB6FB> InstanceID: 4294967302. Vuser not found
75003 Transaction : <http://10.8.101.106:8682/lndm/ui/css/widgets.css> InstanceID: 4294967304. Vuser not found
75003 Transaction : <http://10.8.101.106:8682/lndm/ui/css/layout.css> InstanceID: 4294967303. Vuser not found
75003 Transaction : <http://10.8.101.106:8682/lndm/ui/css/theme.css> InstanceID: 4294967305. Vuser not found
Data Point : <HTTP_404>. Vuser:2 Group: 05 not found
.......

经由多次试验,此原因为脚本名称为0(零)开头,将脚本名称修改为其他数字或是字母开头,就可以正常显示Analysis的所有graph了。

另外,如果不是脚本名称导致的,推荐其他解决方案:首先将结果保存,让其他人打开看看是否存在同样问题;如没有差异,可将脚本让其他人运行一下,看看是否存在同样问题;如果均不能解决,可以考虑重装一遍Loadrunner。

--肖楠
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: 
相关文章推荐