JDBC Datasource Configuration Properties

Property Name Default Value Type Description

Property Name	Default Value	Type	Description
`stacksaga.mysql.datasource.pool-type`	`shared_pool`	Enum	StackSaga support tow different connection pools for retrying and general transactions.+ By default `shared_pool` is used for both. but if you want to use two different connection pools you can provide the type as `separate_pool`.
`stacksaga.mysql.datasource.maximum-retry-pool-size`	`10`	int	If you have configured `shared_pool`, then you can configure the maximum pool size for the retry-pool.
`stacksaga.mysql.datasource.minimum-retry-idle`	`10`	int	If you have configured `shared_pool`, then idle pool size for the retry-pool
`stacksaga.mysql.datasource.ddl-auto`	`update`	Enum	The database should be updated or creating by dropping when the application is started.
NOTE: Due to StackSaga internally uses HikariCP for managing the connection pool, all other regular configurations can be done according the HikariCP Configurations like username, password, connectionTimeout etc. The prefix is `stacksaga.datasource`
`stacksaga.mysql.datasource.retry.crashed-restore-retention-period`	`3600` (In seconds)	long	How long the transaction should be kept waiting to determine whether the transaction unexpectedly crashed.
`stacksaga.mysql.datasource.retry.retention-period`	`300` (In seconds)	long	How long the transaction should be kept waiting to next expose the transaction for retrying. This ensures that avoiding the transaction retrying frequently withing a short period of time. the transaction is frozen for some period of time, even the transaction is failed again after retrying recently.

stacksaga.mysql.datasource.pool-type

shared_pool

Enum

StackSaga support tow different connection pools for retrying and general transactions.+ By default shared_pool is used for both. but if you want to use two different connection pools you can provide the type as separate_pool.

stacksaga.mysql.datasource.maximum-retry-pool-size

10

int

If you have configured shared_pool, then you can configure the maximum pool size for the retry-pool.

stacksaga.mysql.datasource.minimum-retry-idle

10

int

If you have configured shared_pool, then idle pool size for the retry-pool

stacksaga.mysql.datasource.ddl-auto

update

Enum

The database should be updated or creating by dropping when the application is started.

NOTE: Due to StackSaga internally uses HikariCP for managing the connection pool, all other regular configurations can be done according the HikariCP Configurations like username, password, connectionTimeout etc.
The prefix is stacksaga.datasource

stacksaga.mysql.datasource.retry.crashed-restore-retention-period

3600 (In seconds)

long

How long the transaction should be kept waiting to determine whether the transaction unexpectedly crashed.

stacksaga.mysql.datasource.retry.retention-period

300 (In seconds)

long

How long the transaction should be kept waiting to next expose the transaction for retrying. This ensures that avoiding the transaction retrying frequently withing a short period of time. the transaction is frozen for some period of time, even the transaction is failed again after retrying recently.