Each custom setting consists of a name and a value. For example, to set the hash algorithm to BCRYPT you add a custom setting with name HashAlgorithm and value BCRYPT . For a more detailed list of settings and example values, consult full-documented-m2ee.yaml .

If you are running your app on Mendix Cloud or SAP Business Technology Platform, you can access these settings by opening your app in Apps and choosing Environments > Environment Details > Runtime > Custom Runtime Settings . For more information see:

the Runtime Tab section of Environment Details for information about Mendix Cloud

the Runtime tab section of SAP Business Technology Platform for information about the SAP BTP

When you are running your app locally, you can set these values in a Configuration .

There is more information on how this is done in the Cloud Foundry buildpack in Custom Runtime Settings in the GitHub repo.

Duration/Interval Settings

Durations and intervals can be specified in the following formats:

ISO 8601 Periods , such as P7D , PT1H30M , or PT1S (See https://en.wikipedia.org/wiki/ISO_8601#Durations for more information)

HOCON durations , such as 7 days , 90m , or 1 second (See https://github.com/lightbend/config/blob/main/HOCON.md#duration-format for more information)

General Settings

The following custom settings can be configured:

Description Default Value ApplicationRootUrl see ApplicationRootUrl , below In Mendix Cloud, https://[domain]. mendixcloud. com CACertificates A comma-separated list of paths to CA certificates. Example: D:\App\CA1.pem, D:\App\CA2.pem, D:\App\CA3.pem, D:\App\CA4.pem ClientCertificatePasswords Comma-separated list of passwords for Client Certificates (should match the ClientCertificates order). Example: pwd1, pwd2, pwd3, pwd4 ClientCertificates Comma-separated list of paths to Client Certificates. Example: D:\App\Mx1.pfx, D:\App\Mx2.pfx, D:\App\Mx3.pfx, D:\App\Mx4.pfx ClientCertificateUsages Only use this when you have multiple client certificates and you want to configure specific certificates for specific servers.
This setting defines which service must use which client certificate. See NoClientCertificateUsages if you want to make sure that no client certificate is used for a certain host or web service. The value of ClientCertificateUsages must be a comma-separated list of key/value items. A key/value item must be specified as "identifier": "path to certificate" .
For web services, use the imported web service name as the identifier.
For REST services, use the host name of the remote server as the identifier.
Please note that any backslash in the path must be doubled. The whole value must be enclosed by braces ( { } ). For example: ClusterManagerActionInterval The interval (in milliseconds) used for performing all cluster manager actions. These actions include, unblocking users, and removing invalid sessions. If nothing is specified the interval is half the SessionTimeout . 300000 (5 minutes) com. mendix. core. isClusterSlave Set to true in a high-availability scenario when this is not the Cluster Leader . The buildpack will usually enforce this setting, but it may need to be set for some on-premises deployments. false com. mendix. core. SameSiteCookies The SameSite property can be included in all cookies that are returned by the embedded HTTP server. The possible values are Strict , Lax , and None . The default is Strict . Setting it to None is typically needed only when an application is embedded in an iframe of another application with a different domain. Newer browsers may require the connection to be secure (HTTPS) when set to None . If the connection is plain HTTP, then this setting must be changed to Strict (recommended) or Lax . com. mendix. core. ScheduledEventsCleanupAge This setting specifies (in milliseconds) how old objects in the System. ScheduledEventInformation table have to be before they are removed from the database. See Scheduled Events - Legacy for more details. 365 days for projects migrated from Mendix 9 and 7 days for new projects or projects with an empty database. com. mendix. core. ScheduledEventsCleanupBatchSize This setting specifies how many System. ScheduledEventInformation objects will be removed from the database each time the ScheduledEventInformation cleanup task runs. See Scheduled Events - Legacy for more details.
This setting was introduced in Mendix version 10.9.0 10000 com. mendix. core. SessionIdCookieName Defines the name of the cookie value which represents the session ID. Can be useful to change when running in a container which assumes a certain name for the session cookie. XASSESSIONID com. mendix. core. StorageService Defines which storage service module will be used. The storage service module takes care of storing the actual files associated with System.FileDocument objects, such as uploaded files. Possible values are com.mendix.storage. localfilesystem , com.mendix.storage.s3 , and com.mendix.storage.azure . com. mendix. storage. localfilesystem com. mendix. core. UseMimeDecoderForBase64 The setting defines whether to use the Basic decoder ( RFC 4648 ) or MIME decoder ( RFC 2045 ) when decoding base64 binary data. The Basic decoder is recommended due to its strictness in not accepting any character outside the Base64 specification, see Security Considerations . This setting exists for reasons of backward compatibility.
com. mendix. storage. PerformDeleteFromStorage Defines whether a delete of a Mendix file document should result in an actual delete in the storage service. A reason to not perform an actual delete in the storage service can be when it is also used as a backup service. The options are:

• AllFiles – Deletes files from file storage
• TemporaryFiles – Deletes files which were created during a transaction but not referenced by any file document from file storage
• NoFiles – No files are deleted from file storage.

Additionally, we have legacy options true (same as AllFiles ) and false (same as TemporaryFiles ) which will be deprecated in the future. com. mendix. core. ProcessedTasksCleanupAge This setting specifies (in milliseconds) how old objects in the System. ProcessedQueueTask have to be before they are removed from the database. See Task Queue for more details. 365 days for projects migrated from Mendix 9 and 7 days for new projects or projects with an empty database. com. mendix. core. ProcessedTasksCleanupBatchSize This setting specifies how many System. ProcessedQueueTask objects will be removed from the database each time the ProcessedTask cleanup action runs. See Task Queue for more details.
This setting was introduced in Mendix version 10.9.0 10000 EnableApacheCommonsLogging Some libraries used by the Mendix runtime use Apache Commons for logging. By default these log messages are suppressed. Set this value to true to receive the log messages from these libraries in the Mendix logs. false HashAlgorithm Specifies the hash algorithm used to generate hash values for attributes of the HashString type, such as the password of a user. This setting overrides the setting in Studio Pro, see Hash Algorithm . Possible values are BCRYPT , SSHA256 , SHA256 (not recommended) and MD5 (not recommended). To override the default BCrypt cost, you can specify BCRYPT:cost , where ‘cost’ is a number between 10 and 30. An example value is BCRYPT:12 . BCRYPT http. client. CleanupAfterSeconds For the call REST service and call web service activities, the first request to a new host will create an HTTP client that will handle subsequent requests. When there are no new requests to the host for the specified time, the HTTP client will be cleaned up. A value of 0 means no cleanup.
If your app uses these calls, it is strongly recommended that this value is increased. The default could prevent multiple end-users accessing the API simultaneously. A good value is around the number of concurrent users you expect, with a maximum of 250. The value of http.client. MaxConnectionsTotal may also need to increase. LongLivedSessionTimeout This setting is the same as SessionTimeout , but specific to offline-first progressive web apps. 604800000 (7 days) MyScheduledEvents A comma-separated string with the names of the events. Please don’t forget the name of the module (a name can be, for example, CRM.UpdateCustomerStatistics ). ScheduledEventExecution Specify which scheduled events should be executed. Choices are ALL , NONE , or SPECIFIED . In the case of SPECIFIED , enumerate the scheduled events using the MyScheduledEvents configuration option described below. SessionKeepAliveUpdatesInterval Defines how often a runtime writes session LastActive dates in its memory back to the database. one sixth of the value configured for the SessionTimeout setting; if the SessionTimeout is not set, this value defaults to 100000 (100 seconds) SessionTimeout Defines after how much time a session becomes invalid (in milliseconds). After that timeout, a session becomes eligible for removal. The session will not be destroyed until the next time a scheduled task runs to clean up the active sessions. 600000 (10 minutes) TaskQueue. ShutdownGracePeriod Time in ms to wait for task in a task queue to finish when shutting down. 10000 (10 seconds) TempPath The location of the temporary files. [deployment folder]\data\tmp TrackWebServiceUserLastLogin Defines whether to update a user’s LastLogin field on each login when logging in to a published REST, OData, or web service. When this happens a database update query has to be sent and this can have performance consequences on heavy load systems. When this setting is set to false, no database interaction is necessary. UploadedFilesPath The location of the uploaded files. A valid path can be: \\FileServer\CustomerPortalFiles . [deployment folder]\data\files EnableFileDocumentCaching 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 ObjectManagement. StrictChangeBehavior Defines the behavior when changing values of Enums and Calculated attributes.
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.
When set to false, changes to the values of Enums and/or Calculated attributes will be allowed.
We plan to remove this setting in Mendix 11, after which, an exception will always be raised when setting an invalid value. mapping.import.MaxJsonReadingLength 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 for more information.
This setting was introduced in Mendix version 10.9.0 and Mendix MTS version 10.6, patch version 10.6.5. 20000000 (dependent on library version)

ApplicationRootUrl

The ApplicationRootUrl setting is used to specify the domain and path to your application. This can be used within Java actions to get the public location of the application, for example when including a URL to the application when sending emails from a scheduled event.

There are two main ways that you might use to host multiple applications.

Routing based on a (sub)domain

Routing based on a subpath (supported since Mendix 10.3.0)

Say we are hosting two apps, App1 and App2. In domain-based routing, every app gets its own domain (for example. app1.domain.com and app2.domain.com ). In subpath-based routing, this would be on a subpath, for example domain.com/app1 and domain.com/app2 .

When setting up either routing variant, most content is correctly served automatically as it is relative to the path in which it is being served. Exceptions to this include:

Client components that automatically forward/route you to a top-level domain

Content that specifies a full path to your public domain/path

For the first case, domain-based routing is generally more stable, although path-based routing is possible with Mendix version 10.3.0 or above.

Examples of the second case are OData contracts, sending mails to your organization, and any place you want to render a static URL in your application. For this case it is possible to specify the ApplicationRootUrl.

Multiple External Domains

Mendix systems like OData that generate content based on a http request to the server, will use the headers passed (for example, by a proxy) to generate content. These headers are X-Forwarded-Proto , X-Forwarded-Scheme , X-Forwarded-Host , X-Forwarded-Port , X-Forwarded-Prefix and Host . For Mendix 10 and above, ApplicationRootUrl will take precedence over these headers. If you host a single application on two or more domains, you will have to choose one of the domains to represent the public-facing URL.

Log File Settings

The settings below influence the behavior of the log files. These settings can only be used on premises. In the cloud, these settings do not change any behavior.

Description Default Value LogFileName The name of the log file. The log files (actual log file plus back-up files) will be placed in the folder specified by the setting log path. Application.log MaxLogFileSize The maximum size per log file. When the log file reaches this maximum size, the log file will be backed up and a new empty log file will be used. 2097152 (2 MB) MaxLogFileCount The maximum count of log files preserved (actual file plus back-up files). When the maximum count is reached, the oldest backup file will be removed.

Database Settings

Common Settings

Description Default Value DatabaseHost The host name and optionally the TCP port number of the database. Use a colon ( : ) as separator between the host name and port number. Possible values are: db.url.org , db.url.org:1521 , 10.0.0.5 , and 10.0.0.5:1433 . It is possible to use a plain IPv6 address by enclosing it in brackets (for example, [::1]:5432 ).
This will be overridden if you supply DatabaseJdbcUrl . DatabaseName The name of the database or schema used by the Mendix app
This will be overridden if you supply DatabaseJdbcUrl . DatabaseJdbcUrl Defines the JDBC URL to use for the database connection (which overrides the other database connection settings). DatabaseUseSsl When true , the connection will be made using SSL without certificate validation. If you need certificate validation, use DatabaseJdbcUrl instead.
When false , the connection will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). DatabaseUseIntegratedSecurity This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used.
Ensure that the proper domain user for accessing the SQL Server is authenticated on the runtime server using the kinit command. false LogMinDurationQuery Defines whether database queries are logged via the ConnectionBus_Queries log node if they finished after the number of milliseconds specified here. By default, only the relevant SQL query will be logged. Set the log level of the ConnectionBus_Queries log node to TRACE to show more information about the page or the microflow which leads to this query. OracleServiceName Defines the SERVICE_NAME when you have a connection with an Oracle DBMS. DataStorage.EnableDiagnostics This setting can be used to generate a uniqueness constraint violation report. false UseNetworkTimeout This setting is applied to PostgreSQL. It affects the timeout mechanism used when reserving new ids for Mendix objects. If set to true, the socket level request timeout is used. In that case, the request timeout is handled within the operating system. If set to false, the timeout is handled by Mendix runtime. For other databases, timeouts are always handled by Mendix runtime. JdbcLoginTimeout This setting defines the database connection establishment time in milliseconds. 5000 (5 seconds) com.mendix.offline.SynchronizationCleanupInterval This setting defines how often objects of type System.OfflineSynchronizationHistory are cleaned up. 90 (90 days) DataStorage.OptimizeSecurityColumns When true, query columns generated to evaluate XPath constraints in access rules are optimized to true if the runtime can determine that the value will always be true for the objects that the query returns. This is almost always an improvement, but we have seen cases where the PostgreSQL query planner has worse performance for the simpler query. Supported since Mendix 10.17 false

Connection Pooling

The settings below are used to define the database connection pooling behavior. Mendix Runtime uses a pool of reusable database connections. You can, for example, define how many connections can be used. Connection pooling is implemented using the Apache Commons Object-pooling API .

These settings are configured per runtime instance . If you have scaled your application , the number of connections on the database side will be multiplied by the number of runtime instances. For example, if you set ConnectionPoolingMaxIdle to 50 and scale your app to 2 runtime instances, each runtime instance will create at most 50 connections, but on the database side this will lead to a maximum of 100 connections.

Value Default Value ConnectionPoolingMaxWait When the maximum number of “active” objects has been reached, the pool is said to be “exhausted.” The “when exhausted” action used by the connection bus is WHEN_EXHAUSTED_BLOCK . Sets the maximum amount of time (in milliseconds) the borrowObject() method should block before throwing an exception when the pool is exhausted. When less than or equal to 0 , the borrowObject() method may block indefinitely. (!) 10000 (10 seconds) ConnectionPoolingMaxActive Sets the cap on the total number of active instances from the pool. ConnectionPoolingMaxIdle Sets the cap on the number of “idle” instances in the pool. ConnectionPoolingMinIdle Sets the minimum number of objects allowed in the pool before the evictor thread (if active) spawns new objects. Note that no objects are created when numActive + numIdle >= maxActive . This setting has no effect if the idle object evictor is disabled (as in, if timeBetweenEvictionRunsMillis <= 0). ConnectionPoolingTimeBetweenEvictionRunsMillis Sets the number of milliseconds to sleep between runs of the idle object evictor thread. When non-positive, no idle object evictor thread will be run. 300 000 (5 minutes) ConnectionPoolingSoftMinEvictableIdleTimeMillis Sets the minimum amount of time an object may sit idle in the pool before it is eligible for eviction by the idle object evictor (if any), with the extra condition that at least minIdle objects remain in the pool. When non-positive, no objects will be evicted from the pool due to idle time alone. 300 000 (5 minutes) ConnectionPoolingNumTestsPerEvictionRun Sets the maximum number of objects to examine during each run of the idle object evictor thread (if any). When a negative value is supplied, ceil(getNumIdle())/ abs(getNumTestsPerEvictionRun()) tests will be run. This means that when the value is -n, roughly one nth of the idle objects will be tested per run. ConnectionPoolingTestOnBorrow If true , a database connection will be validated by the connection pool before returning it to the application. This can be useful in situations where database connections can be closed by processes outside of the Mendix runtime, like firewalls. Supported in Mendix version 10.6 in patch versions 10.6.4 and above, and in Mendix version 10.8.0 and above. false ConnectionPoolingTestOnCreate If true , a database connection will be validated by the connection pool after being created. Supported in Mendix version 10.6 in patch versions 10.6.4 and above, and in Mendix version 10.8.0 and above. false ConnectionPoolingTestOnReturn If true , a database connection will be validated by the connection pool when it is returned to the pool by the application. Supported in Mendix version 10.6 in patch versions 10.6.4 and above, and in Mendix version 10.8.0 and above. false ConnectionPoolingTestWhileIdle If true , all idle database connections will be validated when the idle object evictor runs. Supported in Mendix version 10.6 in patch versions 10.6.4 and above, and in Mendix version 10.8.0 and above. false

Migration Settings

The settings below are used to define the source database from which all data should be copied to the main database. You have to specify the settings below only once. The main database should exist and should be empty. During the app start-up, the data will be copied if the settings below are specified. Remove the settings afterwards, because they are not needed anymore.

Before the data copying process starts, the main database structure will be generated based on the source database structure. This is necessary to make sure all the data is copied without any problems, especially in cases where the source database has a larger element value than the current domain model specifies.

Value Default Value SourceBuiltInDatabasePath Defines the file location of the built-in source database. This setting is only necessary if a non-default location of the built-in database has to be used to copy the data from. [deployment folder]/data/database SourceDatabaseHost The host name and optionally the TCP port number of the source database. Use a colon as separator between host name and port number. Possible values are: db.url.org , db.url.org:1521 , 10.0.0.5 , or 10.0.0.5:1433 . It’s possible to use a plain IPv6 address by enclosing it in brackets (for example, [::1]:5432 ). SourceDatabaseJdbcUrl Defines the JDBC URL to use for the source database connection (which overrides the other source database connection settings). This feature is not supported for PostgreSQL databases. SourceDatabaseName The name of the source database. SourceDatabasePassword The password for the connection to the source database. SourceDatabaseType The type of the source database. Possible values: HSQLDB , MYSQL , ORACLE , POSTGRESQL , SAPHANA , or SQLSERVER . SourceDatabaseUseIntegratedSecurity This setting defines whether integrated security will be used to authenticate to SQL Server. If true, user name and password will not be used. See DatabaseUseIntegratedSecurity for more information. false SourceDatabaseUseSsl When true , the connection to the source database will be made using SSL without certificate validation. If you need certificate validation, use SourceDatabaseJdbcUrl instead.
When false , the connection to the source database will be made without SSL (this is only relevant for SQL Server, which uses SSL by default). SourceDatabaseUserName The user name for the connection to the source database. SourceOracleServiceName Defines the SERVICE_NAME when you have a connection with an Oracle DBMS as source. com. mendix. storage. s3. ResourceNamePrefix Prefix for the keys under which objects are stored. Separators are not added automatically to keys. For keys like prefix/key1 , com.mendix.storage.s3.ResourceNamePrefix should have value prefix/ . This setting is available in Mendix version 10.6 in patch versions 10.6.4 and above, and in Mendix version 10.8.0 and above. com. mendix. storage. s3. ResourceNameSuffix Suffix for the keys under which objects are stored. This can be used when S3 buckets are divided into different segments for different users with different credentials (for example, store objects as [key].customer1 for customer1 and as [key].customer2 for customer2). Separators are not added automatically to keys. For keys like key1.customer1 , com.mendix.storage.s3.ResourceNameSuffix should have value .customer1 . com. mendix. storage. s3. Region Sets the region in which the S3 bucket is located. This will be used to determine the service endpoint, unless overridden in com. mendix. storage. s3. EndPoint . This setting will also be used as the signing region for requests. com. mendix. storage. s3. EndPoint Overrides the default endpoint. This setting is required when the storage is on a non-AWS location (for example, IBM Cloud Object Storage). Both the endpoint (for example, s3.example.com ) or the full URL (including the protocol) are supported (for example, https://s3.example.com ). Note that when setting a custom endpoint, path style access will be enabled. For more information, see Class S3ClientOptions . com. mendix. storage. s3. UseV2Auth Lets the authentication policy use Signature Version 2 instead of the default Signature Version 4 . Set this setting to true when the endpoint does not support Signature Version 4 . false com. mendix. storage. s3. EncryptionKeys List of keys which can be used to encrypt and decrypt data at rest in S3. The right key to decrypt the data with is automatically selected depending on with which key it was encrypted. Each encryption key consists of a key id, the encryption algorithm and the actual key (Base64 encoded). Example: com. mendix. storage. s3. ForceGlobalBucketAccessEnabled The value true allows the server to route requests to a different region than specified in these settings ( false disallows it). com. mendix. storage. s3. MaxConnections Overrides the default maximum connections limit in the S3 service. The default value is enough for most applications, so we do not recommend explicitly setting this to a custom value unless a larger maximum connections limit is absolutely necessary. DEFAULT_MAX_CONNECTIONS field of the ClientConfiguration interface in the AWS SDK for Java. com. mendix. storage. s3. ClientExecutionTimeout Sets the amount of time (in milliseconds) to allow a call to the storage service to complete. A value of 0 means no timeout. For more information, see the AWS Java SDK . 0 (no timeout) com. mendix. storage. s3. ConnectionTimeout Sets the amount of time to wait (in milliseconds) when initially establishing a connection before giving up and timing out. A value of 0 means infinity and is not recommended. For more information, see the AWS Java SDK . 10.000 (10 seconds) com. mendix. storage. s3. SocketTimeout Sets the amount of time to wait (in milliseconds) for data to be transferred over an established, open connection before the connection times out and is closed. A value of 0 means infinity and is not recommended. For more information, see the AWS Java SDK . 50.000 (50 seconds) com. mendix. storage. s3. RequestTimeout Sets the amount of time to wait (in milliseconds) for the request to complete before giving up and timing out. A value of 0 means no timeout. For more information, see the AWS Java SDK . 0 (no timeout) com. mendix. storage. s3. UseCACertificates Set this value to true to use the configured CACertificates for the connection to the S3 service. false

Microsoft Azure SQL

These settings can be changed to use a Microsoft Azure SQL database for your Mendix application.

An alternative to using DatabaseUserName and DatabasePassword is appending Authentication=ActiveDirectoryDefault to the DatabaseJdbcUrl setting. This will use the credential information present in the running environment to connect to the database. See Connect using ActiveDirectoryDefault authentication mode and DefaultAzureCredential Class in the Microsoft documentation for more information. com. mendix. storage. azure. CreateContainerIfNotExists Indicates whether to check if the container exists, and creates it if it does not exist. com. mendix. storage. azure. ParallelismFactor Maximum number of parallel multi-part file uploads/downloads. We advise not changing this setting unless you experience slow file transfers for large files. Choosing larger values will lead to higher memory usage. com. mendix. storage. azure. UseHttps For enabling or disabling secure connections using HTTPS. Can be true or false . com. mendix. storage. azure. TimeoutIntervalInMs Sets the amount of time (in milliseconds) to allow a call to the storage service to complete. For more information, see the Azure libraries . No timeout com. mendix. storage. azure. MaximumExecutionTimeInMs Sets the maximum execution time (in milliseconds) to use when making this request. For more information, see the Azure libraries . No maximum time

¹ The com.mendix.storage.azure.BlobEndpoint setting can include the container name, as in https://storageaccount.blob.core.windows.net/some-container-name . In this case the value in the com.mendix.storage.azure.Container setting will be used as a directory name.

This behavior is broken in the following versions

8.18.28

9.24.14, 9.24.15, 9.24.16, 9.24.17, 9.24.18

10.6.1, 10.6.2, 10.6.3, 10.6.4, 10.6.5, 10.7.0, 10.8.0, 10.8.1.

In these versions, the container name in the com.mendix.storage.azure.BlobEndpoint setting is ignored and files are stored at the root of the container. If you upgrade to one of these versions from a previous version, you will no longer have access to any files uploaded previously.

Azure blob storage’s default connection protocol is HTTPS in order to encourage secure connections by default. This is a highly recommended best practice (for more information, see Configure Azure Storage Connection Strings ). This should now be transparent, unless you use custom domain names (for details, see Require Secure Transfer ). In that case, you should use the UseHttps setting above to revert to the previous default behavior and disable HTTPS. EnableKeepAlive Defines whether the web client sends a keep alive request every SessionTimeout/2 milliseconds, to prevent a session timeout. Each click in the browser also acts as KeepAlive. Disabling this property will result in a user being logged out automatically after 10 minutes of inactivity, even if the browser remains open. PhoneUserAgentRegEx Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a phone. The regular expression is matched against the user-agent header sent by the client’s web browser. Android, Mobile (iPhone, iPod, BlackBerry) TabletUserAgentRegEx Defines the regular expression that is used to determine whether a user is visiting a Mendix application from a tablet. The regular expression is matched against the User-Agent header sent by the client’s web browser. Android, iPad com. mendix. webui. HybridAppLoginTimeOut Determines how many minutes your token will remain valid before re-authenticating using your full credentials. If no value is set the token will expire after One year (Mendix version 10.9.0 and above) or never expire (Mendix versions below 10.9.0) . com. mendix. webui. FeedbackSizeWarningThreshold A warning is logged when the feedback size exceeds the threshold. Feedback is sent from server to client to instruct (for example, to refresh objects or to open a page). They are serialized as “instructions” in the server response. If there are too many instructions, this can have performance implications, as they all have to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. com. mendix. webui. StateSizeWarningThreshold A warning is logged when the state size exceeds the threshold. The state consists of changes in objects and of objects not committed to the database (yet). If there is too much state, this will have performance implications, as the whole state has to be serialized to the client. For this reason, a warning is logged when the threshold is exceeded. com. mendix. webui. CommittedObjectsThreshold The threshold controls how much data is sent back to the client after executing a microflow. By default, we send back full objects when they are changed or committed. When this threshold is reached, only object GUIDs are sent back instead so that the client knows about the changes while the amount of data sent over the network is reduced. The client will then retrieve the objects later on, if needed.

Metrics Settings

The settings below configure metrics through micrometer . See Metrics for more information and the specification of the settings format.

Description Default Value