Bug 56862 - Unfriendly error message for configuration errors in JMeter
Summary: Unfriendly error message for configuration errors in JMeter
Status: NEW
Alias: None
Product: JMeter - Now in Github
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.9
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2014-08-15 20:47 UTC by Sai Zhang
Modified: 2014-11-16 13:00 UTC (History)
1 user (show)


Note You need to log in before you can comment on or make changes to this bug.
Description Sai Zhang 2014-08-15 20:47:26 UTC
Dear JMeter developers,

The error messages dumped by JMeter (caused by configuration errors) are rather confusing in some cases. I strongly suggest to improve these error messages. Doing so would dramatically improve JMeter's usability.

Here are two reproducible examples:


//if I set the following invalid option value in jmeter.properties

Jmeter simply dumps the error message:

Uncaught Exception java.lang.IllegalArgumentException: timeout value is negative. See log file for details.

(the above error message is really not informative. there is not much connection between "timeout" and the wrong option value "threadstop.wait". Further, the log file does not say anything too. This costs me extra debugging time for this simple mistakes. I would suggest to add show the *configuration name* or the *configuration value* in the error message)


Similar to the above error, if I set:


Jmeter dumps the error message:

Uncaught Exception java.lang.ExceptionInInitializerError. See log file for details.

This is even less useful, and the log file does not show anything useful either.

I would suggest to check the configuration option value when JMeter starts, and improve the corresponding error message (or logs).


Comment 1 Sai Zhang 2014-08-15 20:50:39 UTC
Another example:

//set a wrong value to the following option in jmeter.properities

Here is the error message dumped by JMeter:

An error occurred: null
Press any key to continue . . . 

I think that should be fixed too.
Comment 2 The ASF infrastructure team 2022-09-24 20:37:57 UTC
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/3418