Bug 38840 - FWK005 parse error with Webservice sampler and 10+threads
FWK005 parse error with Webservice sampler and 10+threads
Status: RESOLVED FIXED
Product: JMeter
Classification: Unclassified
Component: Main
2.1.1
PC Linux
: P2 normal (vote)
: ---
Assigned To: JMeter issues mailing list
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2006-03-03 16:17 UTC by Ivan Rancati
Modified: 2006-03-12 05:02 UTC (History)
0 users



Attachments
Test plan that shows the parsing issue (125.69 KB, application/octet-stream)
2006-03-03 16:17 UTC, Ivan Rancati
Details
contains jmeter.log with debug settings (76.49 KB, application/zip)
2006-03-03 16:25 UTC, Ivan Rancati
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Rancati 2006-03-03 16:17:05 UTC
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.
Comment 1 Ivan Rancati 2006-03-03 16:17:54 UTC
Created attachment 17826 [details]
Test plan that shows the parsing issue
Comment 2 Ivan Rancati 2006-03-03 16:25:28 UTC
Created attachment 17827 [details]
contains jmeter.log with debug settings

See for example the error at line 11677
Comment 3 Sebb 2006-03-12 13:02:12 UTC
Sorry for the delay in looking at this.

XMLAssertion currently uses only a single jdom SAXBuilder for all threads, but
jdom is not thread-safe.

The code in the 2.1 branch has been updated to use a thread-local builder.