For sure it's not a JMeter bug, it's an example of Jar Hell <https://dzone.com/articles/what-is-jar-hell> where you have multiple versions of the same library in the CLASSPATH <https://docs.oracle.com/javase/tutorial/essential/environment/paths.html>
There are groovy-*.jar libraries in JMeter Classpath <https://jmeter.apache.org/usermanual/get-started.html#classpath> (lib folder of your JMeter installation) and JMeter automatically loads them on start and if you're adding more Groovy libraries to the classpath by any means it results in 2 same libraries of different versions with undefined order when it comes to classloading. If you want to use your own Groovy - remove JMeter's version and vice versa. Just in case if you cannot remove JMeter's libraries, the latest version of JMeter which was shipped with Groovy 2.4.12 was JMeter 3.3 <https://www.blazemeter.com/blog/whats-new-in-jmeter-3.3> Also according to JMeter Best Practices you should always be using the latest version of JMeter <https://jmeter.apache.org/usermanual/best-practices.html> which is JMeter 5.4.1 <http://www.jmeter-archive.org/ANNOUNCE-Apache-JMeter-5-4-1-released-td5739226.html> as of now and it comes with Groovy 3.0.7 so switching to JMeter's groovy or upgrading your installed SDK might be a viable solution. -- Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
