In a search test, the result tree contains an extraneous closing operation tag. This prevents the parser from displaying the result as XML. For example: in the following, the </operation> following </searchresult> should not exist. <ldapanswer> <operation> <opertype>search</opertype> <searchfilter>(samaccountname=example)</searchfilter> <searchbase>ou=bcbsnc users,dc=bcbsnc,dc=com</searchbase> <scope>2</scope> <countlimit>0</countlimit> <timelimit>0</timelimit> </operation> <searchresult> <dn>CN=example,ou=excample,dc=example,dc=com</dn> <returnedattr>1</returnedattr> <attribute> <attributename>displayName</attributename> <attributevalue>John Smith</attributevalue> </attribute> </searchresult> </operation> <responsecode>0</responsecode> <responsemessage>Success</responsemessage> </ldapanswer>
Created attachment 18747 [details] Patch for problem, with other enhancements This is a patch, made against the svn trunk from 3 days ago. It will solve this problem, has some extra features added and some changes to the userInterface. a patch for the manulas is still to be made :-(
Thanks very much! By the way, SVN trunk is rather out of date - 2.2 is built from branch/rel-2-2 - or is that what you meant? But I expect the patch can be made to work against the branch anyway.
*** Bug 40635 has been marked as a duplicate of this bug. ***
The patches did not seem to work properly, even against the revision quoted in them; however I think it has all now been committed OK. Please try the nightly build (any after r516970) [Note that I combined the bind & sbind panels, as sbind needed all the bind variables anyway]
No problems reported, so assuming fixed
This issue has been migrated to GitHub: https://github.com/apache/jmeter/issues/1765