ConceptsEnvironment Variables

Environment Variables

Certain parts of the engine are configured before reading the application configuration file, and therefore are set via environment variables.

Engine level

com.kubling.maxStringLength

By default, the string data type has a limit of 4,000 characters. However, you can increase this limit by setting the desired value in this environment variable.

com.kubling.transport.workerThreads

Specifies the number of worker threads used by the Engine transport layer to manage direct engine connections and transport-level request processing.

This setting affects only native Engine transports and does not apply to HTTP-based endpoints.

com.kubling.transport.maxMessageSize

Specifies the maximum message size, in bytes, accepted by the Engine transport layer.

Messages exceeding this limit are rejected before processing.

com.kubling.transport.maxStreamingLobSize

Specifies the maximum size, in bytes, allowed for streamed LOB (Large Object) transport operations.

This limit applies to transport-level streaming of large binary or character objects exchanged between the client and the Engine.

Application level

APP_CONFIG

The path to the application configuration YAML file.

MAIN_HTTP_PORT

Specifies the port on which Kubling exposes HTTP-based services.

ENABLE_WEB_CONSOLE

Specifies whether the web console endpoint is activated. This also enables the restart endpoint.

SCRIPT_LOG_LEVEL

Specifies the log level for messages from scripts to be printed.

MAX_HTTP_THREAD_POOL_SIZE

Specifies the maximum number of threads in the HTTP thread pool.

MAX_HTTP_WAITING_QUEUE_CAPACITY

Specifies the maximum capacity of the waiting queue for HTTP requests.

KBL_SKIP_ENV_VAR_TEMP_FILE_ENCRYPTION

Indicates whether the encryption of environment variables saved to disk (used for restarting the engine) should be skipped. When encryption is not skipped, and the container is stopped and restarted, the random key manager generates a new key. This new key cannot decrypt the file created during the previous run, causing issues with the restart process.

PERF_TRACER_RUN_ID

Identifier of the engine run that the performance tracer uses to write events. This is necessary when running complex, multi-run performance tests.

INST_AZ_MON_ACTIVE and INST_AZ_MON_KEY DEPRECATED Marked for removal

Variables related to Azure monitoring, enabling the feature and providing the necessary key.