Selenium WebDriver Sampler in JMeter Fails on AWS EC2: SeleniumManagerOutput Error

[poojahukkeri-CF]

jmeter-248.15_92_80T10-80-5202-71666642-ef8e-4504-9ecc-3f17f255cc67-eu-west-1.log

On executing a JMeter test plan that includes the WebDriver Sampler, which functions as expected in the local environment, but fails when run on AWS EC2 using Taurus (v3.2.3).

The uploaded ZIP file contains:

A .jmx test plan

A CSV file placed under the INPUT_FILES/ directory

Error Log

2025-08-01 05:36:27,576 ERROR c.g.j.p.w.s.WebDriverSampler: ❌ Error: org/openqa/selenium/manager/SeleniumManagerOutput
2025-08-01 05:36:27,663 ERROR c.g.j.p.w.s.WebDriverSampler: unknown protocol: about

Could you please confirm if there are any known issues or changes in the Taurus v3.2.3 template that could impact WebDriver Sampler execution on AWS?

[gockle]

Hi @poojahukkeri-CF

Can you confirm if this is related to Distributed Load Testing solution, the solution uses ECS Fargate to run the Jmeter tests and not EC2.

[poojahukkeri-CF]

Yes this is related to distributed load testing

[gockle]

Hi @poojahukkeri-CF

Distributed Load Testing on AWS does not support selenium framework, can you provide more details how you are using selenium? If you are using it ask part of the Jmeter script, the current version of the solution v3.4.0, uses AmazonLinux image and no longer uses Taurus. The new image does not install selenium plugins for blazemeter. Reference the line 17 in Dockerfile.