Federated Search Error

Question

Hi, I have developed a few federated search agents against our document management system. The search agents work great, etc, EXCEPT for one glitch. When the search is invoked, the portal contacts the search agent and the search builds the document result set and sends it back, all basic stuff. So, if i get 150 results the page display would show display 1-20 of 150. The problem arises when i click next to get the next set of data. The portal shows me the same 20 dsocuments i was looking at but says 21-40 of 150. Now if I click next and then previous or previous and then next it shows me the correct 21-40 documents and all others are fine. Upon investigsting the issue, I found that the portal was contacting the search agent once to get the search result, but when the user hit next for the first time the portal contacted the search agent again and reran the federated search, but everyother next or previous click after that it did not. Any ideas? it's almost like it forgot that it contacted the search agent the first time. Has anyone experienced this problem or know of a bug. The search agent was built verbatum from Plumtree documentation and even reviewed by Plumtree to no avail :(

Answer 1

What is the soap request saying for the following values? If the number to return is set to 10, for the second request, it should be:
<NumberToSkip >10</NumberToSkip> <MaximumReturn >10</MaximumReturn>
The only (non-bug) reason that NumberToSkip should not be set is if the TotalNumberOfHits was set to less than 10 (or whatever you have set for the number returned).