DO NOT REPLY [Bug 48350] Deadlock on distributed testing with 2 clients

https://issues.apache.org/bugzilla/show_bug.cgi?id=48350

Sebb <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO

--- Comment #5 from Sebb <[email protected]> 2010-03-06 15:17:59 UTC ---
Thanks very much for the thread dump and patch.
It's not obvious why the deadlock occurs, because each remote host has its own
ClientJMeterEngine.

Do you have a simpler test case that shows the problem?

Also, do you use the -G options at all?

Seems to me that this could perhaps also cause a deadlock, as the
ClientJMeterEngine code for this is fairly similar.

Perhaps you could try a test with your patch plus a dummy -G option, e.g. just
add

-Gdummy=1

to the client startup.

If this also causes deadlocks, then the remote.setProperties() call probably
needs to be moved into the synch. block as well.

Could you also please try:

remote.configure(testTree, host);
instead of
remote.configure(test, host);

without the synch. block?

Might also be worth trying synchronising on (testTree) with the above change.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.