Azure Load Testing - Remove old MongoDB driver from classpath

Question

I want to run a load test where my test users are persisted in MongoDB.

Locally with JMeter 5.6.3 and JDK 21, I need to remove this old jar from the JMeter lib folder mongo-java-driver-2.14.3.jar. Once removed my uber jar gets loaded and everything works as expected.

In Azure I tried renaming my uber jar so it would get loaded first in the classpath but that didn't work.

What mechanism can I use to manage the classpath order of my dependencies in Azure Load Testing?

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

azure load testing does not allow you to control or reorder the builtin JMeter classpath. The platform ships with its own JMeter runtime and embedded libraries, including the old MongoDB driver, and those cannot be removed, overridden, or reordered.

The only reliable mechanism is to avoid the conflict entirely:

Shade/relocate your MongoDB classes inside your uber jar using Maven Shade or Gradle Shadow. Relocate the com.mongodb packages to a custom namespace so that the built-in driver is never picked up.

1. Do not rely on classpath order. load testing always loads its internal libs first, and you cannot change that.

In short, you cannot manage classpath ordering in azure load testing. You must relocate your dependencies to avoid conflicts with the bundled JMeter libraries.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.