On rare occasions, our web services respond to search query in a way which effectively swaps the results from two different queries by the same user. This is caused by an issues deep within the core library of the Java programming code used for Judici. Simply put, that code cannot resolve multithreaded calls properly at the microsecond level. This can be mitigated in one of two ways:
Make all calls on a single thread; OR
Make parallel threaded calls at a slower pace, using a short pause between each call.
Additionally, we have added into the SEARCHCASES results an echo-back of the search parameters associated with that return. You will find those as attributes in the <Results> element:
litigantName
dateOfBirth
These can be used as a comparison against the expected result sets. If they don't match, you can either:
Watch for the other affected query, and swap the results between the two queries
Discard the results and redo the queries