Thanks. I definitely removed far too much code originally - I'd assumed that some of the code following the Junit Test was only used by the test, but in fact it's just that the Test code is in the middle of the class, rather than at the end ...
It does seem to be working OK now - I've not seen the hang which triggered this all - but I would like to understand the code (one day!)... S. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 20 October 2003 18:58 To: JMeter Developers List Subject: RE: Threads sometimes get stuck in startup If I remember correctly, the pairing structure allows JMeter to remember which elements have been compiled already and which haven't. I can't remember why that was needed, but it was, and removing it will surely break some things. -Mike On 20 Oct 2003 at 13:26, BAZLEY, Sebastian wrote: > Oops! I removed way too much: pairing is not used for testing, but it does > seem to be write-only. > Perhaps it is being used to keep references alive? > Why is it static? > > I'm now unsure as to what any of the apparently unused items are for, so > I've put it all back, but made the accesses to pairing synchronized. This > will hopefully help. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
