Merge pull request #10529 from atennapel/run/3355-session-batch-runtime-settings

[RUN-3355] Add SessionKeepAliveUpdateBatchSize and LastActionExecutionUpdateBatchSize runtime settings

Author: MarkvanMents

content/en/docs/refguide/runtime/custom-settings/_index.md

@@ -85,6 +85,8 @@ The following custom settings can be configured:
 | <a id="UploadedFilesPath" href="#UploadedFilesPath">UploadedFilesPath</a> | The location of the uploaded files. A valid path can be: `\\FileServer\CustomerPortalFiles`. | [deployment folder]\data\files |
 | <a id="EnableFileDocumentCaching" href="#EnableFileDocumentCaching">EnableFileDocumentCaching</a> | Defines whether file documents should be cached. Only enable this if you are sure that the file documents will not contain sensitive information. Images are always cached. | false |
 | <a id="mapping.import.MaxJsonReadingLength" href="#mapping.import.MaxJsonReadingLength">mapping.import.MaxJsonReadingLength</a> | The maximum length of the JSON string received from the remote which can be processed with import mapping. Use this setting when you expect a string which is longer than the default. See [Import Mappings](/refguide/import-mappings/#troubleshooting) for more information. | 20000000 *(dependent on library version)* |
+| <a id="LastActionExecutionUpdateBatchSize" href="#LastActionExecutionUpdateBatchSize">LastActionExecutionUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActionExecution` attribute in the periodic system task. | 1000 *Introduced in Mendix 11.6.1 and 11.7.0.* |
+| <a id="SessionKeepAliveUpdateBatchSize" href="#SessionKeepAliveUpdateBatchSize">SessionKeepAliveUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActive` attribute in the periodic system task. | 1000 *Introduced in Mendix 11.6.1 and 11.7.0.* |
 | <a id="UseOldExceptionBehavior" href="#UseOldExceptionBehavior">UseOldExceptionBehavior</a> | Allows you to set the exception message and wrapping behavior in the Mendix Runtime Server to the behavior below Mendix version 11.6.0. From Mendix 11.6.0 we changed the way messages are constructed to prevent the actual cause of the error being hidden in the details and exception wrapping is reduced significantly.<br/><br/>This change means that error messages will be different and have a significantly less deep exception nesting. Consequently, code which depends on finding some specific exception hardcoded at X levels deep (using `exception.getCause().getCause()` for example), will probably fail.<br/><br/>To restore the previous behavior, set `UseOldExceptionBehavior` to `true`. | false *Introduced in Mendix 11.6.0.* |
 
 ### ApplicationRootUrl {#applicationrooturl-section}

content/en/docs/refguide10/runtime/custom-settings/_index.md

@@ -77,6 +77,8 @@ The following custom settings can be configured:
 | <a id="EnableFileDocumentCaching" href="#EnableFileDocumentCaching">EnableFileDocumentCaching</a> | Defines whether file documents should be cached. Only enable this if you are sure that the file documents will not contain sensitive information. Images are always cached. | false |
 | <a id="ObjectManagementStrictChangeBehavior" href="#ObjectManagementStrictChangeBehavior">ObjectManagement.<wbr>StrictChangeBehavior</a> | Defines the behavior when changing values of Enums and Calculated attributes.<br/>When set to true, setting an invalid value for an Enum attribute and/or setting a value for a Calculated attribute will result in an InvalidEnumerationValueException and/or ReadOnlyAttributeException respectively.<br/>When set to false, changes to the values of Enums and/or Calculated attributes will be allowed.<br/>We plan to remove this setting in Mendix 11, after which, an exception will always be raised when setting an invalid value. | true |
 | <a id="mapping.import.MaxJsonReadingLength" href="#mapping.import.MaxJsonReadingLength">mapping.import.MaxJsonReadingLength</a> | The maximum length of the JSON string received from the remote which can be processed with import mapping. Use this setting when you expect a string which is longer than the default. See [Import Mappings](/refguide10/import-mappings/#troubleshooting) for more information. <br />*This setting was introduced in Mendix version 10.9.0 and Mendix version 10.6, patch version 10.6.5.* | 20000000 *(dependent on library version)* |
+| <a id="LastActionExecutionUpdateBatchSize" href="#LastActionExecutionUpdateBatchSize">LastActionExecutionUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActionExecution` attribute in the periodic system task. | 1000 *Introduced in Mendix 10.24.14.* |
+| <a id="SessionKeepAliveUpdateBatchSize" href="#SessionKeepAliveUpdateBatchSize">SessionKeepAliveUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActive` attribute in the periodic system task. | 1000 *Introduced in Mendix 10.24.14.* |
 
 ### ApplicationRootUrl {#applicationrooturl-section}
 

content/en/docs/refguide9/runtime/custom-settings/_index.md

@@ -77,6 +77,8 @@ The following custom settings can be configured:
 | <a id="TrackUserLastLoginForODataAndREST" href="#TrackUserLastLoginForODataAndREST">TrackUserLastLoginForODataAndREST</a> | Defines whether to update the user's `LastLogin` field on each interaction with a published OData and REST services. When this happens, a database update query has to be sent, which can have performance consequences on heavy load systems. When this setting is set to `false`, no database interaction is necessary. Ths setting is not available in Studio Pro 10, because this behavior is included in the [TrackWebServiceUserLastLogin](#TrackUserLastLoginForODataAndREST) setting. When setting this value to `false`, make sure to also set [TrackWebServiceUserLastLogin](#TrackUserLastLoginForODataAndREST) to `false` so a future upgrade to Studio Pro 10 keeps the behavior. *This setting was introduced in Studio Pro 9.24.34.* | true |
 | <a id="UploadedFilesPath" href="#UploadedFilesPath">UploadedFilesPath</a> | The location of the uploaded files. A valid path can be: `\\FileServer\CustomerPortalFiles`. | [deployment folder]\data\files |
 | <a id="mapping.import.MaxJsonReadingLength" href="#mapping.import.MaxJsonReadingLength">mapping.import.MaxJsonReadingLength</a> | The maximum length of the JSON string received from the remote which can be processed with import mapping. Use this setting when you expect a string which is longer than the default. See [Import Mappings](/refguide/import-mappings/#troubleshooting) for more information. <br />*This setting was introduced in Mendix version 9.24.17.* | 20000000 *(dependent on library version)* |
+| <a id="LastActionExecutionUpdateBatchSize" href="#LastActionExecutionUpdateBatchSize">LastActionExecutionUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActionExecution` attribute in the periodic system task. | 1000 *Introduced in Mendix 9.24.41.* |
+| <a id="SessionKeepAliveUpdateBatchSize" href="#SessionKeepAliveUpdateBatchSize">SessionKeepAliveUpdateBatchSize</a> | This setting specifies how many sessions should be updated per batch when updating the `LastActive` attribute in the periodic system task. | 1000 *Introduced in Mendix 9.24.41.* |
 
 ## Log File Settings