Re: Using paged results, between 2.2.26 and 2.3.38.

[Quanah Gibson-Mount <quanah@zimbra.com>]

--On Tuesday, October 23, 2007 9:27 AM -0300 Brandon Hume <hume-ol@bofh.ca> 
wrote:

> I've got a number of auditing/update/query programs that make use of the
> paged results extension for large queries
>
> Since upgrading the server to 2.3.38 from 2.2.26, all these programs
> have broken; they can retrieve the first page of results, but any
> attempt top fetch the next page results in a "paged results cookie is
> invalid or old" error.  The client programs and the server platform
> (Redhat AS3) are both unaltered between server versions.
>
> I can't find any references to changes with respect to paged results in
> CHANGES, except for the deadlock in bdb problem being fixed.
>
> Would anyone be able to provide some advice for debugging this, perhaps
> being able to see the cookie being assigned by the server and what the
> client is offering back?

Hm, we ran into this at Zimbra as well, and stopped using paged results 
entirely with 2.3.  It's in a bug assigned to me to investigate in Zimbra's 
bugzilla, I simply haven't had the time.  :/

--Quanah


--

Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration