Grouper Users - Open Discussion List

[Andrew Morgan <>]

On Fri, 13 Feb 2015, Kediyal, Prashant wrote:

> Hi,
>
> We have been having a few cases where we see valid web service requests 
> that get logged in the web services log but don't get provisioned 
> through our change log consumer code.
>
> When we look at the change log entry table we don't see the record 
> corresponding to the one logged in the web service log but we see it in 
> change_log_entry_temp. I am assuming That only the records in 
> change_log_entry result in an invocation of our change log consumer. 
> Question is what is the use of the change_log_entry_temp and if it is a 
> temporary holding table, then when will the record move to 
> change_log_entry so that our change log consumer receives it and then 
> proceeds to provision to our LDAP.

The Grouper loader daemon takes care of this.  From 
grouper-loader.base.properties:

##################################
## Change log
##################################

# should the change log temp to change log daemon run?  Note, this should be 
true
changeLog.changeLogTempToChangeLog.enable = true

#quartz cron-like schedule for change log temp to change log daemon, the 
default is 50 seconds after every minute: 50 * * * * ?
#leave blank to disable this
changeLog.changeLogTempToChangeLog.quartz.cron =


I don't understand the "leave blank to disable this" comment though.  My 
grouper-loader.base.properties has it blank (as I pasted above), but 
clearly it is running at 50 seconds every minute here.

        Andy