https://issues.apache.org/bugzilla/show_bug.cgi?id=48350
--- Comment #18 from Philippe Mouawad <p.moua...@ubik-ingenierie.com> 2010-03-06 19:22:20 UTC --- (In reply to comment #15) > I've been able to reproduce the problem with a slightly trimmed version of the > test plan. > > Using > > remote.configure(testTree, host); > instead of > remote.configure(test, host); > > does not stop the deadlocks. > > Nor does synchronizing on testTree, however using a static lock object does > work for me. > > The -G option does not seem to cause deadlocks. > > I'm not yet sure why there can be a deadlock; the code seems to create a > separate copy of the test tree for each client. Perhaps one of the nested data > structures is not being copied. If so, then fixing that should prevent the > deadlock. > > However this may be very tricky to find; in the meantime your original > suggested patch would prevent the deadlocks. > > I don't think it's necessary to synch. for the -G option. Hello, >From my investigations: - synchronizing on testTree doesn't do it because there are 2 different instances of test - and concerning this fix, it doesn't do it because due to HashTree testTree = test, test and testTree are the same object: > remote.configure(testTree, host); > instead of > remote.configure(test, host); Philippe. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-dev-unsubscr...@jakarta.apache.org For additional commands, e-mail: jmeter-dev-h...@jakarta.apache.org
