Grouper Developers Forum

["Michael R. Gettes" <>]

+1 to this request.  failures should block processing.  i view this similar 
to data replication - the idea is to keep the data in sync and if there are 
problems in the sync process, they should block, or, in the very least, be 
placed into an error queue. I hate the error queue notion but I do realize 
lots of products do things this way these days.

/mrg

On May 31, 2012, at 9:26, Lynn Garrison wrote:

>       Is there a way to stop the real time provisioning if there are 
> problems with the ldap server?   We moved to testing real time provisioning 
>  with  openldap.  During the provisioning testing, the file system became 
> full and ldap updates started returning errors.  
> 
> 
> 2012-05-31 09:15:16,001: [DefaultQuartzScheduler_Worker-8] ERROR 
> BaseSpmlProvider.execute(388) -  - Target 'psp' - Modify XML:
> <modifyResponse xmlns='urn:oasis:names:tc:SPML:2:0' status='failure' 
> requestID='2012/05/31-09:15:15.993' error='customError'>
>  <errorMessage>[LDAP: error code 80 - commit failed]</errorMessage>
> </modifyResponse>
> 
>       psp continued to process the change log events.  By the time we 
> realized what was happening, all the change log events had been processed 
> and only have the members were provisioned to the group.
> 
> 
> Lynn
> 
>