7.0.X, 7.1.X, Master
When many web content articles need to be updated (such as expiring them), Liferay will use a scheduler_dispatch thread to update them. However, Liferay does it all in one transaction.
This can cause issues because if the transaction fails for some reason, Liferay will need to roll it all back and try again later, only to fail and roll back again. When it comes to expiring web content, it is not necessary to use a single transaction because it is not critical to prevent "dirty reads" in this case.
Steps to Reproduce
1. Get a database other than MySQL since we will need to limit the database's transaction log size later. MySQL will automatically "break" the max log size limit, which is not what we want in this case. So I used DB2 10.5 (https://files.liferay.com/private/vms/vm-win2012r2/vm-win2012r2.vmdk.x64.db2-10.5.zip)
2. Assuming you're using DB2, create a database with a page size of 32k create database <DATABASENAME> using codeset utf8 territory us pagesize 32 k
3. Connect Liferay 7 to it:
Remember to add the JDBC driver [^db2jcc4.jar]
4. Start Liferay and deploy the [^liferay.dummy.factory-7.0.1.jar]. It can also be found at https://github.com/yasuflatland-lf/liferay-dummy-factory or alternatively use the attached groovy script.
5. Go to Control Panel -> Apps -> Dummy. Use the portlet to Create 200,000 web content. This will take about 2 hours.
6. Once the web content is created, shutdown Liferay
7. Go into the database (I used RazorSQL) and do a select * on JournalArticle. Copy a date from DISPLAYDATE.
8. You will update the Expiration Date to be any day before the Display Date. I used this query: update journalarticle set EXPIRATIONDATE ='2018-12-04 22:25:00.0'
9. Using DB2 Command Window (search for it in the Windows Start menu), minimize the transaction logs for DB2 by running these queries:
To verify that your settings took place, run this query and look for the logprimary and logsecond parameters:
10. Restart DB2, or since it's faster, restart Windows. I don't mean restart VMWare, I mean to make sure to restart the OS. This will make your settings from Step 9 take effect.
11. Start up Liferay, and wait. If you take thread dumps during this time, you should see scheduler threads like:
For me, it took about 9 minutes for Liferay to throw this error [^batch-error.txt]
Based on https://www-01.ibm.com/support/docview.wss?uid=swg21617184, this is error we want to see.
If you continue waiting, you'll see the error thrown again, every time the scheduler runs.
RESULT: Liferay was unable to commit the transaction so it rolls it back and tries again, only to fail and roll back again.
EXPECTED: Liferay can expire web contents in multiple transactions as a single transaction is unnecessary for this use case.