You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ivan Rancati (Bug 38840):
I have a relatively simple JMeter WebService test plan, where I have the
following as listeners:
Aggregate Report
Assertion Results
View Results Tree
The
The plan runs against a XFire web service (although I have seen exactly the same
issue with an Axis server)
When I run it with 2 to 5 threads, all tests pass
If I use 10 threads, occasionally a test would fail.
Inspecting the sampled XML shows no problem, but if I check in the Assertion
Results viewer I see this line
Error in building: FWK005 parse may not be called while parsing.: FWK005 parse
may not be called while parsing.
I have run the test requests through a proxy, and the message is definitely not
coming from the Web Service, it's from JMeter.
From a quick Google search, it might be a problem with the fact that some XML
parsing is not thread safe.
Severity: normal
OS: Linux
The text was updated successfully, but these errors were encountered:
Ivan Rancati (Bug 38840):
I have a relatively simple JMeter WebService test plan, where I have the
following as listeners:
Aggregate Report
Assertion Results
View Results Tree
The
The plan runs against a XFire web service (although I have seen exactly the same
issue with an Axis server)
When I run it with 2 to 5 threads, all tests pass
If I use 10 threads, occasionally a test would fail.
Inspecting the sampled XML shows no problem, but if I check in the Assertion
Results viewer I see this line
Error in building: FWK005 parse may not be called while parsing.: FWK005 parse
may not be called while parsing.
I have run the test requests through a proxy, and the message is definitely not
coming from the Web Service, it's from JMeter.
From a quick Google search, it might be a problem with the fact that some XML
parsing is not thread safe.
Severity: normal
OS: Linux
The text was updated successfully, but these errors were encountered: