Re: Running Multiple JMeter Tests in Parallel – Fi leServer Conflict Issue

--000000000000d94936063a1cb07d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Perhaps use:

Thread Lifetime in "Thread Group"


Deepak
"The greatness of a nation can be judged by the way its animals are treated
- Mahatma Gandhi"

+91 73500 12833
[email protected]

LinkedIn: www.linkedin.com/in/deicool

"Plant a Tree, Go Green"

Make In India : http://www.makeinindia.com/home


On Thu, Jul 17, 2025 at 2:47=E2=80=AFPM Sruthika Bachu <sruthikabachu22@gma=
il.com>
wrote:

> Hi all,
>
> I=E2=80=99m trying to run multiple JMeter test plans in parallel using Ja=
va
> threads, where each thread creates a new StandardJMeterEngine object
> and executes a different test.
>
> However, I=E2=80=99m facing an issue with FileServer. It appears to be a
> singleton and shared across all executions. As a result, when one test
> completes early, it calls FileServer.getFileServer().closeFiles(),
> which causes file-related errors in the other ongoing tests (e.g.,
> missing CSV files).
>
> I=E2=80=99d like to know:
>
> Is running multiple JMeter tests in parallel like this (multiple
> StandardJMeterEngine objects in the same JVM using threads) a
> supported use case?
>
> If not, is the correct approach to launch each test in a separate JVM
> (e.g., via ProcessBuilder)?
>
> Is there a way to isolate or override FileServer usage per test so
> that one doesn't affect the others?
>
> Any suggestions or guidance would be really helpful.
>
> Thanks,
> Sruthika
>

--000000000000d94936063a1cb07d--