Shouldn't the "pattern" member variable be populated when the object is instantiated at deserialization?
Sorry I'm not that familiar with serialization as I should be...
Anyway, I'm thinking the "pattern" should be static: if we have several assertions using the same pattern, we don't want to recompile it...
Something else: I just learned that to use a compiled pattern from different concurrent threads you need to compile it with a "READ_ONLY" flag (or similar).
I guess we'll need to have a deeper look at this, but first of all, I'd need to reproduce your problem. What O.S., JDK, etc. are you using?
Salut,
Jordi.
Scott Eade wrote:
Jordi, I don't have time to look into this right now, but the line:+ Pattern pattern = patternCache.getPattern(stringPattern);in ResponseAssertion.evaluateResponse() results in a NullPointerException when I run a remote JMeter session (it works fine locally). There is a remote possibility this is something odd at my end, but I don't think so. Cheers, Scott
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
