jmeter 配置好了以后起不来,报错(详情见里面),哪位大神帮忙看一下啊!

Posted

tags:

篇首语:本文由小常识网(cha138.com)小编为大家整理,主要介绍了jmeter 配置好了以后起不来,报错(详情见里面),哪位大神帮忙看一下啊!相关的知识,希望对你有一定的参考价值。

Unrecognized VM option 'MaxLiveObjectEvacuationRatio=20'
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
errorlevel=1
请按任意键继续. . .

JDK是配置好的
C:>java -version
java version "1.8.0_65"
Java(TM) SE Runtime Environment (build 1.8.0_65-b17)
Java HotSpot(TM) Client VM (build 25.65-b01, mixed mode, sharing)
C:>

系统环境也配置了
JAVA_HOME:C:\Program Files (x86)\Java\jdk1.8.0_65;
JMETER_HOME:C:\jakarta-jmeter-2.3.4;
Path:%java_home%\bin;%jmeter_home%\bin;....
CLASSPATH:C:\Program Files (x86)\Java\jdk1.8.0_65\lib\dt.jar;C:\Program Files (x86)\Java\jdk1.8.0_65\lib\tools.jar;C:\Program Files (x86)\Java\jdk1.8.0_65\bin;C:\Program Files (x86)\Java\jdk1.8.0_65\lib;%JMETER_HOME%\lib\ext\ApacheJMeter_core.jar;%JMETER_HOME%\lib\jorphan.jar;%JMETER_HOME%\lib\logkit-1.2.jar;

1、首先在CSV文件中维护好数据,jmeter中调用执行,打开软件,点击线程登录接口 --》 添加 。

2、 配置元件 --》 CSV Data Set Config。

3、准备导入参数的文件  loginArgs.csv,内容包括:登录名、登录密码。

4、设置  CSV Data Set Config 参数项:重点设置:存放的文件,设置参数名,设置是否读取表头。

5、登录接口,账号、密码 参数化,即读取CSV Data Set Config中设置的参数,格式为$参数名。

6、运行接口,查看结果,参数化成功。

参考技术A 解决方案:
1、编辑jmeter.bat文件,将set DUMP=-XX:+HeapDumpOnOutOfMemoryError注释掉
2、JDK可能版本过高,可以试试1.6 或 1.7
3、jmter版本不对,可试试2.6 我用的就是2.6
4、如果jmeter长时间压测后,内存溢出,可重新解压缩安装目录,以删除缓存本回答被提问者和网友采纳
参考技术B

可以检查下,是不是安装的这个包

MRP进程起不来, 报错:ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], []

问题背景:
客户数据库服务架构为一主一备,某日备库操作系统意外重启,重启后Oracle MRP进程起不来,
报错:ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []

1> 检查MRP进程

技术图片
 1 SQL> select process,status from v$managed_standby;
 2 
 3 PROCESS STATUS
 4 ------- ------------
 5 ARCH CONNECTED
 6 ARCH CONNECTED
 7 MRP0 WAIT_FOR_LOG
 8 RFS RECEIVING
 9 
10 没有MRP进程,说明备库没有处于恢复状态。尝试启动MRP进程
11 alter database recover managed standby database disconnect from session ;
12 
13 MRP进程起不来,报错日志如下:
14 
15 Clearing online redo logfile 5 complete
16 Media Recovery Log /oraarchivelog/xxxx/oradb_1_227424_866810169.arc
17 Errors in file /u01/oracle/diag/rdbms/oradb/oradb/trace/oradb_pr00_5429.trc (incident=48266):
18 ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []
19 Incident details in: /u01/oracle/diag/rdbms/oradb/oradb/incident/incdir_48266/oradb_pr00_5429_i48266.trc
20 Completed: ALTER DATABASE RECOVER managed standby database disconnect from session 
21 Use ADRCI or Support Workbench to package the incident.
22 See Note 411.1 at My Oracle Support for error and packaging details.
23 Errors with log /oraarchivelog/oradb/oradb_1_227424_866810169.arc
24 MRP0: Background Media Recovery terminated with error 600
25 Errors in file /u01/oracle/diag/rdbms/oradb/oradb/trace/oradb_pr00_5429.trc:
26 ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []
27 Recovery interrupted!
28 Errors in file /u01/oracle/diag/rdbms/oradb/oradb/trace/oradb_pr00_5429.trc:
29 ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []
30 Errors in file /u01/oracle/diag/rdbms/oradb/oradb/trace/oradb_mrp0_5426.trc (incident=48257):
31 ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], [], [], [], []
32 ORA-10877: error signaled in parallel recovery slave 
33 ORA-10877: error signaled in parallel recovery slave 
34 ORA-10877: error signaled in parallel recovery slave 
35 ORA-10877: error signaled in parallel recovery slave 
36 ORA-10877: error signaled in parallel recovery slave 
37 ORA-10877: error signaled in parallel recovery slave 
38 ORA-10877: error signaled in parallel recovery slave 
39 Incident details in: /u01/oracle/diag/rdbms/oradb/oradb/incident/incdir_48257/oradb_mrp0_5426_i48257.trc
40 Use ADRCI or Support Workbench to package the incident.
41 See Note 411.1 at My Oracle Support for error and packaging details.
42 MRP0: Background Media Recovery process shutdown (oradb)
43 Dumping diagnostic data in directory=[cdmp_20180328134814], requested by (instance=1, osid=5429 (PR00)), summary=[incident=48266].
44 Sweep [inc][48266]: completed
45 Sweep [inc][48257]: completed
46 Sweep [inc2][48266]: completed
47 Sweep [inc2][48257]: completed
技术图片

 

发现这个600错误是备库在执行恢复的过程中,发现227424这个归档日志有问题或者找不到,导致日志应用失败,
错误原因是因为Errors with log /oraarchivelog/oradb/oradb_1_227424_866810169.arc
这条日志有问题,把归档日志下的这条日志删除,然后从主库传输过来这条日志,

2> 手动重新应用这条日志

1 alter database register OR replace logfile ‘/home/oracle/oradb_1_227424_866810169.arc‘;

 


3> 开启日志应用

1 alter database recover managed standby database disconnect from session;


或者数据库open状态下

1 alter database recover managed standby database using current logfile disconnect from session;


修复完成,问题解决

 

以上是关于jmeter 配置好了以后起不来,报错(详情见里面),哪位大神帮忙看一下啊!的主要内容,如果未能解决你的问题,请参考以下文章

一个因pid文件丢失,nginx的进程起不来,网站页面无法访问的故事

tomcat缓存

MRP进程起不来, 报错:ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], []

MRP进程起不来, 报错:ORA-00600: internal error code, arguments: [2619], [227424], [], [], [], [], [], [], []

hbase的HMaster进程起不来,是怎么回事

docker起不来报错:Failed to start Docker Application Container Engine.