The problem can occur when you make use of the recordset paging option; for example by adding paging to a list.
Whether the problem occurs is related to the page size and the size of the records of the business object and is not easy to replicate.
The problem has now been fixed and requires you to upgrade the zX.dll runtime library and an optional change to your incDB.xml file.
The fix is inactivate by default; this to ensure backward compatibility. You can activate the fix by adding the following specific to your incDB.xml file:
This specific may have an impact on performance as paging is now implemented as skipping x records one-at-a-time. But at least it does not crash the server.
Happy MySQL paging!