Description

On master and 7.0, the scheduled job that purges old ExportImportConfigurations takes care of purging the related BackgroundTasks as well, so this is not a problem there. But unfortunately there is no ExportImportConfiguration model on 6.2, it was a new feature for 7.0. So we need to make a unique solution for purging old BackgroundTasks on 6.2.

in you portal-ext.properties
2. Turn on staging and do publications to live several times (more than 2 times)
3. Check the backgroundtask table in the database: there should be a record for each publications
4. Wait an hour, don't shut down the portal
5. Check the backgroundtask table in the database: only the latest 2 background tasks should exist

Attachments

Issue Links

causes

LPS-84678java.sql.SQLException: ResultSet may only be accessed in a forward direction

Closed

relates

LPE-15540Old entries are not deleted from the Backgroundtask database table automatically