Scheduled jobs do not get resolved in the default company with Database Partitioning enabled

• Type: Bug
• Status: Verified
• Resolution: Unresolved
• Affects Version/s: Master
• Fix Version/s: None
• Component/s: Core Infrastructure > Database Access
• Labels: None
• Fix Priority: 3

Description
If database partitioning is enabled, scheduled jobs properly work only in companies that are not the default company

Steps to Reproduce

1. Enable database partitioning, in portal-ext.properties set database.partitioning.enabled=true
2. Start portal with MySQL 5.7
3. Create a new company (assert that a new schema is created to assert DB Partitioning is still working as expected)
4. Schedule a Web Content to be published in the future in both the Default Company as well as the newly created company (the default scheduler refresh time is 15minutes i believe, you can adjust this in instance settings for convenience)
5. After each of the scheduled times are up, assert that both web contents created are now in the published state (they should be now visible in a site page as well)

Expected Result
Scheduled Web Contents will get resolved and publish in both the default and the newly created company

Actual Result
Scheduled Web Contents will only get resolved and published outside of the default company, but will never get resolved in the default company

Tested on Tomcat 9.0.17 + PostgreSQL 10.6
Portal master GIT ID: 0df14b8ed544d2c0286c4cc200703e3005e673ad strong text