[Tickets #7478] Re: adding contact to chained ldap slave server causes error message

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/7478
------------------------------------------------------------------------------
  Ticket             | 7478
  Updated By         | tolan at bgz-consultants.com
  Summary            | adding contact to chained ldap slave server causes
                     | error message
  Queue              | Turba
  Version            | 2.3
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


tolan at bgz-consultants.com (2008-10-15 09:42) wrote:

> Mmm, true; but, if we remove that, then you still might hit an error
> on the display page after the redirect. So just removing that check
> doesn't seem like it'll really solve the problem.

I'd suggest that the add function isn't the right place to make the  
check though. If ldap confirms it was added successfully then the add  
function should be happy.

Perhaps the code that displays an entry could retry a few times with a  
short sleep in-between if it fails to find an object? For example  
four, quarter second, sleeps would minimise wait time, and still give  
up to a second for replication. Obviously those particular values  
might not be appropriate, I don't know how long the sync might take,  
but something along those lines?