[Tickets #13825] Re: Remi PHP update to 5.5.21-1 results in constant resyncing

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13825
------------------------------------------------------------------------------
  Ticket             | 13825
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Remi PHP update to 5.5.21-1 results in constant
                     | resyncing
  Queue              | Synchronization
  Version            | FRAMEWORK_5_2
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-02-04 18:23) wrote:


> The only thing I can think of is that this is a secondary effect to  
> the STATUS error, since the HIGHESTMODSEQ value returned from that  
> call is used to determine if we need to treat the server as  
> MODSEQ/CONDSTORE capable or not. If a server that has been treated  
> as MODSEQ is suddenly treated as not, that will cause all sorts of  
> issues with UID handling since we store different data structures  
> for each.

Actually, this wouldn't be the case since if the STATUS call fails (as  
it seems to be doing here), the code simply throws an exception and  
stops processing the request. So something else might be going on here.