From: firstname.lastname@example.org email@example.com On Behalf Of Philip Harle
Sent: Friday, October 14, 2016 10:22 AM
Subject: [grouper-users] Grouper 2.3 upgrade - NULL context_id causing PSP issues
We're currently upgrading of a clone of our live Grouper 2.2.2 installation to 2.3.0 using the grouperInstaller upgrade method.
We've managed to upgrade the API, UI and WS, and all is looking well. I'm now working on upgrading the PSP and have hit an issue.
The background PSP sync (run as part of our grouperloader service) isn't working and we're seeing the following in grouper_error.log:
2016-10-14 15:10:00,028: [DefaultQuartzScheduler_Worker-7] ERROR ChangeLogHelper.processRecords(252) - - Error
2016-10-14 15:10:00,029: [DefaultQuartzScheduler_Worker-7] ERROR ChangeLogHelper.processRecords(283) - - Did not get all the way through the batch! -1 != 3301919
From what I can tell this is because we had a small number of entries in grouper_change_log_entry with a NULL context_id. I cleared these out of the table, and the error no longer appeared in the log. However, when making any change in grouper it is still creating a new entry in the table with a NULL context_id.
Any ideas why this might be the case?
Our eventual plan is to move away from PSP in favour of PSPNG, but I feel we need to fix the above issue before proceeding.
Although, as an aside, can PSPNG be installed using the grouperInstaller on an installation that has been upgraded from 2.2, or do we need to install/configure it manually?