RQMExecutionTool: java.lang.NullPointerException
Hello,
I'm trying to execute RQM test suite using RQMExecutionTool. I have RQM 5.0.2.
I'm executing following command: java -cp RQMExecutionTool.jar com.ibm.rqm.executiontool.ExecutionUtility -tcerId=246024 -projectName="АС Юпитер" -publicURI="https://hs22-33.ca.sbrf.ru:9445/jazz" -user=user -password=pass -exitOnComplite=true
This brings following error:
log4j:WARN No appenders could be found for logger (com.ibm.rqm.executiontool.Exe
cutionUtility).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" java.lang.NullPointerException
at java.io.Reader.<init>(Unknown Source)
at java.io.InputStreamReader.<init>(Unknown Source)
at com.ibm.rqm.executiontool.ExecutionUtility.getHelpContent(Unknown Source)
at com.ibm.rqm.executiontool.ExecutionUtility.executeCommands(Unknown Source)
at com.ibm.rqm.executiontool.ExecutionUtility.main(Unknown Source)
2 answers
A few things were going on there.
1. There was a typo in the command line, as Don pointed out.
2. The RQMExecutionTool_readme.txt file is not in the current directory - hence the NullPointerException, as the tool tried to display the help content (due to the wrong parameter mentioned above) in this file but could not open it.
3. The log4j.properties file is not in the current directory - hence the two "log4j:WARN" messages for the same reason as above.
I guess you only took the .jar file from the package and try to use it. You should've extracted the whole package as is, and there would have been no problems. Also, you can run the tool in an easier way as
java -jar RQMExecutionTool.jar -tcerId=......
1. There was a typo in the command line, as Don pointed out.
2. The RQMExecutionTool_readme.txt file is not in the current directory - hence the NullPointerException, as the tool tried to display the help content (due to the wrong parameter mentioned above) in this file but could not open it.
3. The log4j.properties file is not in the current directory - hence the two "log4j:WARN" messages for the same reason as above.
I guess you only took the .jar file from the package and try to use it. You should've extracted the whole package as is, and there would have been no problems. Also, you can run the tool in an easier way as
java -jar RQMExecutionTool.jar -tcerId=......
Comments
Comments
Don Yang
Jul 05 '16, 1:12 a.m.