Appendix D. Thorntail fractions reference

For information about using the configuration properties provided in Thorntail fractions, see Section 7.4, “Configuring a Thorntail application”.

D.1. Archaius

Warning

This fraction is deprecated.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>archaius</artifactId>
</dependency>

D.2. Bean Validation

Provides class-level constraint and validation according to JSR 303.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>bean-validation</artifactId>
</dependency>

D.3. CDI

Provides context and dependency-injection support according to JSR-299.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>cdi</artifactId>
</dependency>

Configuration

thorntail.cdi.development-mode
Weld comes with a special mode for application development. When the development mode is enabled, certain built-in tools, which facilitate the development of CDI applications, are available. Setting this attribute to true activates the development mode.
thorntail.cdi.non-portable-mode
If true then the non-portable mode is enabled. The non-portable mode is suggested by the specification to overcome problems with legacy applications that do not use CDI SPI properly and may be rejected by more strict validation in CDI 1.1.
thorntail.cdi.require-bean-descriptor
If true then implicit bean archives without bean descriptor file (beans.xml) are ignored by Weld
thorntail.cdi.thread-pool-size
The number of threads to be used by the Weld thread pool. The pool is shared across all CDI-enabled deployments and used primarily for parallel Weld bootstrap.

D.3.1. CDI Configuration

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>cdi-config</artifactId>
</dependency>

D.4. Connector

Primarily an internal fraction used to provide support for higher-level fractions such as JCA (JSR-322).

If you require JCA support, please see the JCA fraction documentation.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>connector</artifactId>
</dependency>

D.5. Container

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>container</artifactId>
</dependency>

D.6. Datasources

Provides support for container-managed database connections.

D.6.1. Autodetectable drivers

If your application includes the appropriate vendor JDBC library in its normal dependencies, these drivers will be detected and installed by Thorntail without any additional effort.

The list of detectable drivers and their driver-name which may be used when defining a datasource is as follows:

Databasedriver-name

MySQL

mysql

PostgreSQL

postgresql

H2

h2

EnterpriseDB

edb

IBM DB2

ibmdb2

Oracle DB

oracle

Microsoft SQLServer

sqlserver

Sybase

sybase

Teiid

teiid

MariaDB

mariadb

Derby

derby

Hive2

hive2

PrestoDB

prestodb

D.6.2. Example datasource definitions

D.6.2.1. MySQL

An example of a MySQL datasource configuration with connection information, basic security, and validation options:

thorntail:
  datasources:
    data-sources:
      MyDS:
        driver-name: mysql
        connection-url: jdbc:mysql://localhost:3306/jbossdb
        user-name: admin
        password: admin
        valid-connection-checker-class-name: org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker
        validate-on-match: true
        background-validation: false
        exception-sorter-class-name: org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter

D.6.2.2. PostgreSQL

An example of a PostgreSQL datasource configuration with connection information, basic security, and validation options:

thorntail:
  datasources:
    data-sources:
      MyDS:
        driver-name: postgresql
        connection-url: jdbc:postgresql://localhost:5432/postgresdb
        user-name: admin
        password: admin
        valid-connection-checker-class-name: org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLValidConnectionChecker
        validate-on-match: true
        background-validation: false
        exception-sorter-class-name: org.jboss.jca.adapters.jdbc.extensions.postgres.PostgreSQLExceptionSorter

D.6.2.3. Oracle

An example of an Oracle datasource configuration with connection information, basic security, and validation options:

thorntail:
  datasources:
    data-sources:
      MyDS:
        driver-name: oracle
        connection-url: jdbc:oracle:thin:@localhost:1521:XE
        user-name: admin
        password: admin
        valid-connection-checker-class-name: org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker
        validate-on-match: true
        background-validation: false
        stale-connection-checker-class-name: org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker
        exception-sorter-class-name: org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>datasources</artifactId>
</dependency>

Configuration

thorntail.datasources.data-sources.KEY.allocation-retry
The allocation retry element indicates the number of times that allocating a connection should be tried before throwing an exception
thorntail.datasources.data-sources.KEY.allocation-retry-wait-millis
The allocation retry wait millis element specifies the amount of time, in milliseconds, to wait between retrying to allocate a connection
thorntail.datasources.data-sources.KEY.allow-multiple-users
Specifies if multiple users will access the datasource through the getConnection(user, password) method and hence if the internal pool type should account for that
thorntail.datasources.data-sources.KEY.authentication-context
The Elytron authentication context which defines the javax.security.auth.Subject that is used to distinguish connections in the pool.
thorntail.datasources.data-sources.KEY.background-validation
An element to specify that connections should be validated on a background thread versus being validated prior to use. Changing this value can be done only on disabled datasource, requires a server restart otherwise.
thorntail.datasources.data-sources.KEY.background-validation-millis
The background-validation-millis element specifies the amount of time, in milliseconds, that background validation will run. Changing this value can be done only on disabled datasource, requires a server restart otherwise
thorntail.datasources.data-sources.KEY.blocking-timeout-wait-millis
The blocking-timeout-millis element specifies the maximum time, in milliseconds, to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for locking a connection, and will never throw an exception if creating a new connection takes an inordinately long time
thorntail.datasources.data-sources.KEY.capacity-decrementer-class
Class defining the policy for decrementing connections in the pool
thorntail.datasources.data-sources.KEY.capacity-decrementer-properties
Properties to be injected in class defining the policy for decrementing connections in the pool
thorntail.datasources.data-sources.KEY.capacity-incrementer-class
Class defining the policy for incrementing connections in the pool
thorntail.datasources.data-sources.KEY.capacity-incrementer-properties
Properties to be injected in class defining the policy for incrementing connections in the pool
thorntail.datasources.data-sources.KEY.check-valid-connection-sql
Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is obtained from the pool
thorntail.datasources.data-sources.KEY.connectable
Enable the use of CMR. This feature means that a local resource can reliably participate in an XA transaction.
thorntail.datasources.data-sources.KEY.connection-listener-class
Speciefies class name extending org.jboss.jca.adapters.jdbc.spi.listener.ConnectionListener that provides a possible to listen for connection activation and passivation in order to perform actions before the connection is returned to the application or returned to the pool.
thorntail.datasources.data-sources.KEY.connection-listener-property
Properties to be injected in class specidied in connection-listener-class
thorntail.datasources.data-sources.KEY.connection-properties.KEY.value
Each connection-property specifies a string name/value pair with the property name coming from the name attribute and the value coming from the element content
thorntail.datasources.data-sources.KEY.connection-url
The JDBC driver connection URL
thorntail.datasources.data-sources.KEY.credential-reference
Credential (from Credential Store) to authenticate on data source
thorntail.datasources.data-sources.KEY.datasource-class
The fully qualified name of the JDBC datasource class
thorntail.datasources.data-sources.KEY.driver-class
The fully qualified name of the JDBC driver class
thorntail.datasources.data-sources.KEY.driver-name
Defines the JDBC driver the datasource should use. It is a symbolic name matching the the name of installed driver. In case the driver is deployed as jar, the name is the name of deployment unit
thorntail.datasources.data-sources.KEY.elytron-enabled
Enables Elytron security for handling authentication of connections. The Elytron authentication-context to be used will be current context if no context is specified (see authentication-context).
thorntail.datasources.data-sources.KEY.enlistment-trace
Defines if WildFly/IronJacamar should record enlistment traces
thorntail.datasources.data-sources.KEY.exception-sorter-class-name
An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides an isExceptionFatal(SQLException) method to validate if an exception should broadcast an error
thorntail.datasources.data-sources.KEY.exception-sorter-properties
The exception sorter properties
thorntail.datasources.data-sources.KEY.flush-strategy
Specifies how the pool should be flush in case of an error.
thorntail.datasources.data-sources.KEY.idle-timeout-minutes
The idle-timeout-minutes elements specifies the maximum time, in minutes, a connection may be idle before being closed. The actual maximum time depends also on the IdleRemover scan time, which is half of the smallest idle-timeout-minutes value of any pool. Changing this value can be done only on disabled datasource, requires a server restart otherwise.
thorntail.datasources.data-sources.KEY.initial-pool-size
The initial-pool-size element indicates the initial number of connections a pool should hold.
thorntail.datasources.data-sources.KEY.jndi-name
Specifies the JNDI name for the datasource
thorntail.datasources.data-sources.KEY.jta
Enable JTA integration
thorntail.datasources.data-sources.KEY.max-pool-size
The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool
thorntail.datasources.data-sources.KEY.mcp
Defines the ManagedConnectionPool implementation, f.ex. org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool
thorntail.datasources.data-sources.KEY.min-pool-size
The min-pool-size element specifies the minimum number of connections for a pool
thorntail.datasources.data-sources.KEY.new-connection-sql
Specifies an SQL statement to execute whenever a connection is added to the connection pool
thorntail.datasources.data-sources.KEY.password
Specifies the password used when creating a new connection
thorntail.datasources.data-sources.KEY.pool-fair
Defines if pool use should be fair
thorntail.datasources.data-sources.KEY.pool-prefill
Should the pool be prefilled. Changing this value can be done only on disabled datasource, requires a server restart otherwise.
thorntail.datasources.data-sources.KEY.pool-use-strict-min
Specifies if the min-pool-size should be considered strictly
thorntail.datasources.data-sources.KEY.prepared-statements-cache-size
The number of prepared statements per connection in an LRU cache
thorntail.datasources.data-sources.KEY.query-timeout
Any configured query timeout in seconds. If not provided no timeout will be set
thorntail.datasources.data-sources.KEY.reauth-plugin-class-name
The fully qualified class name of the reauthentication plugin implementation
thorntail.datasources.data-sources.KEY.reauth-plugin-properties
The properties for the reauthentication plugin
thorntail.datasources.data-sources.KEY.security-domain
Specifies the PicketBox security domain which defines the PicketBox javax.security.auth.Subject that are used to distinguish connections in the pool
thorntail.datasources.data-sources.KEY.set-tx-query-timeout
Whether to set the query timeout based on the time remaining until transaction timeout. Any configured query timeout will be used if there is no transaction
thorntail.datasources.data-sources.KEY.share-prepared-statements
Whether to share prepared statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement
thorntail.datasources.data-sources.KEY.spy
Enable spying of SQL statements
thorntail.datasources.data-sources.KEY.stale-connection-checker-class-name
An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides an isStaleConnection(SQLException) method which if it returns true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException
thorntail.datasources.data-sources.KEY.stale-connection-checker-properties
The stale connection checker properties
thorntail.datasources.data-sources.KEY.statistics-enabled
Define whether runtime statistics are enabled or not.
thorntail.datasources.data-sources.KEY.track-statements
Whether to check for unclosed statements when a connection is returned to the pool, result sets are closed, a statement is closed or return to the prepared statement cache. Valid values are: "false" - do not track statements, "true" - track statements and result sets and warn when they are not closed, "nowarn" - track statements but do not warn about them being unclosed
thorntail.datasources.data-sources.KEY.tracking
Defines if IronJacamar should track connection handles across transaction boundaries
thorntail.datasources.data-sources.KEY.transaction-isolation
Set the java.sql.Connection transaction isolation level. Valid values are: TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE and TRANSACTION_NONE. Different values are used to set customLevel using TransactionIsolation#customLevel
thorntail.datasources.data-sources.KEY.url-delimiter
Specifies the delimiter for URLs in connection-url for HA datasources
thorntail.datasources.data-sources.KEY.url-selector-strategy-class-name
A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
thorntail.datasources.data-sources.KEY.use-ccm
Enable the use of a cached connection manager
thorntail.datasources.data-sources.KEY.use-fast-fail
Whether to fail a connection allocation on the first try if it is invalid (true) or keep trying until the pool is exhausted of all potential connections (false)
thorntail.datasources.data-sources.KEY.use-java-context
Setting this to false will bind the datasource into global JNDI
thorntail.datasources.data-sources.KEY.use-try-lock
Any configured timeout for internal locks on the resource adapter objects in seconds
thorntail.datasources.data-sources.KEY.user-name
Specify the user name used when creating a new connection
thorntail.datasources.data-sources.KEY.valid-connection-checker-class-name
An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides an isValidConnection(Connection) method to validate a connection. If an exception is returned that means the connection is invalid. This overrides the check-valid-connection-sql element
thorntail.datasources.data-sources.KEY.valid-connection-checker-properties
The valid connection checker properties
thorntail.datasources.data-sources.KEY.validate-on-match
The validate-on-match element specifies if connection validation should be done when a connection factory attempts to match a managed connection. This is typically exclusive to the use of background validation
thorntail.datasources.installed-drivers
List of JDBC drivers that have been installed in the runtime
thorntail.datasources.jdbc-drivers.KEY.datasource-class-info
The available properties for the datasource-class, and xa-datasource-class for the jdbc-driver
thorntail.datasources.jdbc-drivers.KEY.deployment-name
The name of the deployment unit from which the driver was loaded
thorntail.datasources.jdbc-drivers.KEY.driver-class-name
The fully qualified class name of the java.sql.Driver implementation
thorntail.datasources.jdbc-drivers.KEY.driver-datasource-class-name
The fully qualified class name of the javax.sql.DataSource implementation
thorntail.datasources.jdbc-drivers.KEY.driver-major-version
The driver’s major version number
thorntail.datasources.jdbc-drivers.KEY.driver-minor-version
The driver’s minor version number
thorntail.datasources.jdbc-drivers.KEY.driver-module-name
The name of the module from which the driver was loaded, if it was loaded from the module path
thorntail.datasources.jdbc-drivers.KEY.driver-name
Defines the JDBC driver the datasource should use. It is a symbolic name matching the the name of installed driver. In case the driver is deployed as jar, the name is the name of deployment unit
thorntail.datasources.jdbc-drivers.KEY.driver-xa-datasource-class-name
The fully qualified class name of the javax.sql.XADataSource implementation
thorntail.datasources.jdbc-drivers.KEY.jdbc-compliant
Whether or not the driver is JDBC compliant
thorntail.datasources.jdbc-drivers.KEY.module-slot
The slot of the module from which the driver was loaded, if it was loaded from the module path
thorntail.datasources.jdbc-drivers.KEY.profile
Domain Profile in which driver is defined. Null in case of standalone server
thorntail.datasources.jdbc-drivers.KEY.xa-datasource-class
XA datasource class
thorntail.datasources.xa-data-sources.KEY.allocation-retry
The allocation retry element indicates the number of times that allocating a connection should be tried before throwing an exception
thorntail.datasources.xa-data-sources.KEY.allocation-retry-wait-millis
The allocation retry wait millis element specifies the amount of time, in milliseconds, to wait between retrying to allocate a connection
thorntail.datasources.xa-data-sources.KEY.allow-multiple-users
Specifies if multiple users will access the datasource through the getConnection(user, password) method and hence if the internal pool type should account for that
thorntail.datasources.xa-data-sources.KEY.authentication-context
The Elytron authentication context which defines the javax.security.auth.Subject that is used to distinguish connections in the pool.
thorntail.datasources.xa-data-sources.KEY.background-validation
An element to specify that connections should be validated on a background thread versus being validated prior to use.
thorntail.datasources.xa-data-sources.KEY.background-validation-millis
The background-validation-millis element specifies the amount of time, in milliseconds, that background validation will run.
thorntail.datasources.xa-data-sources.KEY.blocking-timeout-wait-millis
The blocking-timeout-millis element specifies the maximum time, in milliseconds, to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for locking a connection, and will never throw an exception if creating a new connection takes an inordinately long time
thorntail.datasources.xa-data-sources.KEY.capacity-decrementer-class
Class defining the policy for decrementing connections in the pool
thorntail.datasources.xa-data-sources.KEY.capacity-decrementer-properties
Properties to inject in class defining the policy for decrementing connections in the pool
thorntail.datasources.xa-data-sources.KEY.capacity-incrementer-class
Class defining the policy for incrementing connections in the pool
thorntail.datasources.xa-data-sources.KEY.capacity-incrementer-properties
Properties to inject in class defining the policy for incrementing connections in the pool
thorntail.datasources.xa-data-sources.KEY.check-valid-connection-sql
Specify an SQL statement to check validity of a pool connection. This may be called when managed connection is obtained from the pool
thorntail.datasources.xa-data-sources.KEY.connectable
Enable the use of CMR for this datasource. This feature means that a local resource can reliably participate in an XA transaction.
thorntail.datasources.xa-data-sources.KEY.connection-listener-class
Speciefies class name extending org.jboss.jca.adapters.jdbc.spi.listener.ConnectionListener that provides a possible to listen for connection activation and passivation in order to perform actions before the connection is returned to the application or returned to the pool.
thorntail.datasources.xa-data-sources.KEY.connection-listener-property
Properties to be injected in class specified in connection-listener-class
thorntail.datasources.xa-data-sources.KEY.credential-reference
Credential (from Credential Store) to authenticate on data source
thorntail.datasources.xa-data-sources.KEY.driver-name
Defines the JDBC driver the datasource should use. It is a symbolic name matching the the name of installed driver. In case the driver is deployed as jar, the name is the name of deployment unit
thorntail.datasources.xa-data-sources.KEY.elytron-enabled
Enables Elytron security for handling authentication of connections for recovery. The Elytron authentication-context to be used will be current context if no context is specified (see authentication-context).
thorntail.datasources.xa-data-sources.KEY.enlistment-trace
Defines if WildFly/IronJacamar should record enlistment traces
thorntail.datasources.xa-data-sources.KEY.exception-sorter-class-name
An org.jboss.jca.adapters.jdbc.ExceptionSorter that provides an isExceptionFatal(SQLException) method to validate if an exception should broadcast an error
thorntail.datasources.xa-data-sources.KEY.exception-sorter-properties
The exception sorter properties
thorntail.datasources.xa-data-sources.KEY.flush-strategy
Specifies how the pool should be flush in case of an error.
thorntail.datasources.xa-data-sources.KEY.idle-timeout-minutes
The idle-timeout-minutes elements specifies the maximum time, in minutes, a connection may be idle before being closed. The actual maximum time depends also on the IdleRemover scan time, which is half of the smallest idle-timeout-minutes value of any pool. Changing this value can be done only on disabled datasource, requires a server restart otherwise.
thorntail.datasources.xa-data-sources.KEY.initial-pool-size
The initial-pool-size element indicates the initial number of connections a pool should hold.
thorntail.datasources.xa-data-sources.KEY.interleaving
An element to enable interleaving for XA connections
thorntail.datasources.xa-data-sources.KEY.jndi-name
Specifies the JNDI name for the datasource
thorntail.datasources.xa-data-sources.KEY.max-pool-size
The max-pool-size element specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool
thorntail.datasources.xa-data-sources.KEY.mcp
Defines the ManagedConnectionPool implementation, f.ex. org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool
thorntail.datasources.xa-data-sources.KEY.min-pool-size
The min-pool-size element specifies the minimum number of connections for a pool
thorntail.datasources.xa-data-sources.KEY.new-connection-sql
Specifies an SQL statement to execute whenever a connection is added to the connection pool
thorntail.datasources.xa-data-sources.KEY.no-recovery
Specifies if the connection pool should be excluded from recovery
thorntail.datasources.xa-data-sources.KEY.no-tx-separate-pool
Oracle does not like XA connections getting used both inside and outside a JTA transaction. To workaround the problem you can create separate sub-pools for the different contexts
thorntail.datasources.xa-data-sources.KEY.pad-xid
Should the Xid be padded
thorntail.datasources.xa-data-sources.KEY.password
Specifies the password used when creating a new connection
thorntail.datasources.xa-data-sources.KEY.pool-fair
Defines if pool use should be fair
thorntail.datasources.xa-data-sources.KEY.pool-prefill
Should the pool be prefilled. Changing this value can be done only on disabled datasource, requires a server restart otherwise.
thorntail.datasources.xa-data-sources.KEY.pool-use-strict-min
Specifies if the min-pool-size should be considered strictly
thorntail.datasources.xa-data-sources.KEY.prepared-statements-cache-size
The number of prepared statements per connection in an LRU cache
thorntail.datasources.xa-data-sources.KEY.query-timeout
Any configured query timeout in seconds. If not provided no timeout will be set
thorntail.datasources.xa-data-sources.KEY.reauth-plugin-class-name
The fully qualified class name of the reauthentication plugin implementation
thorntail.datasources.xa-data-sources.KEY.reauth-plugin-properties
The properties for the reauthentication plugin
thorntail.datasources.xa-data-sources.KEY.recovery-authentication-context
The Elytron authentication context which defines the javax.security.auth.Subject that is used to distinguish connections in the pool.
thorntail.datasources.xa-data-sources.KEY.recovery-credential-reference
Credential (from Credential Store) to authenticate on data source
thorntail.datasources.xa-data-sources.KEY.recovery-elytron-enabled
Enables Elytron security for handling authentication of connections for recovery. The Elytron authentication-context to be used will be current context if no context is specified (see authentication-context).
thorntail.datasources.xa-data-sources.KEY.recovery-password
The password used for recovery
thorntail.datasources.xa-data-sources.KEY.recovery-plugin-class-name
The fully qualified class name of the recovery plugin implementation
thorntail.datasources.xa-data-sources.KEY.recovery-plugin-properties
The properties for the recovery plugin
thorntail.datasources.xa-data-sources.KEY.recovery-security-domain
The security domain used for recovery
thorntail.datasources.xa-data-sources.KEY.recovery-username
The user name used for recovery
thorntail.datasources.xa-data-sources.KEY.same-rm-override
The is-same-rm-override element allows one to unconditionally set whether the javax.transaction.xa.XAResource.isSameRM(XAResource) returns true or false
thorntail.datasources.xa-data-sources.KEY.security-domain
Specifies the PicketBox security domain which defines the javax.security.auth.Subject that are used to distinguish connections in the pool
thorntail.datasources.xa-data-sources.KEY.set-tx-query-timeout
Whether to set the query timeout based on the time remaining until transaction timeout. Any configured query timeout will be used if there is no transaction
thorntail.datasources.xa-data-sources.KEY.share-prepared-statements
Whether to share prepared statements, i.e. whether asking for same statement twice without closing uses the same underlying prepared statement
thorntail.datasources.xa-data-sources.KEY.spy
Enable spying of SQL statements
thorntail.datasources.xa-data-sources.KEY.stale-connection-checker-class-name
An org.jboss.jca.adapters.jdbc.StaleConnectionChecker that provides an isStaleConnection(SQLException) method which if it returns true will wrap the exception in an org.jboss.jca.adapters.jdbc.StaleConnectionException
thorntail.datasources.xa-data-sources.KEY.stale-connection-checker-properties
The stale connection checker properties
thorntail.datasources.xa-data-sources.KEY.statistics-enabled
Define whether runtime statistics are enabled or not.
thorntail.datasources.xa-data-sources.KEY.track-statements
Whether to check for unclosed statements when a connection is returned to the pool, result sets are closed, a statement is closed or return to the prepared statement cache. Valid values are: "false" - do not track statements, "true" - track statements and result sets and warn when they are not closed, "nowarn" - track statements but do not warn about them being unclosed
thorntail.datasources.xa-data-sources.KEY.tracking
Defines if IronJacamar should track connection handles across transaction boundaries
thorntail.datasources.xa-data-sources.KEY.transaction-isolation
Set the java.sql.Connection transaction isolation level. Valid values are: TRANSACTION_READ_UNCOMMITTED, TRANSACTION_READ_COMMITTED, TRANSACTION_REPEATABLE_READ, TRANSACTION_SERIALIZABLE and TRANSACTION_NONE. Different values are used to set customLevel using TransactionIsolation#customLevel.
thorntail.datasources.xa-data-sources.KEY.url-delimiter
Specifies the delimiter for URLs in connection-url for HA datasources
thorntail.datasources.xa-data-sources.KEY.url-property
Specifies the property for the URL property in the xa-datasource-property values
thorntail.datasources.xa-data-sources.KEY.url-selector-strategy-class-name
A class that implements org.jboss.jca.adapters.jdbc.URLSelectorStrategy
thorntail.datasources.xa-data-sources.KEY.use-ccm
Enable the use of a cached connection manager
thorntail.datasources.xa-data-sources.KEY.use-fast-fail
Whether to fail a connection allocation on the first try if it is invalid (true) or keep trying until the pool is exhausted of all potential connections (false)
thorntail.datasources.xa-data-sources.KEY.use-java-context
Setting this to false will bind the datasource into global JNDI
thorntail.datasources.xa-data-sources.KEY.use-try-lock
Any configured timeout for internal locks on the resource adapter objects in seconds
thorntail.datasources.xa-data-sources.KEY.user-name
Specify the user name used when creating a new connection
thorntail.datasources.xa-data-sources.KEY.valid-connection-checker-class-name
An org.jboss.jca.adapters.jdbc.ValidConnectionChecker that provides an isValidConnection(Connection) method to validate a connection. If an exception is returned that means the connection is invalid. This overrides the check-valid-connection-sql element
thorntail.datasources.xa-data-sources.KEY.valid-connection-checker-properties
The valid connection checker properties
thorntail.datasources.xa-data-sources.KEY.validate-on-match
The validate-on-match element specifies if connection validation should be done when a connection factory attempts to match a managed connection. This is typically exclusive to the use of background validation
thorntail.datasources.xa-data-sources.KEY.wrap-xa-resource
Should the XAResource instances be wrapped in an org.jboss.tm.XAResourceWrapper instance
thorntail.datasources.xa-data-sources.KEY.xa-datasource-class
The fully qualified name of the javax.sql.XADataSource implementation
thorntail.datasources.xa-data-sources.KEY.xa-datasource-properties.KEY.value
Specifies a property value to assign to the XADataSource implementation class. Each property is identified by the name attribute and the property value is given by the xa-datasource-property element content. The property is mapped onto the XADataSource implementation by looking for a JavaBeans style getter method for the property name. If found, the value of the property is set using the JavaBeans setter with the element text translated to the true property type using the java.beans.PropertyEditor
thorntail.datasources.xa-data-sources.KEY.xa-resource-timeout
The value is passed to XAResource.setTransactionTimeout(), in seconds. Default is zero
thorntail.ds.connection.url
Default datasource connection URL
thorntail.ds.name
Name of the default datasource
thorntail.ds.password
Default datasource connection password
thorntail.ds.username
Default datasource connection user name
thorntail.jdbc.driver
Default datasource JDBC driver name

D.7. EE

An internal fraction used to support other higher-level fractions.

The EE fraction does not imply the totality of Java EE support.

If you require specific Java EE technologies, address them individually, for example jaxrs, cdi, datasources, or ejb.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>ee</artifactId>
</dependency>

Configuration

thorntail.ee.annotation-property-replacement
Flag indicating whether Java EE annotations will have property replacements applied
thorntail.ee.context-services.KEY.jndi-name
The JNDI Name to lookup the context service.
thorntail.ee.context-services.KEY.use-transaction-setup-provider
Flag which indicates if the transaction setup provider should be used
thorntail.ee.default-bindings-service.context-service
The JNDI name where the default EE Context Service can be found
thorntail.ee.default-bindings-service.datasource
The JNDI name where the default EE Datasource can be found
thorntail.ee.default-bindings-service.jms-connection-factory
The JNDI name where the default EE JMS Connection Factory can be found
thorntail.ee.default-bindings-service.managed-executor-service
The JNDI name where the default EE Managed Executor Service can be found
thorntail.ee.default-bindings-service.managed-scheduled-executor-service
The JNDI name where the default EE Managed Scheduled Executor Service can be found
thorntail.ee.default-bindings-service.managed-thread-factory
The JNDI name where the default EE Managed Thread Factory can be found
thorntail.ee.ear-subdeployments-isolated
Flag indicating whether each of the subdeployments within a .ear can access classes belonging to another subdeployment within the same .ear. A value of false means the subdeployments can see classes belonging to other subdeployments within the .ear.
thorntail.ee.global-modules
A list of modules that should be made available to all deployments.
thorntail.ee.jboss-descriptor-property-replacement
Flag indicating whether JBoss specific deployment descriptors will have property replacements applied
thorntail.ee.managed-executor-services.KEY.context-service
The name of the context service to be used by the executor.
thorntail.ee.managed-executor-services.KEY.core-threads
The minimum number of threads to be used by the executor. If left undefined the default core-size is calculated based on the number of processors. A value of zero is not advised and in some cases invalid. See the queue-length attribute for details on how this value is used to determine the queuing strategy.
thorntail.ee.managed-executor-services.KEY.hung-task-threshold
The runtime, in milliseconds, for tasks to be considered hung by the managed executor service. If value is 0 tasks are never considered hung.
thorntail.ee.managed-executor-services.KEY.jndi-name
The JNDI Name to lookup the managed executor service.
thorntail.ee.managed-executor-services.KEY.keepalive-time
When the number of threads is greater than the core, this is the maximum time, in milliseconds, that excess idle threads will wait for new tasks before terminating.
thorntail.ee.managed-executor-services.KEY.long-running-tasks
Flag which hints the duration of tasks executed by the executor.
thorntail.ee.managed-executor-services.KEY.max-threads
The maximum number of threads to be used by the executor. If left undefined the value from core-size will be used. This value is ignored if an unbounded queue is used (only core-threads will be used in that case).
thorntail.ee.managed-executor-services.KEY.queue-length
The executors task queue capacity. A length of 0 means direct hand-off and possible rejection will occur. An undefined length (the default), or Integer.MAX_VALUE, indicates that an unbounded queue should be used. All other values specify an exact queue size. If an unbounded queue or direct hand-off is used, a core-threads value greater than zero is required.
thorntail.ee.managed-executor-services.KEY.reject-policy
The policy to be applied to aborted tasks.
thorntail.ee.managed-executor-services.KEY.thread-factory
The name of the thread factory to be used by the executor.
thorntail.ee.managed-scheduled-executor-services.KEY.context-service
The name of the context service to be used by the scheduled executor.
thorntail.ee.managed-scheduled-executor-services.KEY.core-threads
The number of threads to be used by the scheduled executor, even if they are idle. If this is not defined or is set to 0, the core pool size will be calculated based on the number of available processors.
thorntail.ee.managed-scheduled-executor-services.KEY.hung-task-threshold
The runtime, in milliseconds, for tasks to be considered hung by the scheduled executor. If 0 tasks are never considered hung.
thorntail.ee.managed-scheduled-executor-services.KEY.jndi-name
The JNDI Name to lookup the managed scheduled executor service.
thorntail.ee.managed-scheduled-executor-services.KEY.keepalive-time
When the number of threads is greater than the core, this is the maximum time, in milliseconds, that excess idle threads will wait for new tasks before terminating.
thorntail.ee.managed-scheduled-executor-services.KEY.long-running-tasks
Flag which hints the duration of tasks executed by the scheduled executor.
thorntail.ee.managed-scheduled-executor-services.KEY.reject-policy
The policy to be applied to aborted tasks.
thorntail.ee.managed-scheduled-executor-services.KEY.thread-factory
The name of the thread factory to be used by the scheduled executor.
thorntail.ee.managed-thread-factories.KEY.context-service
The name of the context service to be used by the managed thread factory
thorntail.ee.managed-thread-factories.KEY.jndi-name
The JNDI Name to lookup the managed thread factory.
thorntail.ee.managed-thread-factories.KEY.priority
The priority applied to threads created by the factory
thorntail.ee.spec-descriptor-property-replacement
Flag indicating whether descriptors defined by the Java EE specification will have property replacements applied

D.7.1. EE Security

Provides Java EE Security API support according to JSR 375.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>ee-security</artifactId>
</dependency>

D.8. EJB

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>ejb</artifactId>
</dependency>

Configuration

thorntail.ejb3.allow-ejb-name-regex
If this is true then regular expressions can be used in interceptor bindings to allow interceptors to be mapped to all beans that match the regular expression
thorntail.ejb3.application-security-domains.KEY.enable-jacc
Enable authorization using JACC
thorntail.ejb3.application-security-domains.KEY.referencing-deployments
The deployments currently referencing this mapping
thorntail.ejb3.application-security-domains.KEY.security-domain
The Elytron security domain to be used by deployments that reference the mapped security domain
thorntail.ejb3.async-service.thread-pool-name
The name of the thread pool which handles asynchronous invocations
thorntail.ejb3.caches.KEY.aliases
The aliases by which this cache may also be referenced
thorntail.ejb3.caches.KEY.passivation-store
The passivation store used by this cache
thorntail.ejb3.cluster-passivation-stores.KEY.bean-cache
The name of the cache used to store bean instances.
thorntail.ejb3.cluster-passivation-stores.KEY.cache-container
The name of the cache container used for the bean and client-mappings caches
thorntail.ejb3.cluster-passivation-stores.KEY.idle-timeout
The timeout in units specified by idle-timeout-unit, after which a bean will passivate
thorntail.ejb3.cluster-passivation-stores.KEY.max-size
The maximum number of beans this cache should store before forcing old beans to passivate
thorntail.ejb3.default-clustered-sfsb-cache
Name of the default stateful bean cache, which will be applicable to all clustered stateful EJBs, unless overridden at the deployment or bean level
thorntail.ejb3.default-distinct-name
The default distinct name that is applied to every EJB deployed on this server
thorntail.ejb3.default-entity-bean-instance-pool
Name of the default entity bean instance pool, which will be applicable to all entity beans, unless overridden at the deployment or bean level
thorntail.ejb3.default-entity-bean-optimistic-locking
If set to true entity beans will use optimistic locking by default
thorntail.ejb3.default-mdb-instance-pool
Name of the default MDB instance pool, which will be applicable to all MDBs, unless overridden at the deployment or bean level
thorntail.ejb3.default-missing-method-permissions-deny-access
If this is set to true then methods on an EJB with a security domain specified or with other methods with security metadata will have an implicit @DenyAll unless other security metadata is present
thorntail.ejb3.default-resource-adapter-name
Name of the default resource adapter name that will be used by MDBs, unless overridden at the deployment or bean level
thorntail.ejb3.default-security-domain
The default security domain that will be used for EJBs if the bean doesn’t explicitly specify one
thorntail.ejb3.default-sfsb-cache
Name of the default stateful bean cache, which will be applicable to all stateful EJBs, unless overridden at the deployment or bean level
thorntail.ejb3.default-sfsb-passivation-disabled-cache
Name of the default stateful bean cache, which will be applicable to all stateful EJBs which have passivation disabled. Each deployment or EJB can optionally override this cache name.
thorntail.ejb3.default-singleton-bean-access-timeout
The default access timeout for singleton beans
thorntail.ejb3.default-slsb-instance-pool
Name of the default stateless bean instance pool, which will be applicable to all stateless EJBs, unless overridden at the deployment or bean level
thorntail.ejb3.default-stateful-bean-access-timeout
The default access timeout for stateful beans
thorntail.ejb3.disable-default-ejb-permissions
This deprecated attribute has no effect and will be removed in a future release; it may never be set to a "false" value
thorntail.ejb3.enable-graceful-txn-shutdown
Enabling txn graceful shutdown will make the server wait for active EJB-related transactions to complete before suspending. For that reason, if the server is running on a cluster, the suspending cluster node may receive ejb requests until all active transactions are complete. To avoid this behavior, omit this tag.
thorntail.ejb3.enable-statistics
If set to true, enable the collection of invocation statistics. Deprecated in favour of "statistics-enabled"
thorntail.ejb3.file-passivation-stores.KEY.idle-timeout
The timeout in units specified by idle-timeout-unit, after which a bean will passivate
thorntail.ejb3.file-passivation-stores.KEY.max-size
The maximum number of beans this cache should store before forcing old beans to passivate
thorntail.ejb3.identity-service.outflow-security-domains
References to security domains to attempt to outflow any established identity to
thorntail.ejb3.iiop-service.enable-by-default
If this is true EJB’s will be exposed over IIOP by default, otherwise it needs to be explicitly enabled in the deployment descriptor
thorntail.ejb3.iiop-service.use-qualified-name
If true EJB names will be bound into the naming service with the application and module name prepended to the name (e.g. myapp/mymodule/MyEjb)
thorntail.ejb3.in-vm-remote-interface-invocation-pass-by-value
If set to false, the parameters to invocations on remote interface of an EJB, will be passed by reference. Else, the parameters will be passed by value.
thorntail.ejb3.log-system-exceptions
If this is true then all EJB system (not application) exceptions will be logged. The EJB spec mandates this behaviour, however it is not recommended as it will often result in exceptions being logged twice (once by the EJB and once by the calling code)
thorntail.ejb3.mdb-delivery-groups.KEY.active
Indicates if delivery for all MDBs belonging to this group is active
thorntail.ejb3.passivation-stores.KEY.bean-cache
The name of the cache used to store bean instances.
thorntail.ejb3.passivation-stores.KEY.cache-container
The name of the cache container used for the bean and client-mappings caches
thorntail.ejb3.passivation-stores.KEY.max-size
The maximum number of beans this cache should store before forcing old beans to passivate
thorntail.ejb3.remote-service.channel-creation-options.KEY.type
The type of the channel creation option
thorntail.ejb3.remote-service.channel-creation-options.KEY.value
The value for the EJB remote channel creation option
thorntail.ejb3.remote-service.cluster
The name of the clustered cache container which will be used to store/access the client-mappings of the EJB remoting connector’s socket-binding on each node, in the cluster
thorntail.ejb3.remote-service.connector-ref
The name of the connector on which the EJB3 remoting channel is registered
thorntail.ejb3.remote-service.execute-in-worker
If this is true the EJB request will be executed in the IO subsystems worker, otherwise it will dispatch to the EJB thread pool
thorntail.ejb3.remote-service.thread-pool-name
The name of the thread pool that handles remote invocations
thorntail.ejb3.remoting-profiles.KEY.exclude-local-receiver
If set no local receiver is used in this profile
thorntail.ejb3.remoting-profiles.KEY.local-receiver-pass-by-value
If set local receiver will pass ejb beans by value
thorntail.ejb3.remoting-profiles.KEY.remoting-ejb-receivers.KEY.channel-creation-options.KEY.type
The type of the channel creation option
thorntail.ejb3.remoting-profiles.KEY.remoting-ejb-receivers.KEY.channel-creation-options.KEY.value
The value for the EJB remote channel creation option
thorntail.ejb3.remoting-profiles.KEY.remoting-ejb-receivers.KEY.connect-timeout
Remoting ejb receiver connect timeout
thorntail.ejb3.remoting-profiles.KEY.remoting-ejb-receivers.KEY.outbound-connection-ref
Name of outbound connection that will be used by the ejb receiver
thorntail.ejb3.remoting-profiles.KEY.static-ejb-discovery
Describes static discovery config for EJB’s
thorntail.ejb3.statistics-enabled
If set to true, enable the collection of invocation statistics.
thorntail.ejb3.strict-max-bean-instance-pools.KEY.derive-size
Specifies if and what the max pool size should be derived from. An undefined value (or the deprecated value 'none' which is converted to undefined) indicates that the explicit value of max-pool-size should be used. A value of 'from-worker-pools' indicates that the max pool size should be derived from the size of the total threads for all worker pools configured on the system. A value of 'from-cpu-count' indicates that the max pool size should be derived from the total number of processors available on the system. Note that the computation isn’t a 1:1 mapping, the values may or may not be augmented by other factors.
thorntail.ejb3.strict-max-bean-instance-pools.KEY.derived-size
Derived maximum number of bean instances that the pool can hold at a given point in time
thorntail.ejb3.strict-max-bean-instance-pools.KEY.max-pool-size
Configured maximum number of bean instances that the pool can hold at a given point in time
thorntail.ejb3.strict-max-bean-instance-pools.KEY.timeout
The maximum amount of time to wait for a bean instance to be available from the pool
thorntail.ejb3.strict-max-bean-instance-pools.KEY.timeout-unit
The instance acquisition timeout unit
thorntail.ejb3.thread-pools.KEY.active-count
The approximate number of threads that are actively executing tasks.
thorntail.ejb3.thread-pools.KEY.completed-task-count
The approximate total number of tasks that have completed execution.
thorntail.ejb3.thread-pools.KEY.current-thread-count
The current number of threads in the pool.
thorntail.ejb3.thread-pools.KEY.keepalive-time
Used to specify the amount of time that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.ejb3.thread-pools.KEY.largest-thread-count
The largest number of threads that have ever simultaneously been in the pool.
thorntail.ejb3.thread-pools.KEY.max-threads
The maximum thread pool size.
thorntail.ejb3.thread-pools.KEY.name
The name of the thread pool.
thorntail.ejb3.thread-pools.KEY.queue-size
The queue size.
thorntail.ejb3.thread-pools.KEY.rejected-count
The number of tasks that have been rejected.
thorntail.ejb3.thread-pools.KEY.task-count
The approximate total number of tasks that have ever been scheduled for execution.
thorntail.ejb3.thread-pools.KEY.thread-factory
Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.
thorntail.ejb3.timer-service.database-data-stores.KEY.allow-execution
If this node is allowed to execute timers. If this is false then the timers will be added to the database, and another node may execute them. Note that depending on your refresh interval if you add timers with a very short delay they will not be executed until another node refreshes.
thorntail.ejb3.timer-service.database-data-stores.KEY.database
The type of database that is in use. SQL can be customised per database type.
thorntail.ejb3.timer-service.database-data-stores.KEY.datasource-jndi-name
The datasource that is used to persist the timers
thorntail.ejb3.timer-service.database-data-stores.KEY.partition
The partition name. This should be set to a different value for every node that is sharing a database to prevent the same timer being loaded by multiple noded.
thorntail.ejb3.timer-service.database-data-stores.KEY.refresh-interval
Interval between refreshing the current timer set against the underlying database. A low value means timers get picked up more quickly, but increase load on the database.
thorntail.ejb3.timer-service.default-data-store
The default data store used for persistent timers
thorntail.ejb3.timer-service.file-data-stores.KEY.path
The directory to store persistent timer information in
thorntail.ejb3.timer-service.file-data-stores.KEY.relative-to
The relative path that is used to resolve the timer data store location
thorntail.ejb3.timer-service.thread-pool-name
The name of the thread pool used to run timer service invocations

D.9. Elytron

Elytron can generate the audit log to the same directory where the Thorntail application is executed. Include the following section in the project-defaults.yml file in your application:

thorntail:
  elytron:
    file-audit-logs:
      local-audit:
        path: audit.log

In some environments, for example cloud, you might have to relocate the audit file to a globally writable directory, for example:

thorntail:
  elytron:
    file-audit-logs:
      local-audit:
        path: /tmp/audit.log

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>elytron</artifactId>
</dependency>

Configuration

thorntail.elytron.add-prefix-role-mappers.KEY.prefix
The prefix to add to each role.
thorntail.elytron.add-suffix-role-mappers.KEY.suffix
The suffix to add to each role.
thorntail.elytron.aggregate-http-server-mechanism-factories.KEY.available-mechanisms
The HTTP mechanisms available from this factory instance.
thorntail.elytron.aggregate-http-server-mechanism-factories.KEY.http-server-mechanism-factories
The referenced http server factories to aggregate.
thorntail.elytron.aggregate-principal-decoders.KEY.principal-decoders
The referenced principal decoders to aggregate.
thorntail.elytron.aggregate-principal-transformers.KEY.principal-transformers
The referenced principal transformers to aggregate.
thorntail.elytron.aggregate-providers.KEY.providers
The referenced Provider[] resources to aggregate.
thorntail.elytron.aggregate-realms.KEY.authentication-realm
Reference to the security realm to use for authentication steps (obtaining or validating credentials).
thorntail.elytron.aggregate-realms.KEY.authorization-realm
Reference to the security realm to use for loading the identity for authorization steps (loading of the identity).
thorntail.elytron.aggregate-role-mappers.KEY.role-mappers
The referenced role mappers to aggregate.
thorntail.elytron.aggregate-sasl-server-factories.KEY.available-mechanisms
The SASL mechanisms available from this factory after all filtering has been applied.
thorntail.elytron.aggregate-sasl-server-factories.KEY.sasl-server-factories
The referenced sasl server factories to aggregate.
thorntail.elytron.aggregate-security-event-listeners.KEY.security-event-listeners
The referenced security event listener resources to aggregate.
thorntail.elytron.authentication-configurations.KEY.anonymous
Enables anonymous authentication.
thorntail.elytron.authentication-configurations.KEY.attribute-extends
A previously defined authentication configuration to extend.
thorntail.elytron.authentication-configurations.KEY.authentication-name
The authentication name to use.
thorntail.elytron.authentication-configurations.KEY.authorization-name
The authorization name to use.
thorntail.elytron.authentication-configurations.KEY.credential-reference
The reference to credential stored in CredentialStore under defined alias or clear text password.
thorntail.elytron.authentication-configurations.KEY.forwarding-mode
The type of security identity forwarding to use. A mode of 'authentication' forwarding forwards the principal and credential. A mode of 'authorization' forwards the authorization id, allowing for a different authentication identity.
thorntail.elytron.authentication-configurations.KEY.host
The host to use.
thorntail.elytron.authentication-configurations.KEY.kerberos-security-factory
Reference to a kerberos security factory used to obtain a GSS kerberos credential
thorntail.elytron.authentication-configurations.KEY.mechanism-properties
Configuration properties for the SASL authentication mechanism.
thorntail.elytron.authentication-configurations.KEY.port
The port to use.
thorntail.elytron.authentication-configurations.KEY.protocol
The protocol to use.
thorntail.elytron.authentication-configurations.KEY.realm
The realm to use.
thorntail.elytron.authentication-configurations.KEY.sasl-mechanism-selector
The SASL mechanism selector string.
thorntail.elytron.authentication-configurations.KEY.security-domain
Reference to a security domain to obtain a forwarded identity.
thorntail.elytron.authentication-contexts.KEY.attribute-extends
A previously defined authentication context to extend.
thorntail.elytron.authentication-contexts.KEY.match-rules
The match-rules for this authentication context.
thorntail.elytron.caching-realms.KEY.maximum-age
The time in milliseconds that an item can stay in the cache.
thorntail.elytron.caching-realms.KEY.maximum-entries
The maximum number of entries to keep in the cache.
thorntail.elytron.caching-realms.KEY.realm
A reference to a cacheable security realm.
thorntail.elytron.certificate-authority-accounts.KEY.alias
The alias of certificate authority account key in the keystore. If the alias does not already exist in the keystore, a certificate authority account key will be automatically generated and stored as a PrivateKeyEntry under the alias.
thorntail.elytron.certificate-authority-accounts.KEY.certificate-authority
The name of the certificate authority to use. Allowed values: 'LetsEncrypt'
thorntail.elytron.certificate-authority-accounts.KEY.contact-urls
A list of URLs that the certificate authority can contact about any issues related to this account.
thorntail.elytron.certificate-authority-accounts.KEY.credential-reference
Credential to be used when accessing the certificate authority account key.
thorntail.elytron.certificate-authority-accounts.KEY.key-store
The keystore that contains the certificate authority account key.
thorntail.elytron.chained-principal-transformers.KEY.principal-transformers
The referenced principal transformers to chain.
thorntail.elytron.client-ssl-contexts.KEY.active-session-count
The count of current active sessions.
thorntail.elytron.client-ssl-contexts.KEY.cipher-suite-filter
The filter to apply to specify the enabled cipher suites.
thorntail.elytron.client-ssl-contexts.KEY.key-manager
Reference to the key manager to use within the SSLContext.
thorntail.elytron.client-ssl-contexts.KEY.protocols
The enabled protocols.
thorntail.elytron.client-ssl-contexts.KEY.provider-name
The name of the provider to use. If not specified, all providers from providers will be passed to the SSLContext.
thorntail.elytron.client-ssl-contexts.KEY.providers
The name of the providers to obtain the Provider[] to use to load the SSLContext.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.application-buffer-size
The application buffer size as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.cipher-suite
The selected cipher suite as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.creation-time
The creation time as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.last-accessed-time
The last accessed time as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.local-certificates
The local certificates from the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.local-principal
The local principal as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.packet-buffer-size
The packet buffer size as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.peer-certificates
The peer certificates from the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.peer-host
The peer host as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.peer-port
The peer port as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.peer-principal
The peer principal as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.protocol
The protocol as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.ssl-sessions.KEY.valid
The validity of the session as reported by the SSLSession.
thorntail.elytron.client-ssl-contexts.KEY.trust-manager
Reference to the trust manager to use within the SSLContext.
thorntail.elytron.concatenating-principal-decoders.KEY.joiner
The string to use to join the results of the referenced principal decoders.
thorntail.elytron.concatenating-principal-decoders.KEY.principal-decoders
The referenced principal decoders to concatenate.
thorntail.elytron.configurable-http-server-mechanism-factories.KEY.available-mechanisms
The HTTP mechanisms available from this factory instance.
thorntail.elytron.configurable-http-server-mechanism-factories.KEY.filters
Filtering to be applied to enable / disable mechanisms based on the name.
thorntail.elytron.configurable-http-server-mechanism-factories.KEY.http-server-mechanism-factory
The http server factory to be wrapped.
thorntail.elytron.configurable-http-server-mechanism-factories.KEY.properties
Custom properties to be passed in to the http server factory calls.
thorntail.elytron.configurable-sasl-server-factories.KEY.available-mechanisms
The SASL mechanisms available from this factory after all filtering has been applied.
thorntail.elytron.configurable-sasl-server-factories.KEY.filters
List of filters to be evaluated sequentially combining the results using 'or'.
thorntail.elytron.configurable-sasl-server-factories.KEY.properties
Custom properties to be passed in to the sasl server factory calls.
thorntail.elytron.configurable-sasl-server-factories.KEY.protocol
The protocol that should be passed into factory when creating the mechanism.
thorntail.elytron.configurable-sasl-server-factories.KEY.sasl-server-factory
The sasl server factory to be wrapped.
thorntail.elytron.configurable-sasl-server-factories.KEY.server-name
The server name that should be passed into factory when creating the mechanism.
thorntail.elytron.constant-permission-mappers.KEY.permission-sets
The permission sets to assign.
thorntail.elytron.constant-principal-decoders.KEY.constant
The constant value the principal decoder will always return.
thorntail.elytron.constant-principal-transformers.KEY.constant
The constant value this PrincipalTransformer will always return.
thorntail.elytron.constant-realm-mappers.KEY.realm-name
The name of the constant realm to return.
thorntail.elytron.constant-role-mappers.KEY.roles
The constant roles to be returned by this role mapper.
thorntail.elytron.credential-stores.KEY.create
Specifies whether credential store should create storage when it doesn’t exist.
thorntail.elytron.credential-stores.KEY.credential-reference
Credential reference to be used to create protection parameter.
thorntail.elytron.credential-stores.KEY.implementation-properties
Map of credentials store implementation specific properties.
thorntail.elytron.credential-stores.KEY.location
File name of credential store storage.
thorntail.elytron.credential-stores.KEY.modifiable
Specifies whether credential store is modifiable.
thorntail.elytron.credential-stores.KEY.other-providers
The name of the providers defined within the subsystem to obtain the Providers to search for the one that can create the required JCA objects within credential store. This is valid only for key-store based CredentialStore. If this is not specified then the global list of Providers is used instead.
thorntail.elytron.credential-stores.KEY.provider-name
The name of the provider to use to instantiate the CredentialStoreSpi. If the provider is not specified then the first provider found that can create an instance of the specified 'type' will be used.
thorntail.elytron.credential-stores.KEY.providers
The name of the providers defined within the subsystem to obtain the Providers to search for the one that can create the required CredentialStore type. If this is not specified then the global list of Providers is used instead.
thorntail.elytron.credential-stores.KEY.relative-to
A reference to a previously defined path that the file name is relative to.
thorntail.elytron.credential-stores.KEY.state
The state of the underlying service that represents this credential store at runtime.
thorntail.elytron.credential-stores.KEY.type
The credential store type, e.g. KeyStoreCredentialStore.
thorntail.elytron.custom-credential-security-factories.KEY.class-name
The class name of the implementation of the custom security factory.
thorntail.elytron.custom-credential-security-factories.KEY.configuration
The optional key/value configuration for the custom security factory.
thorntail.elytron.custom-credential-security-factories.KEY.module
The module to use to load the custom security factory.
thorntail.elytron.custom-modifiable-realms.KEY.class-name
The class name of the implementation of the custom realm.
thorntail.elytron.custom-modifiable-realms.KEY.configuration
The optional key/value configuration for the custom realm.
thorntail.elytron.custom-modifiable-realms.KEY.module
The module to use to load the custom realm.
thorntail.elytron.custom-permission-mappers.KEY.class-name
Fully qualified class name of the permission mapper
thorntail.elytron.custom-permission-mappers.KEY.configuration
The optional kay/value configuration for the permission mapper
thorntail.elytron.custom-permission-mappers.KEY.module
Name of the module to use to load the permission mapper
thorntail.elytron.custom-principal-decoders.KEY.class-name
Fully qualified class name of the principal decoder
thorntail.elytron.custom-principal-decoders.KEY.configuration
The optional kay/value configuration for the principal decoder
thorntail.elytron.custom-principal-decoders.KEY.module
Name of the module to use to load the principal decoder
thorntail.elytron.custom-principal-transformers.KEY.class-name
The class name of the implementation of the custom principal transformer.
thorntail.elytron.custom-principal-transformers.KEY.configuration
The optional key/value configuration for the custom principal transformer.
thorntail.elytron.custom-principal-transformers.KEY.module
The module to use to load the custom principal transformer.
thorntail.elytron.custom-realm-mappers.KEY.class-name
Fully qualified class name of the RealmMapper
thorntail.elytron.custom-realm-mappers.KEY.configuration
The optional kay/value configuration for the RealmMapper
thorntail.elytron.custom-realm-mappers.KEY.module
Name of the module to use to load the RealmMapper
thorntail.elytron.custom-realms.KEY.class-name
The class name of the implementation of the custom realm.
thorntail.elytron.custom-realms.KEY.configuration
The optional key/value configuration for the custom realm.
thorntail.elytron.custom-realms.KEY.module
The module to use to load the custom realm.
thorntail.elytron.custom-role-decoders.KEY.class-name
Fully qualified class name of the RoleDecoder
thorntail.elytron.custom-role-decoders.KEY.configuration
The optional kay/value configuration for the RoleDecoder
thorntail.elytron.custom-role-decoders.KEY.module
Name of the module to use to load the RoleDecoder
thorntail.elytron.custom-role-mappers.KEY.class-name
Fully qualified class name of the RoleMapper
thorntail.elytron.custom-role-mappers.KEY.configuration
The optional key/value configuration for the RoleMapper
thorntail.elytron.custom-role-mappers.KEY.module
Name of the module to use to load the RoleMapper
thorntail.elytron.custom-security-event-listeners.KEY.class-name
The class name of the implementation of the custom security event listener.
thorntail.elytron.custom-security-event-listeners.KEY.configuration
The optional key/value configuration for the custom security event listener.
thorntail.elytron.custom-security-event-listeners.KEY.module
The module to use to load the custom security event listener.
thorntail.elytron.default-authentication-context
The default authentication context to be associated with all deployments.
thorntail.elytron.default-ssl-context
Reference to the SSLContext which should be globally registered as the default.
thorntail.elytron.dir-contexts.KEY.authentication-context
The authentication context to obtain login credentials to connect to the LDAP server. Can be omitted if authentication-level is 'none' (anonymous).
thorntail.elytron.dir-contexts.KEY.authentication-level
The authentication level (security level/authentication mechanism) to use. Corresponds to SECURITY_AUTHENTICATION ('java.naming.security.authentication') environment property. Allowed values: 'none', 'simple', sasl_mech, where sasl_mech is a space-separated list of SASL mechanism names.
thorntail.elytron.dir-contexts.KEY.connection-timeout
The timeout for connecting to the LDAP server in milliseconds.
thorntail.elytron.dir-contexts.KEY.credential-reference
The credential reference to authenticate and connect to the LDAP server. Can be omitted if authentication-level is 'none' (anonymous).
thorntail.elytron.dir-contexts.KEY.enable-connection-pooling
Indicates if connection pooling is enabled.
thorntail.elytron.dir-contexts.KEY.module
Name of module that will be used as class loading base.
thorntail.elytron.dir-contexts.KEY.principal
The principal to authenticate and connect to the LDAP server. Can be omitted if authentication-level is 'none' (anonymous).
thorntail.elytron.dir-contexts.KEY.properties
The additional connection properties for the DirContext.
thorntail.elytron.dir-contexts.KEY.read-timeout
The read timeout for an LDAP operation in milliseconds.
thorntail.elytron.dir-contexts.KEY.referral-mode
If referrals should be followed.
thorntail.elytron.dir-contexts.KEY.ssl-context
The name of ssl-context used to secure connection to the LDAP server.
thorntail.elytron.dir-contexts.KEY.url
The connection url.
thorntail.elytron.disallowed-providers
A list of providers that are not allowed, and will be removed from the providers list.
thorntail.elytron.file-audit-logs.KEY.attribute-synchronized
Whether every event should be immediately synchronised to disk.
thorntail.elytron.file-audit-logs.KEY.autoflush
Whether every event should be immediately flushed to disk (If undefined will default to the value of synchronized).
thorntail.elytron.file-audit-logs.KEY.format
The format to use to record the audit event.
thorntail.elytron.file-audit-logs.KEY.path
Path of the file to be written.
thorntail.elytron.file-audit-logs.KEY.relative-to
The relative path to the audit log.
thorntail.elytron.filesystem-realms.KEY.encoded
Whether the identity names should be stored encoded (Base32) in file names.
thorntail.elytron.filesystem-realms.KEY.levels
The number of levels of directory hashing to apply.
thorntail.elytron.filesystem-realms.KEY.path
The path to the file containing the realm.
thorntail.elytron.filesystem-realms.KEY.relative-to
The pre-defined path the path is relative to.
thorntail.elytron.filtering-key-stores.KEY.alias-filter
A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2
thorntail.elytron.filtering-key-stores.KEY.key-store
Name of filtered KeyStore.
thorntail.elytron.filtering-key-stores.KEY.state
The state of the underlying service that represents this KeyStore at runtime, if it is anything other than UP runtime operations will not be available.
thorntail.elytron.final-providers
Reference to the Providers that should be registered after all existing Providers.
thorntail.elytron.http-authentication-factories.KEY.available-mechanisms
The HTTP mechanisms available from this configuration after all filtering has been applied.
thorntail.elytron.http-authentication-factories.KEY.http-server-mechanism-factory
The HttpServerAuthenticationMechanismFactory to associate with this resource
thorntail.elytron.http-authentication-factories.KEY.mechanism-configurations
Mechanism specific configuration
thorntail.elytron.http-authentication-factories.KEY.security-domain
The SecurityDomain to associate with this resource
thorntail.elytron.identity-realms.KEY.attribute-name
The name of the attribute associated with this identity.
thorntail.elytron.identity-realms.KEY.attribute-values
The values associated with the identity attributes.
thorntail.elytron.identity-realms.KEY.identity
The name of the identity available from the security realm.
thorntail.elytron.initial-providers
Reference to the Providers that should be registered ahead of all existing Providers.
thorntail.elytron.jaspi-configurations.KEY.application-context
The application-context this configuration is to be associated with or '*' for all application contexts.
thorntail.elytron.jaspi-configurations.KEY.description
Description of this configuration.
thorntail.elytron.jaspi-configurations.KEY.layer
The layer this configuration is to be associated with or '*' for all layers.
thorntail.elytron.jaspi-configurations.KEY.server-auth-modules
List of ServerAuthModule definitions for this configuration.
thorntail.elytron.jdbc-realms.KEY.principal-query
The authentication query used to authenticate users based on specific key types.
thorntail.elytron.kerberos-security-factories.KEY.debug
Should the JAAS step of obtaining the credential have debug logging enabled.
thorntail.elytron.kerberos-security-factories.KEY.fail-cache
Amount of seconds before new try to obtain server credential should be done if it has failed last time.
thorntail.elytron.kerberos-security-factories.KEY.mechanism-names
The mechanism names the credential should be usable with. Names will be converted to OIDs and used together with OIDs from mechanism-oids attribute.
thorntail.elytron.kerberos-security-factories.KEY.mechanism-oids
The mechanism OIDs the credential should be usable with. Will be used together with OIDs derived from names from mechanism-names attribute.
thorntail.elytron.kerberos-security-factories.KEY.minimum-remaining-lifetime
How much lifetime (in seconds) should a cached credential have remaining before it is recreated.
thorntail.elytron.kerberos-security-factories.KEY.obtain-kerberos-ticket
Should the KerberosTicket also be obtained and associated with the credential. This is required to be true where credentials are delegated to the server.
thorntail.elytron.kerberos-security-factories.KEY.options
The Krb5LoginModule additional options.
thorntail.elytron.kerberos-security-factories.KEY.path
The path of the KeyTab to load to obtain the credential.
thorntail.elytron.kerberos-security-factories.KEY.principal
The principal represented by the KeyTab
thorntail.elytron.kerberos-security-factories.KEY.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.elytron.kerberos-security-factories.KEY.request-lifetime
How much lifetime (in seconds) should be requested for newly created credentials.
thorntail.elytron.kerberos-security-factories.KEY.required
Is the keytab file with adequate principal required to exist at the time the service starts?
thorntail.elytron.kerberos-security-factories.KEY.server
If this for use server side or client side?
thorntail.elytron.kerberos-security-factories.KEY.wrap-gss-credential
Should generated GSS credentials be wrapped to prevent improper disposal or not?
thorntail.elytron.key-managers.KEY.algorithm
The name of the algorithm to use to create the underlying KeyManagerFactory.
thorntail.elytron.key-managers.KEY.alias-filter
A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2
thorntail.elytron.key-managers.KEY.credential-reference
The credential reference to decrypt KeyStore item. (Not a password of the KeyStore.)
thorntail.elytron.key-managers.KEY.key-store
Reference to the KeyStore to use to initialise the underlying KeyManagerFactory.
thorntail.elytron.key-managers.KEY.provider-name
The name of the provider to use to create the underlying KeyManagerFactory.
thorntail.elytron.key-managers.KEY.providers
Reference to obtain the Provider[] to use when creating the underlying KeyManagerFactory.
thorntail.elytron.key-store-realms.KEY.key-store
Reference to the KeyStore that should be used to back this security realm.
thorntail.elytron.key-stores.KEY.alias-filter
A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2
thorntail.elytron.key-stores.KEY.attribute-synchronized
The time this KeyStore was last loaded or saved. Note: Some providers may continue to apply updates after the KeyStore was loaded within the application server.
thorntail.elytron.key-stores.KEY.credential-reference
The reference to credential stored in CredentialStore under defined alias or clear text password.
thorntail.elytron.key-stores.KEY.loaded-provider
Information about the provider that was used for this KeyStore.
thorntail.elytron.key-stores.KEY.modified
Indicates if the in-memory representation of the KeyStore has been changed since it was last loaded or stored. Note: For some providers updates may be immediate without further load or store calls.
thorntail.elytron.key-stores.KEY.path
The path to the KeyStore file.
thorntail.elytron.key-stores.KEY.provider-name
The name of the provider to use to load the KeyStore, disables searching for the first Provider that can create a KeyStore of the specified type.
thorntail.elytron.key-stores.KEY.providers
A reference to the providers that should be used to obtain the list of Provider instances to search, if not specified the global list of providers will be used instead.
thorntail.elytron.key-stores.KEY.relative-to
The base path this store is relative to.
thorntail.elytron.key-stores.KEY.required
Is the file required to exist at the time the KeyStore service starts?
thorntail.elytron.key-stores.KEY.size
The number of entries in the KeyStore.
thorntail.elytron.key-stores.KEY.state
The state of the underlying service that represents this KeyStore at runtime, if it is anything other than UP runtime operations will not be available.
thorntail.elytron.key-stores.KEY.type
The type of the KeyStore, used when creating the new KeyStore instance.
thorntail.elytron.ldap-key-stores.KEY.alias-attribute
The name of LDAP attribute, where will be item alias stored.
thorntail.elytron.ldap-key-stores.KEY.certificate-attribute
The name of LDAP attribute, where will be certificate stored.
thorntail.elytron.ldap-key-stores.KEY.certificate-chain-attribute
The name of LDAP attribute, where will be certificate chain stored.
thorntail.elytron.ldap-key-stores.KEY.certificate-chain-encoding
The encoding of the certificate chain.
thorntail.elytron.ldap-key-stores.KEY.certificate-type
The type of the Certificate.
thorntail.elytron.ldap-key-stores.KEY.dir-context
The name of DirContext, which will be used to communication with LDAP server.
thorntail.elytron.ldap-key-stores.KEY.filter-alias
The LDAP filter for obtaining an item of the KeyStore by alias. If this is not specified then the default value will be (alias_attribute={0}). The string '{0}' will be replaced by the searched alias and the 'alias_attribute' value will be the value of the attribute 'alias-attribute'.
thorntail.elytron.ldap-key-stores.KEY.filter-certificate
The LDAP filter for obtaining an item of the KeyStore by certificate. If this is not specified then the default value will be (certificate_attribute={0}). The string '{0}' will be replaced by searched encoded certificate and the 'certificate_attribute' will be the value of the attribute 'certificate-attribute'.
thorntail.elytron.ldap-key-stores.KEY.filter-iterate
The LDAP filter for iterating over all items of the KeyStore. If this is not specified then the default value will be (alias_attribute=*). The 'alias_attribute' will be the value of the attribute 'alias-attribute'.
thorntail.elytron.ldap-key-stores.KEY.key-attribute
The name of LDAP attribute, where will be key stored.
thorntail.elytron.ldap-key-stores.KEY.key-type
The type of KeyStore, in which will be key serialized to LDAP attribute.
thorntail.elytron.ldap-key-stores.KEY.new-item-template
Configuration for item creation. Define how will look LDAP entry of newly created keystore item.
thorntail.elytron.ldap-key-stores.KEY.search-path
The path in LDAP, where will be KeyStore items searched.
thorntail.elytron.ldap-key-stores.KEY.search-recursive
If the LDAP search should be recursive.
thorntail.elytron.ldap-key-stores.KEY.search-time-limit
The time limit for obtaining keystore items from LDAP.
thorntail.elytron.ldap-key-stores.KEY.size
The size of LDAP KeyStore in amount of items/aliases.
thorntail.elytron.ldap-key-stores.KEY.state
The state of the underlying service that represents this KeyStore at runtime, if it is anything other than UP runtime operations will not be available.
thorntail.elytron.ldap-realms.KEY.allow-blank-password
Does this realm support blank password direct verification? Blank password attempt will be rejected otherwise.
thorntail.elytron.ldap-realms.KEY.dir-context
The configuration to connect to a LDAP server.
thorntail.elytron.ldap-realms.KEY.direct-verification
Does this realm support verification of credentials by directly connecting to LDAP as the account being authenticated?
thorntail.elytron.ldap-realms.KEY.identity-mapping
The configuration options that define how principals are mapped to their corresponding entries in the underlying LDAP server.
thorntail.elytron.logical-permission-mappers.KEY.left
Reference to the permission mapper to use to the left of the operation.
thorntail.elytron.logical-permission-mappers.KEY.logical-operation
The logical operation to use to combine the permission mappers.
thorntail.elytron.logical-permission-mappers.KEY.right
Reference to the permission mapper to use to the right of the operation.
thorntail.elytron.logical-role-mappers.KEY.left
Reference to a role mapper to be used on the left side of the operation.
thorntail.elytron.logical-role-mappers.KEY.logical-operation
The logical operation to be performed on the role mapper mappings.
thorntail.elytron.logical-role-mappers.KEY.right
Reference to a role mapper to be used on the right side of the operation.
thorntail.elytron.mapped-regex-realm-mappers.KEY.delegate-realm-mapper
The RealmMapper to delegate to if the pattern does not match. If no delegate is specified then the default realm on the domain will be used instead. If the username does not match the pattern and a delegate realm-mapper is present, the result of delegate-realm-mapper is mapped via the realm-map.
thorntail.elytron.mapped-regex-realm-mappers.KEY.pattern
The regular expression which must contain at least one capture group to extract the realm from the name. If the regular expression matches more than one capture group, the first capture group is used.
thorntail.elytron.mapped-regex-realm-mappers.KEY.realm-map
Mapping of realm name extracted using the regular expression to a defined realm name. If the value for the mapping is not in the map or the realm whose name is the result of the mapping does not exist in the given security domain, the default realm is used.
thorntail.elytron.mapped-role-mappers.KEY.keep-mapped
When set to 'true' the mapped roles will retain all roles, that have defined mappings.
thorntail.elytron.mapped-role-mappers.KEY.keep-non-mapped
When set to 'true' the mapped roles will retain all roles, that have no defined mappings.
thorntail.elytron.mapped-role-mappers.KEY.role-map
A string to string list map for mapping roles.
thorntail.elytron.mechanism-provider-filtering-sasl-server-factories.KEY.available-mechanisms
The SASL mechanisms available from this factory after all filtering has been applied.
thorntail.elytron.mechanism-provider-filtering-sasl-server-factories.KEY.enabling
When set to 'true' no provider loaded mechanisms are enabled unless matched by one of the filters, setting to 'false' has the inverse effect.
thorntail.elytron.mechanism-provider-filtering-sasl-server-factories.KEY.filters
The filters to apply when comparing the mechanisms from the providers, a filter matches when all of the specified values match the mechanism / provider pair.
thorntail.elytron.mechanism-provider-filtering-sasl-server-factories.KEY.sasl-server-factory
Reference to a sasl server factory to be wrapped by this definition.
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.attribute-synchronized
Whether every event should be immediately synchronised to disk.
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.autoflush
Whether every event should be immediately flushed to disk (If undefined will default to the value of synchronized).
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.format
The format to use to record the audit event.
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.path
Path of the file to be written.
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.relative-to
The relative path to the audit log.
thorntail.elytron.periodic-rotating-file-audit-logs.KEY.suffix
The suffix string in a format which can be understood by java.time.format.DateTimeFormatter. The period of the rotation is automatically calculated based on the suffix.
thorntail.elytron.permission-sets.KEY.permissions
The permissions in the permission set.
thorntail.elytron.policies.KEY.custom-policy
A custom policy provider definition.
thorntail.elytron.policies.KEY.jacc-policy
A policy provider definition that sets up JACC and related services.
thorntail.elytron.properties-realms.KEY.attribute-synchronized
The time the properties files that back this realm were last loaded.
thorntail.elytron.properties-realms.KEY.groups-attribute
The name of the attribute in the returned AuthorizationIdentity that should contain the group membership information for the identity.
thorntail.elytron.properties-realms.KEY.groups-properties
The properties file containing the users and their groups.
thorntail.elytron.properties-realms.KEY.users-properties
The properties file containing the users and their passwords.
thorntail.elytron.provider-http-server-mechanism-factories.KEY.available-mechanisms
The HTTP mechanisms available from this factory instance.
thorntail.elytron.provider-http-server-mechanism-factories.KEY.providers
The providers to use to locate the factories, if not specified the globally registered list of Providers will be used.
thorntail.elytron.provider-loaders.KEY.argument
An argument to be passed into the constructor as the Provider is instantiated.
thorntail.elytron.provider-loaders.KEY.class-names
The fully qualified class names of the providers to load, these are loaded after the service-loader discovered providers and duplicates will be skipped.
thorntail.elytron.provider-loaders.KEY.configuration
The key/value configuration to be passed to the Provider to initialise it.
thorntail.elytron.provider-loaders.KEY.loaded-providers
The list of providers loaded by this provider loader.
thorntail.elytron.provider-loaders.KEY.module
The name of the module to load the provider from.
thorntail.elytron.provider-loaders.KEY.path
The path of the file to use to initialise the providers.
thorntail.elytron.provider-loaders.KEY.relative-to
The base path of the configuration file.
thorntail.elytron.provider-sasl-server-factories.KEY.available-mechanisms
The SASL mechanisms available from this factory after all filtering has been applied.
thorntail.elytron.provider-sasl-server-factories.KEY.providers
The providers to use to locate the factories, if not specified the globally registered list of Providers will be used.
thorntail.elytron.regex-principal-transformers.KEY.pattern
The regular expression to use to locate the portion of the name to be replaced.
thorntail.elytron.regex-principal-transformers.KEY.replace-all
Should all occurrences of the pattern matched be replaced or only the first occurrence.
thorntail.elytron.regex-principal-transformers.KEY.replacement
The value to be used as the replacement.
thorntail.elytron.regex-validating-principal-transformers.KEY.match
If set to true, the name must match the given pattern to make validation successful. If set to false, the name must not match the given pattern to make validation successful.
thorntail.elytron.regex-validating-principal-transformers.KEY.pattern
The regular expression to use for the principal transformer.
thorntail.elytron.register-jaspi-factory
Should the Elytron JASPI factory be globally registered?
thorntail.elytron.sasl-authentication-factories.KEY.available-mechanisms
The SASL mechanisms available from this configuration after all filtering has been applied.
thorntail.elytron.sasl-authentication-factories.KEY.mechanism-configurations
Mechanism specific configuration
thorntail.elytron.sasl-authentication-factories.KEY.sasl-server-factory
The SaslServerFactory to associate with this resource
thorntail.elytron.sasl-authentication-factories.KEY.security-domain
The SecurityDomain to associate with this resource
thorntail.elytron.security-domains.KEY.default-realm
The default realm contained by this security domain.
thorntail.elytron.security-domains.KEY.outflow-anonymous
When outflowing to a security domain if outflow is not possible should the anonymous identity be used? Outflowing anonymous has the effect of clearing any identity already established for that domain.
thorntail.elytron.security-domains.KEY.outflow-security-domains
The list of security domains that the security identity from this domain should automatically outflow to.
thorntail.elytron.security-domains.KEY.permission-mapper
A reference to a PermissionMapper to be used by this domain.
thorntail.elytron.security-domains.KEY.post-realm-principal-transformer
A reference to a principal transformer to be applied after the realm has operated on the supplied identity name.
thorntail.elytron.security-domains.KEY.pre-realm-principal-transformer
A reference to a principal transformer to be applied before the realm is selected.
thorntail.elytron.security-domains.KEY.principal-decoder
A reference to a PrincipalDecoder to be used by this domain.
thorntail.elytron.security-domains.KEY.realm-mapper
Reference to the RealmMapper to be used by this domain.
thorntail.elytron.security-domains.KEY.realms
The list of realms contained by this security domain.
thorntail.elytron.security-domains.KEY.role-mapper
Reference to the RoleMapper to be used by this domain.
thorntail.elytron.security-domains.KEY.security-event-listener
Reference to a listener for security events.
thorntail.elytron.security-domains.KEY.trusted-security-domains
The list of security domains that are trusted by this security domain.
thorntail.elytron.security-properties
Security properties to be set.
thorntail.elytron.server-ssl-contexts.KEY.active-session-count
The count of current active sessions.
thorntail.elytron.server-ssl-contexts.KEY.authentication-optional
Rejecting of the client certificate by the security domain will not prevent the connection. Allows a fall through to use other authentication mechanisms (like form login) when the client certificate is rejected by security domain. Has an effect only when the security domain is set.
thorntail.elytron.server-ssl-contexts.KEY.cipher-suite-filter
The filter to apply to specify the enabled cipher suites.
thorntail.elytron.server-ssl-contexts.KEY.final-principal-transformer
A final principal transformer to apply for this mechanism realm.
thorntail.elytron.server-ssl-contexts.KEY.key-manager
Reference to the key manager to use within the SSLContext.
thorntail.elytron.server-ssl-contexts.KEY.maximum-session-cache-size
The maximum number of SSL sessions in the cache. The default value -1 means use the JVM default value. Value zero means there is no limit.
thorntail.elytron.server-ssl-contexts.KEY.need-client-auth
To require a client certificate on SSL handshake. Connection without trusted client certificate (see trust-manager) will be rejected.
thorntail.elytron.server-ssl-contexts.KEY.post-realm-principal-transformer
A principal transformer to apply after the realm is selected.
thorntail.elytron.server-ssl-contexts.KEY.pre-realm-principal-transformer
A principal transformer to apply before the realm is selected.
thorntail.elytron.server-ssl-contexts.KEY.protocols
The enabled protocols.
thorntail.elytron.server-ssl-contexts.KEY.provider-name
The name of the provider to use. If not specified, all providers from providers will be passed to the SSLContext.
thorntail.elytron.server-ssl-contexts.KEY.providers
The name of the providers to obtain the Provider[] to use to load the SSLContext.
thorntail.elytron.server-ssl-contexts.KEY.realm-mapper
The realm mapper to be used for SSL authentication.
thorntail.elytron.server-ssl-contexts.KEY.security-domain
The security domain to use for authentication during SSL session establishment.
thorntail.elytron.server-ssl-contexts.KEY.session-timeout
The timeout for SSL sessions, in seconds. The default value -1 means use the JVM default value. Value zero means there is no limit.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.application-buffer-size
The application buffer size as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.cipher-suite
The selected cipher suite as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.creation-time
The creation time as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.last-accessed-time
The last accessed time as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.local-certificates
The local certificates from the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.local-principal
The local principal as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.packet-buffer-size
The packet buffer size as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.peer-certificates
The peer certificates from the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.peer-host
The peer host as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.peer-port
The peer port as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.peer-principal
The peer principal as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.protocol
The protocol as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.ssl-sessions.KEY.valid
The validity of the session as reported by the SSLSession.
thorntail.elytron.server-ssl-contexts.KEY.trust-manager
Reference to the trust manager to use within the SSLContext.
thorntail.elytron.server-ssl-contexts.KEY.use-cipher-suites-order
To honor local cipher suites preference.
thorntail.elytron.server-ssl-contexts.KEY.want-client-auth
To request (but not to require) a client certificate on SSL handshake. If a security domain is referenced and supports X509 evidence, this will be set to true automatically. Ignored when need-client-auth is set.
thorntail.elytron.server-ssl-contexts.KEY.wrap
Should the SSLEngine, SSLSocket, and SSLServerSocket instances returned be wrapped to protect against further modification.
thorntail.elytron.server-ssl-sni-contexts.KEY.default-ssl-context
The context to use if no SNI information is present, or if it does not match any mappings
thorntail.elytron.server-ssl-sni-contexts.KEY.host-context-map
A mapping between a server name and an SSContext
thorntail.elytron.service-loader-http-server-mechanism-factories.KEY.available-mechanisms
The HTTP mechanisms available from this factory instance.
thorntail.elytron.service-loader-http-server-mechanism-factories.KEY.module
The module to use to obtain the classloader to load the factories, if not specified the classloader to load the resource will be used instead.
thorntail.elytron.service-loader-sasl-server-factories.KEY.available-mechanisms
The SASL mechanisms available from this factory after all filtering has been applied.
thorntail.elytron.service-loader-sasl-server-factories.KEY.module
The module to use to obtain the classloader to load the factories, if not specified the classloader to load the resource will be used instead.
thorntail.elytron.simple-permission-mappers.KEY.mapping-mode
The mapping mode that should be used in the event of multiple matches.
thorntail.elytron.simple-permission-mappers.KEY.permission-mappings
The defined permission mappings.
thorntail.elytron.simple-regex-realm-mappers.KEY.delegate-realm-mapper
The RealmMapper to delegate to if there is no match using the pattern.
thorntail.elytron.simple-regex-realm-mappers.KEY.pattern
The regular expression which must contain at least one capture group to extract the realm from the name. If the regular expression matches more than one capture group, the first capture group is used.
thorntail.elytron.simple-role-decoders.KEY.attribute
The name of the attribute from the identity to map directly to roles.
thorntail.elytron.size-rotating-file-audit-logs.KEY.attribute-synchronized
Whether every event should be immediately flushed to disk (If undefined will default to the value of synchronized).
thorntail.elytron.size-rotating-file-audit-logs.KEY.autoflush
Whether every event should be immediately flushed to disk.
thorntail.elytron.size-rotating-file-audit-logs.KEY.format
The format to use to record the audit event.
thorntail.elytron.size-rotating-file-audit-logs.KEY.max-backup-index
The maximum number of files to backup when rotating.
thorntail.elytron.size-rotating-file-audit-logs.KEY.path
Path of the file to be written.
thorntail.elytron.size-rotating-file-audit-logs.KEY.relative-to
The relative path to the audit log.
thorntail.elytron.size-rotating-file-audit-logs.KEY.rotate-on-boot
Whether the file should be rotated before the a new file is set.
thorntail.elytron.size-rotating-file-audit-logs.KEY.rotate-size
The log file size the file should rotate at.
thorntail.elytron.size-rotating-file-audit-logs.KEY.suffix
Format of date used as suffix of log file names in java.time.format.DateTimeFormatter. The suffix does not play a role in determining when the file should be rotated.
thorntail.elytron.syslog-audit-logs.KEY.format
The format to use to record the audit event.
thorntail.elytron.syslog-audit-logs.KEY.host-name
The host name to embed withing all events sent to the remote syslog server.
thorntail.elytron.syslog-audit-logs.KEY.port
The listening port on the syslog server.
thorntail.elytron.syslog-audit-logs.KEY.server-address
The server address of the syslog server the events should be sent to.
thorntail.elytron.syslog-audit-logs.KEY.ssl-context
The SSLContext to use to connect to the syslog server when SSL_TCP transport is used.
thorntail.elytron.syslog-audit-logs.KEY.transport
The transport to use to connect to the syslog server.
thorntail.elytron.token-realms.KEY.jwt
A token validator to be used in conjunction with a token-based realm that handles security tokens based on the JWT/JWS standard.
thorntail.elytron.token-realms.KEY.oauth2-introspection
A token validator to be used in conjunction with a token-based realm that handles OAuth2 Access Tokens and validates them using an endpoint compliant with OAuth2 Token Introspection specification(RFC-7662).
thorntail.elytron.token-realms.KEY.principal-claim
The name of the claim that should be used to obtain the principal’s name.
thorntail.elytron.trust-managers.KEY.algorithm
The name of the algorithm to use to create the underlying TrustManagerFactory.
thorntail.elytron.trust-managers.KEY.alias-filter
A filter to apply to the aliases returned from the KeyStore, can either be a comma separated list of aliases to return or one of the following formats ALL:-alias1:-alias2, NONE:+alias1:+alias2
thorntail.elytron.trust-managers.KEY.certificate-revocation-list
Enables certificate revocation list checks to a trust manager.
thorntail.elytron.trust-managers.KEY.key-store
Reference to the KeyStore to use to initialise the underlying TrustManagerFactory.
thorntail.elytron.trust-managers.KEY.provider-name
The name of the provider to use to create the underlying TrustManagerFactory.
thorntail.elytron.trust-managers.KEY.providers
Reference to obtain the Provider[] to use when creating the underlying TrustManagerFactory.
thorntail.elytron.x500-attribute-principal-decoders.KEY.attribute-name
The name of the X.500 attribute to map (can be defined using OID instead)
thorntail.elytron.x500-attribute-principal-decoders.KEY.convert
When set to 'true', if the Principal is not already an X500Principal conversion will be attempted
thorntail.elytron.x500-attribute-principal-decoders.KEY.joiner
The joining string
thorntail.elytron.x500-attribute-principal-decoders.KEY.maximum-segments
The maximum number of occurrences of the attribute to map
thorntail.elytron.x500-attribute-principal-decoders.KEY.oid
The OID of the X.500 attribute to map (can be defined using attribute name instead)
thorntail.elytron.x500-attribute-principal-decoders.KEY.required-attributes
The attributes names of the attributes that must be present in the principal
thorntail.elytron.x500-attribute-principal-decoders.KEY.required-oids
The OIDs of the attributes that must be present in the principal
thorntail.elytron.x500-attribute-principal-decoders.KEY.reverse
When set to 'true', the attribute values will be processed and returned in reverse order
thorntail.elytron.x500-attribute-principal-decoders.KEY.start-segment
The 0-based starting occurrence of the attribute to map

D.10. Hibernate Validator

Provides support and integration for applications using Hibernate Validator.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>hibernate-validator</artifactId>
</dependency>

D.11. Hystrix

Warning

This fraction is deprecated.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>hystrix</artifactId>
</dependency>

Configuration

thorntail.hystrix.collapser.default.maxRequestsInBatch
The maximum number of requests allowed in a batch before this triggers a batch execution
thorntail.hystrix.collapser.default.requestCache.enabled
Indicates whether request caching is enabled for HystrixCollapser.execute() and HystrixCollapser.queue() invocations
thorntail.hystrix.collapser.default.timerDelayInMilliseconds
The number of milliseconds after the creation of the batch that its execution is triggered
thorntail.hystrix.command.default.circuitBreaker.enabled
Determines whether a circuit breaker will be used to track health and to short-circuit requests if it trips
thorntail.hystrix.command.default.circuitBreaker.errorThresholdPercentage
The error percentage at or above which the circuit should trip open and start short-circuiting requests to fallback logic
thorntail.hystrix.command.default.circuitBreaker.forceClosed
If true, forces the circuit breaker into a closed state in which it will allow requests regardless of the error percentage
thorntail.hystrix.command.default.circuitBreaker.forceOpen
If true, forces the circuit breaker into an open (tripped) state in which it will reject all requests
thorntail.hystrix.command.default.circuitBreaker.requestVolumeThreshold
The minimum number of requests in a rolling window that will trip the circuit
thorntail.hystrix.command.default.circuitBreaker.sleepWindowInMilliseconds
The amount of time, after tripping the circuit, to reject requests before allowing attempts again to determine if the circuit should again be closed
thorntail.hystrix.command.default.execution.isolation.semaphore.maxConcurrentRequests
The maximum number of requests allowed to a HystrixCommand.run() method when you are using ExecutionIsolationStrategy.SEMAPHORE
thorntail.hystrix.command.default.execution.isolation.strategy
Isolation strategy (THREAD or SEMAPHORE)
thorntail.hystrix.command.default.execution.isolation.thread.interruptOnCancel
Indicates whether the HystrixCommand.run() execution should be interrupted when a cancellation occurs
thorntail.hystrix.command.default.execution.isolation.thread.interruptOnTimeout
Indicates whether the HystrixCommand.run() execution should be interrupted when a timeout occurs
thorntail.hystrix.command.default.execution.isolation.thread.timeoutInMilliseconds
The time in milliseconds after which the caller will observe a timeout and walk away from the command execution
thorntail.hystrix.command.default.execution.timeout.enabled
Indicates whether the HystrixCommand.run() execution should have a timeout
thorntail.hystrix.command.default.fallback.enabled
Determines whether a call to HystrixCommand.getFallback() will be attempted when failure or rejection occurs
thorntail.hystrix.command.default.fallback.isolation.semaphore.maxConcurrentRequests
The maximum number of requests allowed to a HystrixCommand.getFallback() method when you are using ExecutionIsolationStrategy.SEMAPHORE
thorntail.hystrix.command.default.metrics.healthSnapshot.intervalInMilliseconds
The time to wait, in milliseconds, between allowing health snapshots to be taken that calculate success and error percentages and affect circuit breaker status
thorntail.hystrix.command.default.metrics.rollingPercentile.bucketSize
The maximum number of execution times that are kept per bucket
thorntail.hystrix.command.default.metrics.rollingPercentile.enabled
Indicates whether execution latencies should be tracked and calculated as percentiles
thorntail.hystrix.command.default.metrics.rollingPercentile.numBuckets
The number of buckets the rollingPercentile window will be divided into
thorntail.hystrix.command.default.metrics.rollingPercentile.timeInMilliseconds
The duration of the rolling window in which execution times are kept to allow for percentile calculations, in milliseconds
thorntail.hystrix.command.default.metrics.rollingStats.numBuckets
The number of buckets the rolling statistical window is divided into
thorntail.hystrix.command.default.metrics.rollingStats.timeInMilliseconds
The duration of the statistical rolling window, in milliseconds. This is how long Hystrix keeps metrics for the circuit breaker to use and for publishing
thorntail.hystrix.command.default.requestCache.enabled
Indicates whether HystrixCommand.getCacheKey() should be used with HystrixRequestCache to provide de-duplication functionality via request-scoped caching
thorntail.hystrix.command.default.requestLog.enabled
Indicates whether HystrixCommand execution and events should be logged to HystrixRequestLog
thorntail.hystrix.stream.path
Context path for the stream
thorntail.hystrix.threadpool.default.allowMaximumSizeToDivergeFromCoreSize
Allows the configuration for maximumSize to take effect
thorntail.hystrix.threadpool.default.coreSize
The core thread-pool size
thorntail.hystrix.threadpool.default.keepAliveTimeMinutes
The keep-alive time, in minutes
thorntail.hystrix.threadpool.default.maxQueueSize
The maximum queue size of the BlockingQueue implementation
thorntail.hystrix.threadpool.default.maximumSize
The maximum thread-pool size
thorntail.hystrix.threadpool.default.metrics.rollingPercentile.numBuckets
The number of buckets the rolling statistical window is divided into
thorntail.hystrix.threadpool.default.metrics.rollingStats.timeInMilliseconds
The duration of the statistical rolling window, in milliseconds
thorntail.hystrix.threadpool.default.queueSizeRejectionThreshold
The queue size rejection threshold - an artificial maximum queue size at which rejections will occur even if maxQueueSize has not been reached

D.12. Infinispan

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>infinispan</artifactId>
</dependency>

Configuration

thorntail.infinispan.cache-containers.KEY.aliases
The list of aliases for this cache container
thorntail.infinispan.cache-containers.KEY.async-operations-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.async-operations-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.async-operations-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.async-operations-thread-pool.queue-length
The queue length.
thorntail.infinispan.cache-containers.KEY.cache-manager-status
The status of the cache manager component. May return null if the cache manager is not started.
thorntail.infinispan.cache-containers.KEY.cluster-name
The name of the cluster this node belongs to. May return null if the cache manager is not started.
thorntail.infinispan.cache-containers.KEY.coordinator-address
The logical address of the cluster’s coordinator. May return null if the cache manager is not started.
thorntail.infinispan.cache-containers.KEY.default-cache
The default infinispan cache
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.activations
The number of cache node activations (bringing a node into memory from a cache store) . May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.async-marshalling
If enabled, this will cause marshalling of entries to be performed asynchronously.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.average-read-time
Average time (in ms) for cache reads. Includes hits and misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.average-replication-time
The average time taken to replicate data around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.average-write-time
Average time (in ms) for cache writes. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.after-failures
Indicates the number of failures after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.enabled
Indicates whether or not this backup site is enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.failure-policy
The policy to follow when connectivity to the backup site fails.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.min-wait
Indicates the minimum time (in milliseconds) to wait after the max number of failures is reached, after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.strategy
The backup strategy for this cache
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.backups-component.backups.KEY.timeout
The timeout for replicating to the backup site.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.binary-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.cache-status
The status of the cache component. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.capacity-factor
Controls the proportion of entries that will reside on the local node, compared to the other nodes in the cluster.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.consistent-hash-strategy
Defines the consistent hash strategy for the cache.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.attribute-class
The custom store implementation class to use for this cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.custom-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.elapsed-time
Time (in secs) since cache started. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.expiration-component.interval
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.expiration-component.lifespan
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.expiration-component.max-idle
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.path
The system path under which this cache store will persist its entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.relative-to
The system path to which the specified path is relative.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.file-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hit-ratio
The hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hits
The number of cache attribute hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.cache-configuration
Name of the cache configuration template defined in Infinispan Server to create caches from.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.remote-cache-container
Reference to a container-managed remote-cache-container.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.hotrod-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.indexing
If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.indexing-properties
Properties to control indexing behaviour
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.invalidations
The number of cache invalidations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.l1-lifespan
Maximum lifespan of an entry placed in the L1 cache. This element configures the L1 cache behavior in 'distributed' caches instances. In any other cache modes, this element is ignored.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.acquire-timeout
Maximum time to attempt a particular lock acquisition.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.concurrency-level
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.current-concurrency-level
The estimated number of concurrently updating threads which this cache can support. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.isolation
Sets the cache locking isolation level.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.number-of-locks-available
The number of locks available to this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.number-of-locks-held
The number of locks currently in use by this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.locking-component.striping
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.misses
The number of cache attribute misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.mixed-jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.module
The module whose class loader should be used when building this cache’s configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.number-of-entries
The current number of entries in the cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.object-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.object-memory.size
Triggers eviction of the least recently used entries when the number of cache entries exceeds this threshold.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.off-heap-memory.capacity
Defines the capacity of the off-heap storage.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.off-heap-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.off-heap-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.off-heap-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.owners
Number of cluster-wide replicas for each cache entry.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.partition-handling-component.availability
Indicates the current availability of the cache.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.partition-handling-component.enabled
If enabled, the cache will enter degraded mode upon detecting a network partition that threatens the integrity of the cache.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.passivations
The number of cache node passivations (passivating a node from memory to a cache store). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.queue-flush-interval
In ASYNC mode, this attribute controls how often the asynchronous thread used to flush the replication queue runs. This should be a positive integer which represents thread wakeup time in milliseconds.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.queue-size
In ASYNC mode, this attribute can be used to trigger flushing of the queue when it reaches a specific threshold.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.read-write-ratio
The read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.cache
The name of the remote cache to use for this remote store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.remote-servers
A list of remote servers for this cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.socket-timeout
A socket timeout for remote cache communication.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-store.tcp-no-delay
A TCP_NODELAY value for remote cache communication.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remote-timeout
In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remove-hits
The number of cache attribute remove hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.remove-misses
The number of cache attribute remove misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.replication-count
The number of times data was replicated around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.replication-failures
The number of data replication failures. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.segments
Controls the number of hash space segments which is the granularity for key distribution in the cluster. Value must be strictly positive.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.state-transfer-component.chunk-size
The maximum number of cache entries in a batch of transferred state.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.state-transfer-component.enabled
If enabled, this will cause the cache to ask neighboring caches for state when it starts up, so the cache starts 'warm', although it will impact startup time.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.state-transfer-component.timeout
The maximum amount of time (ms) to wait for state from neighboring caches, before throwing an exception and aborting startup. If timeout is 0, state transfer is performed asynchronously, and the cache will be immediately available.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.statistics-enabled
If enabled, statistics will be collected for this cache
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.stores
The number of cache attribute put operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.success-ratio
The data replication success ratio (successes/successes+failures). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.time-since-reset
Time (in secs) since cache statistics were reset. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.commits
The number of transaction commits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.locking
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.mode
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.prepares
The number of transaction prepares. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.rollbacks
The number of transaction rollbacks. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.distributed-caches.KEY.transaction-component.stop-timeout
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
thorntail.infinispan.cache-containers.KEY.expiration-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.expiration-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.activations
The number of cache node activations (bringing a node into memory from a cache store) . May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.async-marshalling
If enabled, this will cause marshalling of entries to be performed asynchronously.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.average-read-time
Average time (in ms) for cache reads. Includes hits and misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.average-replication-time
The average time taken to replicate data around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.average-write-time
Average time (in ms) for cache writes. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.binary-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.cache-status
The status of the cache component. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.attribute-class
The custom store implementation class to use for this cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.custom-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.elapsed-time
Time (in secs) since cache started. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.expiration-component.interval
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.expiration-component.lifespan
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.expiration-component.max-idle
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.path
The system path under which this cache store will persist its entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.relative-to
The system path to which the specified path is relative.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.file-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hit-ratio
The hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hits
The number of cache attribute hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.cache-configuration
Name of the cache configuration template defined in Infinispan Server to create caches from.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.remote-cache-container
Reference to a container-managed remote-cache-container.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.hotrod-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.indexing
If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.indexing-properties
Properties to control indexing behaviour
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.invalidations
The number of cache invalidations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.acquire-timeout
Maximum time to attempt a particular lock acquisition.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.concurrency-level
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.current-concurrency-level
The estimated number of concurrently updating threads which this cache can support. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.isolation
Sets the cache locking isolation level.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.number-of-locks-available
The number of locks available to this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.number-of-locks-held
The number of locks currently in use by this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.locking-component.striping
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.misses
The number of cache attribute misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.mixed-jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.module
The module whose class loader should be used when building this cache’s configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.number-of-entries
The current number of entries in the cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.object-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.object-memory.size
Triggers eviction of the least recently used entries when the number of cache entries exceeds this threshold.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.off-heap-memory.capacity
Defines the capacity of the off-heap storage.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.off-heap-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.off-heap-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.off-heap-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.passivations
The number of cache node passivations (passivating a node from memory to a cache store). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.queue-flush-interval
In ASYNC mode, this attribute controls how often the asynchronous thread used to flush the replication queue runs. This should be a positive integer which represents thread wakeup time in milliseconds.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.queue-size
In ASYNC mode, this attribute can be used to trigger flushing of the queue when it reaches a specific threshold.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.read-write-ratio
The read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.cache
The name of the remote cache to use for this remote store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.remote-servers
A list of remote servers for this cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.socket-timeout
A socket timeout for remote cache communication.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-store.tcp-no-delay
A TCP_NODELAY value for remote cache communication.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remote-timeout
In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remove-hits
The number of cache attribute remove hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.remove-misses
The number of cache attribute remove misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.replication-count
The number of times data was replicated around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.replication-failures
The number of data replication failures. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.statistics-enabled
If enabled, statistics will be collected for this cache
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.stores
The number of cache attribute put operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.success-ratio
The data replication success ratio (successes/successes+failures). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.time-since-reset
Time (in secs) since cache statistics were reset. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.commits
The number of transaction commits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.locking
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.mode
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.prepares
The number of transaction prepares. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.rollbacks
The number of transaction rollbacks. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.invalidation-caches.KEY.transaction-component.stop-timeout
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
thorntail.infinispan.cache-containers.KEY.is-coordinator
Set to true if this node is the cluster’s coordinator. May return null if the cache manager is not started.
thorntail.infinispan.cache-containers.KEY.jgroups-transport.channel
The channel of this cache container’s transport.
thorntail.infinispan.cache-containers.KEY.jgroups-transport.lock-timeout
The timeout for locks for the transport
thorntail.infinispan.cache-containers.KEY.listener-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.listener-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.listener-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.listener-thread-pool.queue-length
The queue length.
thorntail.infinispan.cache-containers.KEY.local-address
The local address of the node. May return null if the cache manager is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.activations
The number of cache node activations (bringing a node into memory from a cache store) . May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.average-read-time
Average time (in ms) for cache reads. Includes hits and misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.average-write-time
Average time (in ms) for cache writes. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.binary-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.cache-status
The status of the cache component. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.attribute-class
The custom store implementation class to use for this cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.custom-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.elapsed-time
Time (in secs) since cache started. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.expiration-component.interval
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.expiration-component.lifespan
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.expiration-component.max-idle
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.path
The system path under which this cache store will persist its entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.relative-to
The system path to which the specified path is relative.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.file-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hit-ratio
The hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hits
The number of cache attribute hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.cache-configuration
Name of the cache configuration template defined in Infinispan Server to create caches from.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.remote-cache-container
Reference to a container-managed remote-cache-container.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.hotrod-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.indexing
If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.indexing-properties
Properties to control indexing behaviour
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.invalidations
The number of cache invalidations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.acquire-timeout
Maximum time to attempt a particular lock acquisition.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.concurrency-level
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.current-concurrency-level
The estimated number of concurrently updating threads which this cache can support. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.isolation
Sets the cache locking isolation level.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.number-of-locks-available
The number of locks available to this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.number-of-locks-held
The number of locks currently in use by this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.locking-component.striping
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.misses
The number of cache attribute misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.mixed-jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.module
The module whose class loader should be used when building this cache’s configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.number-of-entries
The current number of entries in the cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.object-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.object-memory.size
Triggers eviction of the least recently used entries when the number of cache entries exceeds this threshold.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.off-heap-memory.capacity
Defines the capacity of the off-heap storage.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.off-heap-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.off-heap-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.off-heap-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.passivations
The number of cache node passivations (passivating a node from memory to a cache store). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.read-write-ratio
The read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.cache
The name of the remote cache to use for this remote store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.remote-servers
A list of remote servers for this cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.socket-timeout
A socket timeout for remote cache communication.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remote-store.tcp-no-delay
A TCP_NODELAY value for remote cache communication.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remove-hits
The number of cache attribute remove hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.remove-misses
The number of cache attribute remove misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.statistics-enabled
If enabled, statistics will be collected for this cache
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.stores
The number of cache attribute put operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.time-since-reset
Time (in secs) since cache statistics were reset. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.commits
The number of transaction commits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.locking
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.mode
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.prepares
The number of transaction prepares. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.rollbacks
The number of transaction rollbacks. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.local-caches.KEY.transaction-component.stop-timeout
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
thorntail.infinispan.cache-containers.KEY.module
The module whose class loader should be used when building this cache container’s configuration.
thorntail.infinispan.cache-containers.KEY.persistence-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.persistence-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.remote-command-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.remote-command-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.remote-command-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.remote-command-thread-pool.queue-length
The queue length.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.activations
The number of cache node activations (bringing a node into memory from a cache store) . May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.async-marshalling
If enabled, this will cause marshalling of entries to be performed asynchronously.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.average-read-time
Average time (in ms) for cache reads. Includes hits and misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.average-replication-time
The average time taken to replicate data around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.average-write-time
Average time (in ms) for cache writes. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.after-failures
Indicates the number of failures after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.enabled
Indicates whether or not this backup site is enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.failure-policy
The policy to follow when connectivity to the backup site fails.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.min-wait
Indicates the minimum time (in milliseconds) to wait after the max number of failures is reached, after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.strategy
The backup strategy for this cache
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.backups-component.backups.KEY.timeout
The timeout for replicating to the backup site.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.binary-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.cache-status
The status of the cache component. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.attribute-class
The custom store implementation class to use for this cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.custom-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.elapsed-time
Time (in secs) since cache started. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.expiration-component.interval
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.expiration-component.lifespan
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.expiration-component.max-idle
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.path
The system path under which this cache store will persist its entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.relative-to
The system path to which the specified path is relative.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.file-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hit-ratio
The hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hits
The number of cache attribute hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.cache-configuration
Name of the cache configuration template defined in Infinispan Server to create caches from.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.remote-cache-container
Reference to a container-managed remote-cache-container.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.hotrod-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.indexing
If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.indexing-properties
Properties to control indexing behaviour
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.invalidations
The number of cache invalidations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.acquire-timeout
Maximum time to attempt a particular lock acquisition.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.concurrency-level
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.current-concurrency-level
The estimated number of concurrently updating threads which this cache can support. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.isolation
Sets the cache locking isolation level.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.number-of-locks-available
The number of locks available to this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.number-of-locks-held
The number of locks currently in use by this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.locking-component.striping
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.misses
The number of cache attribute misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.mixed-jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.module
The module whose class loader should be used when building this cache’s configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.number-of-entries
The current number of entries in the cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.object-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.object-memory.size
Triggers eviction of the least recently used entries when the number of cache entries exceeds this threshold.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.off-heap-memory.capacity
Defines the capacity of the off-heap storage.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.off-heap-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.off-heap-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.off-heap-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.partition-handling-component.availability
Indicates the current availability of the cache.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.partition-handling-component.enabled
If enabled, the cache will enter degraded mode upon detecting a network partition that threatens the integrity of the cache.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.passivations
The number of cache node passivations (passivating a node from memory to a cache store). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.queue-flush-interval
In ASYNC mode, this attribute controls how often the asynchronous thread used to flush the replication queue runs. This should be a positive integer which represents thread wakeup time in milliseconds.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.queue-size
In ASYNC mode, this attribute can be used to trigger flushing of the queue when it reaches a specific threshold.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.read-write-ratio
The read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.cache
The name of the remote cache to use for this remote store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.remote-servers
A list of remote servers for this cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.socket-timeout
A socket timeout for remote cache communication.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-store.tcp-no-delay
A TCP_NODELAY value for remote cache communication.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remote-timeout
In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remove-hits
The number of cache attribute remove hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.remove-misses
The number of cache attribute remove misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.replication-count
The number of times data was replicated around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.replication-failures
The number of data replication failures. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.state-transfer-component.chunk-size
The maximum number of cache entries in a batch of transferred state.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.state-transfer-component.enabled
If enabled, this will cause the cache to ask neighboring caches for state when it starts up, so the cache starts 'warm', although it will impact startup time.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.state-transfer-component.timeout
The maximum amount of time (ms) to wait for state from neighboring caches, before throwing an exception and aborting startup. If timeout is 0, state transfer is performed asynchronously, and the cache will be immediately available.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.statistics-enabled
If enabled, statistics will be collected for this cache
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.stores
The number of cache attribute put operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.success-ratio
The data replication success ratio (successes/successes+failures). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.time-since-reset
Time (in secs) since cache statistics were reset. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.commits
The number of transaction commits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.locking
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.mode
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.prepares
The number of transaction prepares. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.rollbacks
The number of transaction rollbacks. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.replicated-caches.KEY.transaction-component.stop-timeout
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.activations
The number of cache node activations (bringing a node into memory from a cache store) . May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.async-marshalling
If enabled, this will cause marshalling of entries to be performed asynchronously.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.average-read-time
Average time (in ms) for cache reads. Includes hits and misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.average-replication-time
The average time taken to replicate data around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.average-write-time
Average time (in ms) for cache writes. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.after-failures
Indicates the number of failures after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.enabled
Indicates whether or not this backup site is enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.failure-policy
The policy to follow when connectivity to the backup site fails.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.min-wait
Indicates the minimum time (in milliseconds) to wait after the max number of failures is reached, after which this backup site should go offline.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.strategy
The backup strategy for this cache
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.backups-component.backups.KEY.timeout
The timeout for replicating to the backup site.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.bias-lifespan
When greater than zero, specifies the duration (in ms) that a cache entry will be cached on a non-owner following a write operation.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.binary-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.cache-status
The status of the cache component. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.consistent-hash-strategy
Defines the consistent hash strategy for the cache.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.attribute-class
The custom store implementation class to use for this cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.custom-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.elapsed-time
Time (in secs) since cache started. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.expiration-component.interval
Interval (in milliseconds) between subsequent runs to purge expired entries from memory and any cache stores. If you wish to disable the periodic eviction process altogether, set wakeupInterval to -1.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.expiration-component.lifespan
Maximum lifespan of a cache entry, after which the entry is expired cluster-wide, in milliseconds. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.expiration-component.max-idle
Maximum idle time a cache entry will be maintained in the cache, in milliseconds. If the idle time is exceeded, the entry will be expired cluster-wide. -1 means the entries never expire.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.path
The system path under which this cache store will persist its entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.relative-to
The system path to which the specified path is relative.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.file-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hit-ratio
The hit/miss ratio for the cache (hits/hits+misses). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hits
The number of cache attribute hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.cache-configuration
Name of the cache configuration template defined in Infinispan Server to create caches from.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.remote-cache-container
Reference to a container-managed remote-cache-container.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.hotrod-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.indexing
If enabled, entries will be indexed when they are added to the cache. Indexes will be updated as entries change or are removed.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.indexing-properties
Properties to control indexing behaviour
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.invalidation-batch-size
The threshold after which batched invalidations are sent.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.invalidations
The number of cache invalidations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.acquire-timeout
Maximum time to attempt a particular lock acquisition.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.concurrency-level
Concurrency level for lock containers. Adjust this value according to the number of concurrent threads interacting with Infinispan.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.current-concurrency-level
The estimated number of concurrently updating threads which this cache can support. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.isolation
Sets the cache locking isolation level.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.number-of-locks-available
The number of locks available to this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.number-of-locks-held
The number of locks currently in use by this cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.locking-component.striping
If true, a pool of shared locks is maintained for all entries that need to be locked. Otherwise, a lock is created per entry in the cache. Lock striping helps control memory footprint but may reduce concurrency in the system.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.misses
The number of cache attribute misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-keyed-table
Defines a table used to store cache entries whose keys cannot be expressed as strings.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.binary-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.data-source
References the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.datasource
The jndi name of the data source used to connect to this store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.dialect
The dialect of this datastore.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-keyed-table
Defines a table used to store persistent cache entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-table.data-column
A database column to hold cache entry data.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-table.fetch-size
For DB queries, the fetch size will be used to set the fetch size on ResultSets.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-table.id-column
A database column to hold cache entry ids.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-table.prefix
The prefix for the database table name.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.mixed-jdbc-store.string-table.timestamp-column
A database column to hold cache entry timestamps.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.module
The module whose class loader should be used when building this cache’s configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.number-of-entries
The current number of entries in the cache. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.object-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.object-memory.size
Triggers eviction of the least recently used entries when the number of cache entries exceeds this threshold.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.off-heap-memory.capacity
Defines the capacity of the off-heap storage.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.off-heap-memory.eviction-type
Indicates whether the size attribute refers to the number of cache entries (i.e. COUNT) or the collective size of the cache entries (i.e. MEMORY).
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.off-heap-memory.evictions
The number of cache eviction operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.off-heap-memory.size
Eviction threshold, as defined by the eviction-type.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.partition-handling-component.availability
Indicates the current availability of the cache.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.partition-handling-component.enabled
If enabled, the cache will enter degraded mode upon detecting a network partition that threatens the integrity of the cache.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.passivations
The number of cache node passivations (passivating a node from memory to a cache store). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.queue-flush-interval
In ASYNC mode, this attribute controls how often the asynchronous thread used to flush the replication queue runs. This should be a positive integer which represents thread wakeup time in milliseconds.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.queue-size
In ASYNC mode, this attribute can be used to trigger flushing of the queue when it reaches a specific threshold.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.read-write-ratio
The read/write ratio of the cache ((hits+misses)/stores). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.behind-write.flush-lock-timeout
Timeout to acquire the lock which guards the state to be flushed to the cache store periodically.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.behind-write.modification-queue-size
Maximum number of entries in the asynchronous queue. When the queue is full, the store becomes write-through until it can accept new entries.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.behind-write.shutdown-timeout
Timeout in milliseconds to stop the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.behind-write.thread-pool-size
Size of the thread pool whose threads are responsible for applying the modifications to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.cache
The name of the remote cache to use for this remote store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.cache-loader-loads
The number of cache loader node loads. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.cache-loader-misses
The number of cache loader node misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.fetch-state
If true, fetch persistent state when joining a cluster. If multiple cache stores are chained, only one of them can have this property enabled.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.max-batch-size
The maximum size of a batch to be inserted/deleted from the store. If the value is less than one, then no upper limit is placed on the number of operations in a batch.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.passivation
If true, data is only written to the cache store when it is evicted from memory, a phenomenon known as 'passivation'. Next time the data is requested, it will be 'activated' which means that data will be brought back to memory and removed from the persistent store. If false, the cache store contains a copy of the contents in memory, so writes to cache result in cache store writes. This essentially gives you a 'write-through' configuration.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.preload
If true, when the cache starts, data stored in the cache store will be pre-loaded into memory. This is particularly useful when data in the cache store will be needed immediately after startup and you want to avoid cache operations being delayed as a result of loading this data lazily. Can be used to provide a 'warm-cache' on startup, however there is a performance penalty as startup time is affected by this process.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.properties
A list of cache store properties.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.properties.KEY.value
The value of the cache store property.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.purge
If true, purges this cache store when it starts up.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.remote-servers
A list of remote servers for this cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.shared
This setting should be set to true when multiple cache instances share the same cache store (e.g., multiple nodes in a cluster using a JDBC-based CacheStore pointing to the same, shared database.) Setting this to true avoids multiple cache instances writing the same modification multiple times. If enabled, only the node where the modification originated will write to the cache store. If disabled, each individual cache reacts to a potential remote update by storing the data to the cache store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.singleton
If true, the singleton store cache store is enabled. SingletonStore is a delegating cache store used for situations when only one instance in a cluster should interact with the underlying store.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.socket-timeout
A socket timeout for remote cache communication.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-store.tcp-no-delay
A TCP_NODELAY value for remote cache communication.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remote-timeout
In SYNC mode, the timeout (in ms) used to wait for an acknowledgment when making a remote call, after which the call is aborted and an exception is thrown.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remove-hits
The number of cache attribute remove hits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.remove-misses
The number of cache attribute remove misses. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.replication-count
The number of times data was replicated around the cluster. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.replication-failures
The number of data replication failures. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.segments
Controls the number of hash space segments which is the granularity for key distribution in the cluster. Value must be strictly positive.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.state-transfer-component.chunk-size
The maximum number of cache entries in a batch of transferred state.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.state-transfer-component.enabled
If enabled, this will cause the cache to ask neighboring caches for state when it starts up, so the cache starts 'warm', although it will impact startup time.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.state-transfer-component.timeout
The maximum amount of time (ms) to wait for state from neighboring caches, before throwing an exception and aborting startup. If timeout is 0, state transfer is performed asynchronously, and the cache will be immediately available.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.statistics-enabled
If enabled, statistics will be collected for this cache
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.stores
The number of cache attribute put operations. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.success-ratio
The data replication success ratio (successes/successes+failures). May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.time-since-reset
Time (in secs) since cache statistics were reset. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.commits
The number of transaction commits. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.locking
The locking mode for this cache, one of OPTIMISTIC or PESSIMISTIC.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.mode
Sets the cache transaction mode to one of NONE, NON_XA, NON_DURABLE_XA, FULL_XA.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.prepares
The number of transaction prepares. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.rollbacks
The number of transaction rollbacks. May return null if the cache is not started.
thorntail.infinispan.cache-containers.KEY.scattered-caches.KEY.transaction-component.stop-timeout
If there are any ongoing transactions when a cache is stopped, Infinispan waits for ongoing remote and local transactions to finish. The amount of time to wait for is defined by the cache stop timeout.
thorntail.infinispan.cache-containers.KEY.state-transfer-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.state-transfer-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.state-transfer-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.state-transfer-thread-pool.queue-length
The queue length.
thorntail.infinispan.cache-containers.KEY.statistics-enabled
If enabled, statistics will be collected for this cache container
thorntail.infinispan.cache-containers.KEY.transport-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.cache-containers.KEY.transport-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.transport-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.cache-containers.KEY.transport-thread-pool.queue-length
The queue length.
thorntail.infinispan.default-fraction
(not yet documented)
thorntail.infinispan.remote-cache-containers.KEY.async-thread-pool.keepalive-time
Used to specify the amount of milliseconds that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.infinispan.remote-cache-containers.KEY.async-thread-pool.max-threads
The maximum thread pool size.
thorntail.infinispan.remote-cache-containers.KEY.async-thread-pool.min-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.infinispan.remote-cache-containers.KEY.async-thread-pool.queue-length
The queue length.
thorntail.infinispan.remote-cache-containers.KEY.connection-pool-component.exhausted-action
Specifies what happens when asking for a connection from a server’s pool, and that pool is exhausted.
thorntail.infinispan.remote-cache-containers.KEY.connection-pool-component.max-active
Controls the maximum number of connections per server that are allocated (checked out to client threads, or idle in the pool) at one time. When non-positive, there is no limit to the number of connections per server. When maxActive is reached, the connection pool for that server is said to be exhausted. Value -1 means no limit.
thorntail.infinispan.remote-cache-containers.KEY.connection-pool-component.max-wait
The amount of time in milliseconds to wait for a connection to become available when the exhausted action is ExhaustedAction.WAIT, after which a java.util.NoSuchElementException will be thrown. If a negative value is supplied, the pool will block indefinitely.
thorntail.infinispan.remote-cache-containers.KEY.connection-pool-component.min-evictable-idle-time
Specifies the minimum amount of time that an connection may sit idle in the pool before it is eligible for eviction due to idle time. When non-positive, no connection will be dropped from the pool due to idle time alone. This setting has no effect unless timeBetweenEvictionRunsMillis > 0.
thorntail.infinispan.remote-cache-containers.KEY.connection-pool-component.min-idle
Sets a target value for the minimum number of idle connections (per server) that should always be available. If this parameter is set to a positive number and timeBetweenEvictionRunsMillis > 0, each time the idle connection eviction thread runs, it will try to create enough idle instances so that there will be minIdle idle instances available for each server.
thorntail.infinispan.remote-cache-containers.KEY.connection-timeout
Defines the maximum socket connect timeout before giving up connecting to the server.
thorntail.infinispan.remote-cache-containers.KEY.default-remote-cluster
Required default remote server cluster.
thorntail.infinispan.remote-cache-containers.KEY.invalidation-near-cache.max-entries
Defines the maximum number of elements to keep in the near cache.
thorntail.infinispan.remote-cache-containers.KEY.key-size-estimate
This hint allows sizing of byte buffers when serializing and deserializing keys, to minimize array resizing.
thorntail.infinispan.remote-cache-containers.KEY.max-retries
Sets the maximum number of retries for each request. A valid value should be greater or equals than 0. Zero means no retry will made in case of a network failure.
thorntail.infinispan.remote-cache-containers.KEY.module
Defines the module whose class loader should be used when configuring remote cache container marshaller.
thorntail.infinispan.remote-cache-containers.KEY.protocol-version
This property defines the protocol version that this client should use.
thorntail.infinispan.remote-cache-containers.KEY.remote-clusters.KEY.socket-bindings
List of outbound-socket-bindings of Hot Rod servers to connect to.
thorntail.infinispan.remote-cache-containers.KEY.security-component.ssl-context
Reference to the Elytron-managed SSLContext to be used for connecting to the remote cluster.
thorntail.infinispan.remote-cache-containers.KEY.socket-timeout
Enable or disable SO_TIMEOUT on socket connections to remote Hot Rod servers with the specified timeout, in milliseconds. A timeout of 0 is interpreted as an infinite timeout.
thorntail.infinispan.remote-cache-containers.KEY.tcp-keep-alive
Configures TCP Keepalive on the TCP stack.
thorntail.infinispan.remote-cache-containers.KEY.tcp-no-delay
Enable or disable TCP_NODELAY on socket connections to remote Hot Rod servers.
thorntail.infinispan.remote-cache-containers.KEY.value-size-estimate
This hint allows sizing of byte buffers when serializing and deserializing values, to minimize array resizing.

D.13. IO

Primarily an internal fraction supporting I/O activities for higher-level fractions.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>io</artifactId>
</dependency>

Configuration

thorntail.io.buffer-pools.KEY.buffer-size
The size of each buffer slice in bytes, if not set optimal value is calculated based on available RAM resources in your system.
thorntail.io.buffer-pools.KEY.buffers-per-slice
How many buffers per slice, if not set optimal value is calculated based on available RAM resources in your system.
thorntail.io.buffer-pools.KEY.direct-buffers
Does the buffer pool use direct buffers, some platforms don’t support direct buffers
thorntail.io.workers.KEY.busy-task-thread-count
An estimate of busy threads in the task worker thread pool
thorntail.io.workers.KEY.core-pool-size
Minimum number of threads to keep in the underlying thread pool even if they are idle. Threads over this limit will be terminated over time specified by task-keepalive attribute.
thorntail.io.workers.KEY.io-thread-count
I/O thread count
thorntail.io.workers.KEY.io-threads
Specify the number of I/O threads to create for the worker. If not specified, a default will be chosen, which is calculated by cpuCount * 2
thorntail.io.workers.KEY.max-pool-size
The maximum number of threads to allow in the thread pool. Depending on implementation, when this limit is reached, tasks which cannot be queued may be rejected.
thorntail.io.workers.KEY.outbound-bind-address.KEY.bind-address
The address to bind to when the destination address matches
thorntail.io.workers.KEY.outbound-bind-address.KEY.bind-port
The port number to bind to when the destination address matches
thorntail.io.workers.KEY.outbound-bind-address.KEY.match
The destination address range to match
thorntail.io.workers.KEY.queue-size
An estimate of the number of tasks in the worker queue.
thorntail.io.workers.KEY.servers.KEY.connection-count
Estimate of the current connection count
thorntail.io.workers.KEY.servers.KEY.connection-limit-high-water-mark
If the connection count hits this number, no new connections will be accepted until the count drops below the low-water mark.
thorntail.io.workers.KEY.servers.KEY.connection-limit-low-water-mark
If the connection count has previously hit the high water mark, once it drops back down below this count, connections will be accepted again.
thorntail.io.workers.KEY.shutdown-requested
True is shutdown of the pool was requested
thorntail.io.workers.KEY.stack-size
The stack size (in bytes) to attempt to use for worker threads.
thorntail.io.workers.KEY.task-core-threads
Specify the starting number of threads for the worker task thread pool.
thorntail.io.workers.KEY.task-keepalive
Specify the number of milliseconds to keep non-core task threads alive.
thorntail.io.workers.KEY.task-max-threads
Specify the maximum number of threads for the worker task thread pool.If not set, default value used which is calculated by formula cpuCount * 16,as long as MaxFileDescriptorCount jmx property allows that number, otherwise calculation takes max into account to adjust it accordingly.

D.14. Jaeger

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaeger</artifactId>
</dependency>

Configuration

thorntail.jaeger.agent-host
The hostname for communicating with agent via UDP
thorntail.jaeger.agent-port
The port for communicating with agent via UDP
thorntail.jaeger.enable-b3-header-propagation
Whether to enable propagation of B3 headers in the configured Tracer. By default this is false.
thorntail.jaeger.password
Password to send as part of "Basic" authentication to the endpoint
thorntail.jaeger.remote-reporter-http-endpoint
Remote Reporter HTTP endpoint for Jaeger collector, such as http://jaeger-collector.istio-system:14268/api/traces
thorntail.jaeger.reporter-flush-interval
The reporter’s flush interval (ms)
thorntail.jaeger.reporter-log-spans
Whether the reporter should also log the spans
thorntail.jaeger.reporter-max-queue-size
The reporter’s maximum queue size
thorntail.jaeger.sampler-manager-host
The host name and port when using the remote controlled sampler
thorntail.jaeger.sampler-parameter
The sampler parameter (number). Ex.: 1
thorntail.jaeger.sampler-type
The sampler type. Ex.: const
thorntail.jaeger.service-name
The service name. Required (via this parameter, system property or env var). Ex.: order-manager
thorntail.jaeger.user
Username to send as part of "Basic" authentication to the endpoint

D.15. JAX-RS

Provides support for building RESTful web services according to JSR-311.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs</artifactId>
</dependency>

Configuration

thorntail.deployment.KEY.jaxrs.application-path
Set the JAX-RS application path. If set, Thorntail will automatically generate a JAX-RS Application class and use this value as the @ApplicationPath

D.15.1. JAX-RS + CDI

An internal fraction providing integration between JAX-RS and CDI.

For more information, see the JAX-RS and CDI fraction documentation.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-cdi</artifactId>
</dependency>

D.15.2. JAX-RS + JAXB

Provides support within JAX-RS applications for the XML binding framework according to JSR-31 and JSR-222.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-jaxb</artifactId>
</dependency>

D.15.3. JAX-RS + JSON-B

Provides support within JAX-RS application for JSON Binding according to JSR-367.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-jsonb</artifactId>
</dependency>

D.15.4. JAX-RS + JSON-P

Provides support within JAX-RS application for JSON processing according to JSR-374.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-jsonp</artifactId>
</dependency>

D.15.5. JAX-RS + Multipart

Provides support within JAX-RS application for MIME multipart form processing.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-multipart</artifactId>
</dependency>

D.15.6. JAX-RS + Validator

Provides integration and support between JAX-RS applications and Hibernate Validator.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jaxrs-validator</artifactId>
</dependency>

D.16. JCA

Provides support for the Java Connector Architecture (JCA) according to JSR 322.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jca</artifactId>
</dependency>

Configuration

thorntail.jca.archive-validation.enabled
Specify whether archive validation is enabled
thorntail.jca.archive-validation.fail-on-error
Should an archive validation error report fail the deployment
thorntail.jca.archive-validation.fail-on-warn
Should an archive validation warning report fail the deployment
thorntail.jca.bean-validation.enabled
Specify whether bean validation is enabled
thorntail.jca.bootstrap-contexts.KEY.name
The name of the BootstrapContext
thorntail.jca.bootstrap-contexts.KEY.workmanager
The WorkManager instance for the BootstrapContext
thorntail.jca.cached-connection-manager.debug
Enable/disable debug information logging
thorntail.jca.cached-connection-manager.error
Enable/disable error information logging
thorntail.jca.cached-connection-manager.ignore-unknown-connections
Do not cache unknown connections
thorntail.jca.cached-connection-manager.install
Enable/disable the cached connection manager valve and interceptor
thorntail.jca.distributed-workmanagers.KEY.elytron-enabled
Enables Elytron security for this workmanager.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.allow-core-timeout
Whether core threads may time out.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.core-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.current-thread-count
The current number of threads in the pool.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.handoff-executor
An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.keepalive-time
Used to specify the amount of time that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.largest-thread-count
The largest number of threads that have ever simultaneously been in the pool.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.max-threads
The maximum thread pool size.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.name
The name of the thread pool.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.queue-length
The queue length.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.queue-size
The queue size.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.rejected-count
The number of tasks that have been passed to the handoff-executor (if one is specified) or discarded.
thorntail.jca.distributed-workmanagers.KEY.long-running-threads.KEY.thread-factory
Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.
thorntail.jca.distributed-workmanagers.KEY.name
The name of the DistributedWorkManager
thorntail.jca.distributed-workmanagers.KEY.policy
The policy decides when to redistribute a Work instance
thorntail.jca.distributed-workmanagers.KEY.policy-options
List of policy’s options key/value pairs
thorntail.jca.distributed-workmanagers.KEY.selector
The selector decides to which nodes in the network to redistribute the Work instance to
thorntail.jca.distributed-workmanagers.KEY.selector-options
List of selector’s options key/value pairs
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.allow-core-timeout
Whether core threads may time out.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.core-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.current-thread-count
The current number of threads in the pool.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.handoff-executor
An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.keepalive-time
Used to specify the amount of time that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.largest-thread-count
The largest number of threads that have ever simultaneously been in the pool.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.max-threads
The maximum thread pool size.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.name
The name of the thread pool.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.queue-length
The queue length.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.queue-size
The queue size.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.rejected-count
The number of tasks that have been passed to the handoff-executor (if one is specified) or discarded.
thorntail.jca.distributed-workmanagers.KEY.short-running-threads.KEY.thread-factory
Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.
thorntail.jca.tracer.enabled
Specify whether tracer is enabled
thorntail.jca.workmanagers.KEY.elytron-enabled
Enables Elytron security for this workmanager.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.allow-core-timeout
Whether core threads may time out.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.core-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.current-thread-count
The current number of threads in the pool.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.handoff-executor
An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.keepalive-time
Used to specify the amount of time that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.largest-thread-count
The largest number of threads that have ever simultaneously been in the pool.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.max-threads
The maximum thread pool size.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.name
The name of the thread pool.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.queue-length
The queue length.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.queue-size
The queue size.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.rejected-count
The number of tasks that have been passed to the handoff-executor (if one is specified) or discarded.
thorntail.jca.workmanagers.KEY.long-running-threads.KEY.thread-factory
Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.
thorntail.jca.workmanagers.KEY.name
The name of the WorkManager
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.allow-core-timeout
Whether core threads may time out.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.core-threads
The core thread pool size which is smaller than the maximum pool size. If undefined, the core thread pool size is the same as the maximum thread pool size.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.current-thread-count
The current number of threads in the pool.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.handoff-executor
An executor to delegate tasks to in the event that a task cannot be accepted. If not specified, tasks that cannot be accepted will be silently discarded.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.keepalive-time
Used to specify the amount of time that pool threads should be kept running when idle; if not specified, threads will run until the executor is shut down.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.largest-thread-count
The largest number of threads that have ever simultaneously been in the pool.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.max-threads
The maximum thread pool size.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.name
The name of the thread pool.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.queue-length
The queue length.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.queue-size
The queue size.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.rejected-count
The number of tasks that have been passed to the handoff-executor (if one is specified) or discarded.
thorntail.jca.workmanagers.KEY.short-running-threads.KEY.thread-factory
Specifies the name of a specific thread factory to use to create worker threads. If not defined an appropriate default thread factory will be used.

D.17. JMX

Provides support for Java Management Extensions (JMX) according to JSR-3.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jmx</artifactId>
</dependency>

Configuration

thorntail.jmx.audit-log-configuration.enabled
Whether audit logging is enabled.
thorntail.jmx.audit-log-configuration.log-boot
Whether operations should be logged on server boot.
thorntail.jmx.audit-log-configuration.log-read-only
Whether operations that do not modify the configuration or any runtime services should be logged.
thorntail.jmx.expression-expose-model.domain-name
The domain name to use for the 'expression' model controller JMX facade in the MBeanServer.
thorntail.jmx.jmx-remoting-connector.use-management-endpoint
If true the connector will use the management endpoint, otherwise it will use the remoting subsystem one
thorntail.jmx.non-core-mbean-sensitivity
Whether or not core MBeans, i.e. mbeans not coming from the model controller, should be considered sensitive.
thorntail.jmx.resolved-expose-model.domain-name
The domain name to use for the 'resolved' model controller JMX facade in the MBeanServer.
thorntail.jmx.resolved-expose-model.proper-property-format
If false, PROPERTY type attributes are represented as a DMR string, this is the legacy behaviour. If true, PROPERTY type attributes are represented by a composite type where the key is a string, and the value has the same type as the property in the underlying model.
thorntail.jmx.show-model
Alias for the existence of the 'resolved' model controller jmx facade. When writing, if set to 'true' it will add the 'resolved' model controller jmx facade resource with the default domain name.

D.18. JPA

Provides support for the Java Persistence API according to JSR-220.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jpa</artifactId>
</dependency>

Configuration

thorntail.jpa.default-datasource
The name of the default global datasource.
thorntail.jpa.default-extended-persistence-inheritance
Controls how JPA extended persistence context (XPC) inheritance is performed. 'DEEP' shares the extended persistence context at top bean level. 'SHALLOW' the extended persistece context is only shared with the parent bean (never with sibling beans).

D.19. JSF

Provides support for JavaServer Faces 2.3 according to JSR-372.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jsf</artifactId>
</dependency>

Configuration

thorntail.jsf.default-jsf-impl-slot
Default JSF implementation slot
thorntail.jsf.disallow-doctype-decl
Specifies whether or not DOCTYPE declarations in JSF deployments should be disallowed. This setting can be overridden at the deployment level.

D.20. JSON-B

Provides support for JSON Binding according to JSR-367.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jsonb</artifactId>
</dependency>

D.21. JSON-P

Provides support for JSON Processing according to JSR-353.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>jsonp</artifactId>
</dependency>

D.22. Keycloak

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>keycloak</artifactId>
</dependency>

Configuration

thorntail.keycloak.json.path
Path to Keycloak adapter configuration
thorntail.keycloak.multitenancy.paths
Map of the relative request paths to Keycloak adapter configuration locations
thorntail.keycloak.realms.KEY.allow-any-hostname
SSL Setting
thorntail.keycloak.realms.KEY.always-refresh-token
Refresh token on every single web request
thorntail.keycloak.realms.KEY.auth-server-url
Base URL of the Realm Auth Server
thorntail.keycloak.realms.KEY.auth-server-url-for-backend-requests
URL to use to make background calls to auth server
thorntail.keycloak.realms.KEY.autodetect-bearer-only
autodetect bearer-only requests
thorntail.keycloak.realms.KEY.client-key-password
n/a
thorntail.keycloak.realms.KEY.client-keystore
n/a
thorntail.keycloak.realms.KEY.client-keystore-password
n/a
thorntail.keycloak.realms.KEY.confidential-port
Specify the confidential port (SSL/TLS) used by the Realm Auth Server
thorntail.keycloak.realms.KEY.connection-pool-size
Connection pool size for the client used by the adapter
thorntail.keycloak.realms.KEY.cors-allowed-headers
CORS allowed headers
thorntail.keycloak.realms.KEY.cors-allowed-methods
CORS allowed methods
thorntail.keycloak.realms.KEY.cors-exposed-headers
CORS exposed headers
thorntail.keycloak.realms.KEY.cors-max-age
CORS max-age header
thorntail.keycloak.realms.KEY.disable-trust-manager
Adapter will not use a trust manager when making adapter HTTPS requests
thorntail.keycloak.realms.KEY.enable-cors
Enable Keycloak CORS support
thorntail.keycloak.realms.KEY.expose-token
Enable secure URL that exposes access token
thorntail.keycloak.realms.KEY.ignore-oauth-query-parameter
disable query parameter parsing for access_token
thorntail.keycloak.realms.KEY.principal-attribute
token attribute to use to set Principal name
thorntail.keycloak.realms.KEY.proxy-url
The URL for the HTTP proxy if one is used.
thorntail.keycloak.realms.KEY.realm-public-key
Public key of the realm
thorntail.keycloak.realms.KEY.register-node-at-startup
Cluster setting
thorntail.keycloak.realms.KEY.register-node-period
how often to re-register node
thorntail.keycloak.realms.KEY.ssl-required
Specify if SSL is required (valid values are all, external and none)
thorntail.keycloak.realms.KEY.token-store
cookie or session storage for auth session data
thorntail.keycloak.realms.KEY.truststore
Truststore used for adapter client HTTPS requests
thorntail.keycloak.realms.KEY.truststore-password
Password of the Truststore
thorntail.keycloak.realms.KEY.verify-token-audience
If true, then during bearer-only authentication, the adapter will verify if token contains this client name (resource) as an audience
thorntail.keycloak.secure-deployments.KEY.adapter-state-cookie-path
If set, defines the path used in cookies set by the adapter. Useful when deploying the application in the root context path.
thorntail.keycloak.secure-deployments.KEY.allow-any-hostname
SSL Setting
thorntail.keycloak.secure-deployments.KEY.always-refresh-token
Refresh token on every single web request
thorntail.keycloak.secure-deployments.KEY.auth-server-url
Base URL of the Realm Auth Server
thorntail.keycloak.secure-deployments.KEY.auth-server-url-for-backend-requests
URL to use to make background calls to auth server
thorntail.keycloak.secure-deployments.KEY.autodetect-bearer-only
autodetect bearer-only requests
thorntail.keycloak.secure-deployments.KEY.bearer-only
Bearer Token Auth only
thorntail.keycloak.secure-deployments.KEY.client-key-password
n/a
thorntail.keycloak.secure-deployments.KEY.client-keystore
n/a
thorntail.keycloak.secure-deployments.KEY.client-keystore-password
n/a
thorntail.keycloak.secure-deployments.KEY.confidential-port
Specify the confidential port (SSL/TLS) used by the Realm Auth Server
thorntail.keycloak.secure-deployments.KEY.connection-pool-size
Connection pool size for the client used by the adapter
thorntail.keycloak.secure-deployments.KEY.cors-allowed-headers
CORS allowed headers
thorntail.keycloak.secure-deployments.KEY.cors-allowed-methods
CORS allowed methods
thorntail.keycloak.secure-deployments.KEY.cors-exposed-headers
CORS exposed headers
thorntail.keycloak.secure-deployments.KEY.cors-max-age
CORS max-age header
thorntail.keycloak.secure-deployments.KEY.credentials.KEY.value
Credential value
thorntail.keycloak.secure-deployments.KEY.disable-trust-manager
Adapter will not use a trust manager when making adapter HTTPS requests
thorntail.keycloak.secure-deployments.KEY.enable-basic-auth
Enable Basic Authentication
thorntail.keycloak.secure-deployments.KEY.enable-cors
Enable Keycloak CORS support
thorntail.keycloak.secure-deployments.KEY.expose-token
Enable secure URL that exposes access token
thorntail.keycloak.secure-deployments.KEY.ignore-oauth-query-parameter
disable query parameter parsing for access_token
thorntail.keycloak.secure-deployments.KEY.min-time-between-jwks-requests
If adapter recognize token signed by unknown public key, it will try to download new public key from keycloak server. However it won’t try to download if already tried it in less than 'min-time-between-jwks-requests' seconds
thorntail.keycloak.secure-deployments.KEY.principal-attribute
token attribute to use to set Principal name
thorntail.keycloak.secure-deployments.KEY.proxy-url
The URL for the HTTP proxy if one is used.
thorntail.keycloak.secure-deployments.KEY.public-client
Public client
thorntail.keycloak.secure-deployments.KEY.public-key-cache-ttl
Maximum time the downloaded public keys are considered valid. When this time reach, the adapter is forced to download public keys from keycloak server
thorntail.keycloak.secure-deployments.KEY.realm
Keycloak realm
thorntail.keycloak.secure-deployments.KEY.realm-public-key
Public key of the realm
thorntail.keycloak.secure-deployments.KEY.redirect-rewrite-rules.KEY.value
redirect-rewrite-rule value
thorntail.keycloak.secure-deployments.KEY.register-node-at-startup
Cluster setting
thorntail.keycloak.secure-deployments.KEY.register-node-period
how often to re-register node
thorntail.keycloak.secure-deployments.KEY.resource
Application name
thorntail.keycloak.secure-deployments.KEY.ssl-required
Specify if SSL is required (valid values are all, external and none)
thorntail.keycloak.secure-deployments.KEY.token-minimum-time-to-live
The adapter will refresh the token if the current token is expired OR will expire in 'token-minimum-time-to-live' seconds or less
thorntail.keycloak.secure-deployments.KEY.token-store
cookie or session storage for auth session data
thorntail.keycloak.secure-deployments.KEY.truststore
Truststore used for adapter client HTTPS requests
thorntail.keycloak.secure-deployments.KEY.truststore-password
Password of the Truststore
thorntail.keycloak.secure-deployments.KEY.turn-off-change-session-id-on-login
The session id is changed by default on a successful login. Change this to true if you want to turn this off
thorntail.keycloak.secure-deployments.KEY.use-resource-role-mappings
Use resource level permissions from token
thorntail.keycloak.secure-deployments.KEY.verify-token-audience
If true, then during bearer-only authentication, the adapter will verify if token contains this client name (resource) as an audience
thorntail.keycloak.secure-servers.KEY.adapter-state-cookie-path
If set, defines the path used in cookies set by the adapter. Useful when deploying the application in the root context path.
thorntail.keycloak.secure-servers.KEY.allow-any-hostname
SSL Setting
thorntail.keycloak.secure-servers.KEY.always-refresh-token
Refresh token on every single web request
thorntail.keycloak.secure-servers.KEY.auth-server-url
Base URL of the Realm Auth Server
thorntail.keycloak.secure-servers.KEY.auth-server-url-for-backend-requests
URL to use to make background calls to auth server
thorntail.keycloak.secure-servers.KEY.autodetect-bearer-only
autodetect bearer-only requests
thorntail.keycloak.secure-servers.KEY.bearer-only
Bearer Token Auth only
thorntail.keycloak.secure-servers.KEY.client-key-password
n/a
thorntail.keycloak.secure-servers.KEY.client-keystore
n/a
thorntail.keycloak.secure-servers.KEY.client-keystore-password
n/a
thorntail.keycloak.secure-servers.KEY.confidential-port
Specify the confidential port (SSL/TLS) used by the Realm Auth Server
thorntail.keycloak.secure-servers.KEY.connection-pool-size
Connection pool size for the client used by the adapter
thorntail.keycloak.secure-servers.KEY.cors-allowed-headers
CORS allowed headers
thorntail.keycloak.secure-servers.KEY.cors-allowed-methods
CORS allowed methods
thorntail.keycloak.secure-servers.KEY.cors-exposed-headers
CORS exposed headers
thorntail.keycloak.secure-servers.KEY.cors-max-age
CORS max-age header
thorntail.keycloak.secure-servers.KEY.credentials.KEY.value
Credential value
thorntail.keycloak.secure-servers.KEY.disable-trust-manager
Adapter will not use a trust manager when making adapter HTTPS requests
thorntail.keycloak.secure-servers.KEY.enable-basic-auth
Enable Basic Authentication
thorntail.keycloak.secure-servers.KEY.enable-cors
Enable Keycloak CORS support
thorntail.keycloak.secure-servers.KEY.expose-token
Enable secure URL that exposes access token
thorntail.keycloak.secure-servers.KEY.ignore-oauth-query-parameter
disable query parameter parsing for access_token
thorntail.keycloak.secure-servers.KEY.min-time-between-jwks-requests
If adapter recognize token signed by unknown public key, it will try to download new public key from keycloak server. However it won’t try to download if already tried it in less than 'min-time-between-jwks-requests' seconds
thorntail.keycloak.secure-servers.KEY.principal-attribute
token attribute to use to set Principal name
thorntail.keycloak.secure-servers.KEY.proxy-url
The URL for the HTTP proxy if one is used.
thorntail.keycloak.secure-servers.KEY.public-client
Public client
thorntail.keycloak.secure-servers.KEY.public-key-cache-ttl
Maximum time the downloaded public keys are considered valid. When this time reach, the adapter is forced to download public keys from keycloak server
thorntail.keycloak.secure-servers.KEY.realm
Keycloak realm
thorntail.keycloak.secure-servers.KEY.realm-public-key
Public key of the realm
thorntail.keycloak.secure-servers.KEY.redirect-rewrite-rules.KEY.value
redirect-rewrite-rule value
thorntail.keycloak.secure-servers.KEY.register-node-at-startup
Cluster setting
thorntail.keycloak.secure-servers.KEY.register-node-period
how often to re-register node
thorntail.keycloak.secure-servers.KEY.resource
Application name
thorntail.keycloak.secure-servers.KEY.ssl-required
Specify if SSL is required (valid values are all, external and none)
thorntail.keycloak.secure-servers.KEY.token-minimum-time-to-live
The adapter will refresh the token if the current token is expired OR will expire in 'token-minimum-time-to-live' seconds or less
thorntail.keycloak.secure-servers.KEY.token-store
cookie or session storage for auth session data
thorntail.keycloak.secure-servers.KEY.truststore
Truststore used for adapter client HTTPS requests
thorntail.keycloak.secure-servers.KEY.truststore-password
Password of the Truststore
thorntail.keycloak.secure-servers.KEY.turn-off-change-session-id-on-login
The session id is changed by default on a successful login. Change this to true if you want to turn this off
thorntail.keycloak.secure-servers.KEY.use-resource-role-mappings
Use resource level permissions from token
thorntail.keycloak.secure-servers.KEY.verify-token-audience
If true, then during bearer-only authentication, the adapter will verify if token contains this client name (resource) as an audience

D.23. Logging

Provides facilities to configure logging categories, levels and handlers.

When specifying log-levels through properties, since they include dots, they should be placed between square brackets, such as thorntail.logging.loggers.[com.mycorp.logger].level.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>logging</artifactId>
</dependency>

Configuration

thorntail.logging.add-logging-api-dependencies
Indicates whether or not logging API dependencies should be added to deployments during the deployment process. A value of true will add the dependencies to the deployment. A value of false will skip the deployment from being processed for logging API dependencies.
thorntail.logging.async-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.async-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.async-handlers.KEY.level
The log level specifying which message levels will be logged by this handler. Message levels lower than this value will be discarded.
thorntail.logging.async-handlers.KEY.name
The name of the handler.
thorntail.logging.async-handlers.KEY.overflow-action
Specify what action to take when the overflowing. The valid options are 'block' and 'discard'
thorntail.logging.async-handlers.KEY.queue-length
The queue length to use before flushing writing
thorntail.logging.async-handlers.KEY.subhandlers
The Handlers associated with this async handler.
thorntail.logging.console-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.console-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.console-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.console-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.console-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.console-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.console-handlers.KEY.name
The name of the handler.
thorntail.logging.console-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.console-handlers.KEY.target
Defines the target of the console handler. The value can be System.out, System.err or console.
thorntail.logging.custom-formatters.KEY.attribute-class
The logging formatter class to be used.
thorntail.logging.custom-formatters.KEY.module
The module that the logging formatter depends on.
thorntail.logging.custom-formatters.KEY.properties
Defines the properties used for the logging formatter. All properties must be accessible via a setter method.
thorntail.logging.custom-handlers.KEY.attribute-class
The logging handler class to be used.
thorntail.logging.custom-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.custom-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.custom-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.custom-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.custom-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.custom-handlers.KEY.module
The module that the logging handler depends on.
thorntail.logging.custom-handlers.KEY.name
The name of the handler.
thorntail.logging.custom-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.custom-handlers.KEY.properties
Defines the properties used for the logging handler. All properties must be accessible via a setter method.
thorntail.logging.file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.file-handlers.KEY.name
The name of the handler.
thorntail.logging.file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.json-formatters.KEY.date-format
The date/time format pattern. The pattern must be a valid java.time.format.DateTimeFormatter.ofPattern() pattern. The default pattern is an ISO-8601 extended offset date-time format.
thorntail.logging.json-formatters.KEY.exception-output-type
Indicates how the cause of the logged message, if one is available, will be added to the JSON output.
thorntail.logging.json-formatters.KEY.key-overrides
Allows the names of the keys for the JSON properties to be overridden.
thorntail.logging.json-formatters.KEY.meta-data
Sets the meta data to use in the JSON format. Properties will be added to each log message.
thorntail.logging.json-formatters.KEY.pretty-print
Indicates whether or not pretty printing should be used when formatting.
thorntail.logging.json-formatters.KEY.print-details
Sets whether or not details should be printed. Printing the details can be expensive as the values are retrieved from the caller. The details include the source class name, source file name, source method name, source module name, source module version and source line number.
thorntail.logging.json-formatters.KEY.record-delimiter
The value to be used to indicate the end of a record. If set to null no delimiter will be used at the end of the record. The default value is a line feed.
thorntail.logging.json-formatters.KEY.zone-id
The zone ID for formatting the date and time. The system default is used if left undefined.
thorntail.logging.log-files.KEY.file-size
The size of the log file in bytes.
thorntail.logging.log-files.KEY.last-modified-time
The date, in milliseconds, the file was last modified.
thorntail.logging.log-files.KEY.last-modified-timestamp
The date, in ISO 8601 format, the file was last modified.
thorntail.logging.log-files.KEY.stream
Provides the server log as a response attachment. The response result value is the unique id of the attachment.
thorntail.logging.loggers.KEY.category
Specifies the category for the logger.
thorntail.logging.loggers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.loggers.KEY.handlers
The handlers associated with the logger.
thorntail.logging.loggers.KEY.level
The log level specifying which message levels will be logged by the logger. Message levels lower than this value will be discarded.
thorntail.logging.loggers.KEY.use-parent-handlers
Specifies whether or not this logger should send its output to its parent Logger.
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.level
The log level specifying which message levels will be logged by this handler. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.overflow-action
Specify what action to take when the overflowing. The valid options are 'block' and 'discard'
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.queue-length
The queue length to use before flushing writing
thorntail.logging.logging-profiles.KEY.async-handlers.KEY.subhandlers
The Handlers associated with this async handler.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.console-handlers.KEY.target
Defines the target of the console handler. The value can be System.out, System.err or console.
thorntail.logging.logging-profiles.KEY.custom-formatters.KEY.attribute-class
The logging formatter class to be used.
thorntail.logging.logging-profiles.KEY.custom-formatters.KEY.module
The module that the logging formatter depends on.
thorntail.logging.logging-profiles.KEY.custom-formatters.KEY.properties
Defines the properties used for the logging formatter. All properties must be accessible via a setter method.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.attribute-class
The logging handler class to be used.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.module
The module that the logging handler depends on.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.custom-handlers.KEY.properties
Defines the properties used for the logging handler. All properties must be accessible via a setter method.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.date-format
The date/time format pattern. The pattern must be a valid java.time.format.DateTimeFormatter.ofPattern() pattern. The default pattern is an ISO-8601 extended offset date-time format.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.exception-output-type
Indicates how the cause of the logged message, if one is available, will be added to the JSON output.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.key-overrides
Allows the names of the keys for the JSON properties to be overridden.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.meta-data
Sets the meta data to use in the JSON format. Properties will be added to each log message.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.pretty-print
Indicates whether or not pretty printing should be used when formatting.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.print-details
Sets whether or not details should be printed. Printing the details can be expensive as the values are retrieved from the caller. The details include the source class name, source file name, source method name, source module name, source module version and source line number.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.record-delimiter
The value to be used to indicate the end of a record. If set to null no delimiter will be used at the end of the record. The default value is a line feed.
thorntail.logging.logging-profiles.KEY.json-formatters.KEY.zone-id
The zone ID for formatting the date and time. The system default is used if left undefined.
thorntail.logging.logging-profiles.KEY.log-files.KEY.file-size
The size of the log file in bytes.
thorntail.logging.logging-profiles.KEY.log-files.KEY.last-modified-time
The date, in milliseconds, the file was last modified.
thorntail.logging.logging-profiles.KEY.log-files.KEY.last-modified-timestamp
The date, in ISO 8601 format, the file was last modified.
thorntail.logging.logging-profiles.KEY.log-files.KEY.stream
Provides the server log as a response attachment. The response result value is the unique id of the attachment.
thorntail.logging.logging-profiles.KEY.loggers.KEY.category
Specifies the category for the logger.
thorntail.logging.logging-profiles.KEY.loggers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.loggers.KEY.handlers
The handlers associated with the logger.
thorntail.logging.logging-profiles.KEY.loggers.KEY.level
The log level specifying which message levels will be logged by the logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.loggers.KEY.use-parent-handlers
Specifies whether or not this logger should send its output to its parent Logger.
thorntail.logging.logging-profiles.KEY.pattern-formatters.KEY.color-map
The color-map attribute allows for a comma delimited list of colors to be used for different levels with a pattern formatter. The format for the color mapping pattern is level-name:color-name.Valid Levels; severe, fatal, error, warn, warning, info, debug, trace, config, fine, finer, finest Valid Colors; black, green, red, yellow, blue, magenta, cyan, white, brightblack, brightred, brightgreen, brightblue, brightyellow, brightmagenta, brightcyan, brightwhite
thorntail.logging.logging-profiles.KEY.pattern-formatters.KEY.pattern
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.periodic-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The period of the rotation is automatically calculated based on the suffix.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.max-backup-index
The maximum number of backups to keep.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.rotate-on-boot
Indicates the file should be rotated each time the file attribute is changed. This always happens when at initialization time.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.rotate-size
The size at which to rotate the log file.
thorntail.logging.logging-profiles.KEY.periodic-size-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The period of the rotation is automatically calculated based on the suffix.
thorntail.logging.logging-profiles.KEY.root-logger.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.root-logger.handlers
The handlers associated with the root logger.
thorntail.logging.logging-profiles.KEY.root-logger.level
The log level specifying which message levels will be logged by the root logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.max-backup-index
The maximum number of backups to keep.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.rotate-on-boot
Indicates the file should be rotated each time the file attribute is changed. This always happens when at initialization time.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.rotate-size
The size at which to rotate the log file.
thorntail.logging.logging-profiles.KEY.size-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The suffix does not determine when the file should be rotated.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.block-on-reconnect
If set to true the write methods will block when attempting to reconnect. This is only advisable to be set to true if using an asynchronous handler.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.outbound-socket-binding-ref
Outbound socket reference for the socket connection.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.protocol
The protocol the socket should communicate over.
thorntail.logging.logging-profiles.KEY.socket-handlers.KEY.ssl-context
The reference to the defined SSL context. This is only used if the protocol is set to SSL_TCP.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.app-name
The app name used when formatting the message in RFC5424 format. By default the app name is "java".
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.facility
Facility as defined by RFC-5424 (http://tools.ietf.org/html/rfc5424)and RFC-3164 (http://tools.ietf.org/html/rfc3164).
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.hostname
The name of the host the messages are being sent from. For example the name of the host the application server is running on.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.port
The port the syslog server is listening on.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.server-address
The address of the syslog server.
thorntail.logging.logging-profiles.KEY.syslog-handlers.KEY.syslog-format
Formats the log message according to the RFC specification.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.date-format
The date/time format pattern. The pattern must be a valid java.time.format.DateTimeFormatter.ofPattern() pattern. The default pattern is an ISO-8601 extended offset date-time format.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.exception-output-type
Indicates how the cause of the logged message, if one is available, will be added to the XML output.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.key-overrides
Allows the names of the keys for the XML properties to be overridden.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.meta-data
Sets the meta data to use in the XML format. Properties will be added to each log message.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.namespace-uri
Sets the namespace URI used for each record if print-namespace attribute is true. Note that if no namespace-uri is defined and there are overridden keys no namespace will be written regardless if the print-namespace attribute is set to true.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.pretty-print
Indicates whether or not pretty printing should be used when formatting.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.print-details
Sets whether or not details should be printed. Printing the details can be expensive as the values are retrieved from the caller. The details include the source class name, source file name, source method name, source module name, source module version and source line number.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.print-namespace
Turns on or off the printing of the namespace for each <record/>. This is set to false by default.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.record-delimiter
The value to be used to indicate the end of a record. If set to null no delimiter will be used at the end of the record. The default value is a line feed.
thorntail.logging.logging-profiles.KEY.xml-formatters.KEY.zone-id
The zone ID for formatting the date and time. The system default is used if left undefined.
thorntail.logging.pattern-formatters.KEY.color-map
The color-map attribute allows for a comma delimited list of colors to be used for different levels with a pattern formatter. The format for the color mapping pattern is level-name:color-name.Valid Levels; severe, fatal, error, warn, warning, info, debug, trace, config, fine, finer, finest Valid Colors; black, green, red, yellow, blue, magenta, cyan, white, brightblack, brightred, brightgreen, brightblue, brightyellow, brightmagenta, brightcyan, brightwhite
thorntail.logging.pattern-formatters.KEY.pattern
Defines a pattern for the formatter.
thorntail.logging.periodic-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.periodic-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.periodic-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.periodic-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.periodic-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.periodic-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.periodic-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.periodic-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.periodic-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.periodic-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.periodic-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The period of the rotation is automatically calculated based on the suffix.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.periodic-size-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.max-backup-index
The maximum number of backups to keep.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.rotate-on-boot
Indicates the file should be rotated each time the file attribute is changed. This always happens when at initialization time.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.rotate-size
The size at which to rotate the log file.
thorntail.logging.periodic-size-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The period of the rotation is automatically calculated based on the suffix.
thorntail.logging.root-logger.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.root-logger.handlers
The handlers associated with the root logger.
thorntail.logging.root-logger.level
The log level specifying which message levels will be logged by the root logger. Message levels lower than this value will be discarded.
thorntail.logging.size-rotating-file-handlers.KEY.append
Specify whether to append to the target file.
thorntail.logging.size-rotating-file-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.size-rotating-file-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.size-rotating-file-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.size-rotating-file-handlers.KEY.file
The file description consisting of the path and optional relative to path.
thorntail.logging.size-rotating-file-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.size-rotating-file-handlers.KEY.formatter
Defines a pattern for the formatter.
thorntail.logging.size-rotating-file-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.size-rotating-file-handlers.KEY.max-backup-index
The maximum number of backups to keep.
thorntail.logging.size-rotating-file-handlers.KEY.name
The name of the handler.
thorntail.logging.size-rotating-file-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.size-rotating-file-handlers.KEY.rotate-on-boot
Indicates the file should be rotated each time the file attribute is changed. This always happens when at initialization time.
thorntail.logging.size-rotating-file-handlers.KEY.rotate-size
The size at which to rotate the log file.
thorntail.logging.size-rotating-file-handlers.KEY.suffix
Set the suffix string. The string is in a format which can be understood by java.text.SimpleDateFormat. The suffix does not determine when the file should be rotated.
thorntail.logging.socket-handlers.KEY.autoflush
Automatically flush after each write.
thorntail.logging.socket-handlers.KEY.block-on-reconnect
If set to true the write methods will block when attempting to reconnect. This is only advisable to be set to true if using an asynchronous handler.
thorntail.logging.socket-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.socket-handlers.KEY.encoding
The character encoding used by this Handler.
thorntail.logging.socket-handlers.KEY.filter-spec
A filter expression value to define a filter. Example for a filter that does not match a pattern: not(match("JBAS.*"))
thorntail.logging.socket-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.socket-handlers.KEY.named-formatter
The name of the defined formatter to be used on the handler.
thorntail.logging.socket-handlers.KEY.outbound-socket-binding-ref
Outbound socket reference for the socket connection.
thorntail.logging.socket-handlers.KEY.protocol
The protocol the socket should communicate over.
thorntail.logging.socket-handlers.KEY.ssl-context
The reference to the defined SSL context. This is only used if the protocol is set to SSL_TCP.
thorntail.logging.syslog-handlers.KEY.app-name
The app name used when formatting the message in RFC5424 format. By default the app name is "java".
thorntail.logging.syslog-handlers.KEY.enabled
If set to true the handler is enabled and functioning as normal, if set to false the handler is ignored when processing log messages.
thorntail.logging.syslog-handlers.KEY.facility
Facility as defined by RFC-5424 (http://tools.ietf.org/html/rfc5424)and RFC-3164 (http://tools.ietf.org/html/rfc3164).
thorntail.logging.syslog-handlers.KEY.hostname
The name of the host the messages are being sent from. For example the name of the host the application server is running on.
thorntail.logging.syslog-handlers.KEY.level
The log level specifying which message levels will be logged by this logger. Message levels lower than this value will be discarded.
thorntail.logging.syslog-handlers.KEY.port
The port the syslog server is listening on.
thorntail.logging.syslog-handlers.KEY.server-address
The address of the syslog server.
thorntail.logging.syslog-handlers.KEY.syslog-format
Formats the log message according to the RFC specification.
thorntail.logging.use-deployment-logging-config
Indicates whether or not deployments should use a logging configuration file found in the deployment to configure the log manager. If set to true and a logging configuration file was found in the deployments META-INF or WEB-INF/classes directory, then a log manager will be configured with those settings. If set false the servers logging configuration will be used regardless of any logging configuration files supplied in the deployment.
thorntail.logging.xml-formatters.KEY.date-format
The date/time format pattern. The pattern must be a valid java.time.format.DateTimeFormatter.ofPattern() pattern. The default pattern is an ISO-8601 extended offset date-time format.
thorntail.logging.xml-formatters.KEY.exception-output-type
Indicates how the cause of the logged message, if one is available, will be added to the XML output.
thorntail.logging.xml-formatters.KEY.key-overrides
Allows the names of the keys for the XML properties to be overridden.
thorntail.logging.xml-formatters.KEY.meta-data
Sets the meta data to use in the XML format. Properties will be added to each log message.
thorntail.logging.xml-formatters.KEY.namespace-uri
Sets the namespace URI used for each record if print-namespace attribute is true. Note that if no namespace-uri is defined and there are overridden keys no namespace will be written regardless if the print-namespace attribute is set to true.
thorntail.logging.xml-formatters.KEY.pretty-print
Indicates whether or not pretty printing should be used when formatting.
thorntail.logging.xml-formatters.KEY.print-details
Sets whether or not details should be printed. Printing the details can be expensive as the values are retrieved from the caller. The details include the source class name, source file name, source method name, source module name, source module version and source line number.
thorntail.logging.xml-formatters.KEY.print-namespace
Turns on or off the printing of the namespace for each <record/>. This is set to false by default.
thorntail.logging.xml-formatters.KEY.record-delimiter
The value to be used to indicate the end of a record. If set to null no delimiter will be used at the end of the record. The default value is a line feed.
thorntail.logging.xml-formatters.KEY.zone-id
The zone ID for formatting the date and time. The system default is used if left undefined.

D.24. Management

Provides the JBoss EAP management API.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>management</artifactId>
</dependency>

Configuration

thorntail.management.audit-access.audit-log-logger.enabled
Whether audit logging is enabled.
thorntail.management.audit-access.audit-log-logger.log-boot
Whether operations should be logged on server boot.
thorntail.management.audit-access.audit-log-logger.log-read-only
Whether operations that do not modify the configuration or any runtime services should be logged.
thorntail.management.audit-access.file-handlers.KEY.disabled-due-to-failure
Whether this handler has been disabled due to logging failures.
thorntail.management.audit-access.file-handlers.KEY.failure-count
The number of logging failures since the handler was initialized.
thorntail.management.audit-access.file-handlers.KEY.formatter
The formatter used to format the log messages.
thorntail.management.audit-access.file-handlers.KEY.max-failure-count
The maximum number of logging failures before disabling this handler.
thorntail.management.audit-access.file-handlers.KEY.path
The path of the audit log file.
thorntail.management.audit-access.file-handlers.KEY.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.audit-access.file-handlers.KEY.rotate-at-startup
Whether the old log file should be rotated at server startup.
thorntail.management.audit-access.in-memory-handlers.KEY.max-history
The maximum number of operation stored in history for this handler.
thorntail.management.audit-access.json-formatters.KEY.compact
If true will format the JSON on one line. There may still be values containing new lines, so if having the whole record on one line is important, set escape-new-line or escape-control-characters to true.
thorntail.management.audit-access.json-formatters.KEY.date-format
The date format to use as understood by java.text.SimpleDateFormat. Will be ignored if include-date="false".
thorntail.management.audit-access.json-formatters.KEY.date-separator
The separator between the date and the rest of the formatted log message. Will be ignored if include-date="false".
thorntail.management.audit-access.json-formatters.KEY.escape-control-characters
If true will escape all control characters (ascii entries with a decimal value < 32) with the ascii code in octal, e.g.' becomes '#012'. If this is true, it will override escape-new-line="false".
thorntail.management.audit-access.json-formatters.KEY.escape-new-line
If true will escape all new lines with the ascii code in octal, e.g. "#012".
thorntail.management.audit-access.json-formatters.KEY.include-date
Whether or not to include the date in the formatted log record.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.disabled-due-to-failure
Whether this handler has been disabled due to logging failures.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.failure-count
The number of logging failures since the handler was initialized.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.formatter
The formatter used to format the log messages.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.max-failure-count
The maximum number of logging failures before disabling this handler.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.path
The path of the audit log file.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.audit-access.periodic-rotating-file-handlers.KEY.suffix
The suffix string in a format which can be understood by java.text.SimpleDateFormat. The period of the rotation is automatically calculated based on the suffix.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.disabled-due-to-failure
Whether this handler has been disabled due to logging failures.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.failure-count
The number of logging failures since the handler was initialized.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.formatter
The formatter used to format the log messages.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.max-backup-index
The maximum number of backups to keep.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.max-failure-count
The maximum number of logging failures before disabling this handler.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.path
The path of the audit log file.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.audit-access.size-rotating-file-handlers.KEY.rotate-size
The size at which to rotate the log file.
thorntail.management.audit-access.syslog-handlers.KEY.app-name
The application name to add to the syslog records as defined in section 6.2.5 of RFC-5424. If not specified it will default to the name of the product.
thorntail.management.audit-access.syslog-handlers.KEY.disabled-due-to-failure
Whether this handler has been disabled due to logging failures.
thorntail.management.audit-access.syslog-handlers.KEY.facility
The facility to use for syslog logging as defined in section 6.2.1 of RFC-5424, and section 4.1.1 of RFC-3164.
thorntail.management.audit-access.syslog-handlers.KEY.failure-count
The number of logging failures since the handler was initialized.
thorntail.management.audit-access.syslog-handlers.KEY.formatter
The formatter used to format the log messages.
thorntail.management.audit-access.syslog-handlers.KEY.max-failure-count
The maximum number of logging failures before disabling this handler.
thorntail.management.audit-access.syslog-handlers.KEY.max-length
The maximum length in bytes a log message, including the header, is allowed to be. If undefined, it will default to 1024 bytes if the syslog-format is RFC3164, or 2048 bytes if the syslog-format is RFC5424.
thorntail.management.audit-access.syslog-handlers.KEY.syslog-format
Whether to set the syslog format to the one specified in RFC-5424 or RFC-3164.
thorntail.management.audit-access.syslog-handlers.KEY.tcp-protocol.host
The host of the syslog server for the tcp requests.
thorntail.management.audit-access.syslog-handlers.KEY.tcp-protocol.message-transfer
The message transfer setting as described in section 3.4 of RFC-6587. This can either be OCTET_COUNTING as described in section 3.4.1 of RFC-6587, or NON_TRANSPARENT_FRAMING as described in section 3.4.1 of RFC-6587. See your syslog provider’s documentation for what is supported.
thorntail.management.audit-access.syslog-handlers.KEY.tcp-protocol.port
The port of the syslog server for the tcp requests.
thorntail.management.audit-access.syslog-handlers.KEY.tcp-protocol.reconnect-timeout
If a connection drop is detected, the number of seconds to wait before reconnecting. A negative number means don’t reconnect automatically.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.key-password
The password for the keystore key.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.key-password-credential-reference
The reference to credential for the keystore key stored in CredentialStore under defined alias or clear text password.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.keystore-password
The password for the keystore.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.keystore-password-credential-reference
The reference to credential for the keystore password stored in CredentialStore under defined alias or clear text password.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.keystore-path
The path of the keystore.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.client-certificate-store-authentication.keystore-relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'keystore-relative-to' is provided, the value of the 'keystore-path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.host
The host of the syslog server for the tls over tcp requests.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.message-transfer
The message transfer setting as described in section 3.4 of RFC-6587. This can either be OCTET_COUNTING as described in section 3.4.1 of RFC-6587, or NON_TRANSPARENT_FRAMING as described in section 3.4.1 of RFC-6587. See your syslog provider’s documentation for what is supported.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.port
The port of the syslog server for the tls over tcp requests.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.reconnect-timeout
If a connection drop is detected, the number of seconds to wait before reconnecting. A negative number means don’t reconnect automatically.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.truststore-authentication.keystore-password
The password for the truststore.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.truststore-authentication.keystore-password-credential-reference
The reference to credential for the truststore password stored in CredentialStore under defined alias or clear text password.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.truststore-authentication.keystore-path
The path of the truststore.
thorntail.management.audit-access.syslog-handlers.KEY.tls-protocol.truststore-authentication.keystore-relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'keystore-relative-to' is provided, the value of the 'keystore-path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.audit-access.syslog-handlers.KEY.truncate
Whether or not a message, including the header, should truncate the message if the length in bytes is greater than the maximum length. If set to false messages will be split and sent with the same header values.
thorntail.management.audit-access.syslog-handlers.KEY.udp-protocol.host
The host of the syslog server for the udp requests.
thorntail.management.audit-access.syslog-handlers.KEY.udp-protocol.port
The port of the syslog server for the udp requests.
thorntail.management.authorization-access.all-role-names
The official names of all roles supported by the current management access control provider. This includes any standard roles as well as any user-defined roles.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.address
Address pattern describing a resource or resources to which the constraint applies.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.attributes
List of the names of attributes to which the constraint specifically applies.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.entire-resource
True if the constraint applies to the resource as a whole; false if it only applies to one or more attributes or operations.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.operations
List of the names of operations to which the constraint specifically applies.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.configured-application
Set to override the default as to whether the constraint is considered an application resource.
thorntail.management.authorization-access.application-classification-constraint.types.KEY.classifications.KEY.default-application
Whether targets having this application type constraint are considered application resources.
thorntail.management.authorization-access.permission-combination-policy
The policy for combining access control permissions when the authorization policy grants the user more than one type of permission for a given action. In the standard role based authorization policy, this would occur when a user maps to multiple roles. The 'permissive' policy means if any of the permissions allow the action, the action is allowed. The 'rejecting' policy means the existence of multiple permissions should result in an error.
thorntail.management.authorization-access.provider
The provider to use for management access control decisions.
thorntail.management.authorization-access.role-mappings.KEY.excludes.KEY.name
The name of the user or group being mapped.
thorntail.management.authorization-access.role-mappings.KEY.excludes.KEY.realm
An optional attribute to map based on the realm used for authentication.
thorntail.management.authorization-access.role-mappings.KEY.excludes.KEY.type
The type of the Principal being mapped, either 'group' or 'user'.
thorntail.management.authorization-access.role-mappings.KEY.include-all
Configure if all authenticated users should be automatically assigned this role.
thorntail.management.authorization-access.role-mappings.KEY.includes.KEY.name
The name of the user or group being mapped.
thorntail.management.authorization-access.role-mappings.KEY.includes.KEY.realm
An optional attribute to map based on the realm used for authentication.
thorntail.management.authorization-access.role-mappings.KEY.includes.KEY.type
The type of the Principal being mapped, either 'group' or 'user'.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.address
Address pattern describing a resource or resources to which the constraint applies.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.attributes
List of the names of attributes to which the constraint specifically applies.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.entire-resource
True if the constraint applies to the resource as a whole; false if it only applies to one or more attributes or operations.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.applies-tos.KEY.operations
List of the names of operations to which the constraint specifically applies.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.configured-application
Set to override the default as to whether the constraint is considered an application resource.
thorntail.management.authorization-access.sensitivity-classification-constraint.types.KEY.classifications.KEY.default-application
Whether targets having this application type constraint are considered application resources.
thorntail.management.authorization-access.standard-role-names
The official names of the standard roles supported by the current management access control provider.
thorntail.management.authorization-access.use-identity-roles
Should the raw roles obtained from the underlying security identity be used directly?
thorntail.management.authorization-access.vault-expression-constraint.configured-requires-read
Set to override the default as to whether reading attributes containing vault expressions should be considered sensitive.
thorntail.management.authorization-access.vault-expression-constraint.configured-requires-write
Set to override the default as to whether writing attributes containing vault expressions should be considered sensitive.
thorntail.management.authorization-access.vault-expression-constraint.default-requires-read
Whether reading attributes containing vault expressions should be considered sensitive.
thorntail.management.authorization-access.vault-expression-constraint.default-requires-write
Whether writing attributes containing vault expressions should be considered sensitive.
thorntail.management.bind.interface
Interface to bind for the management ports
thorntail.management.configuration-changes-service.max-history
The maximum number of configuration changes stored in history.
thorntail.management.http-interface-management-interface.allowed-origins
Comma separated list of trusted Origins for sending Cross-Origin Resource Sharing requests on the management API once the user is authenticated.
thorntail.management.http-interface-management-interface.console-enabled
Flag that indicates admin console is enabled
thorntail.management.http-interface-management-interface.http-authentication-factory
The authentication policy to use to secure the interface for normal HTTP requests.
thorntail.management.http-interface-management-interface.http-upgrade
HTTP Upgrade specific configuration
thorntail.management.http-interface-management-interface.http-upgrade-enabled
Flag that indicates HTTP Upgrade is enabled, which allows HTTP requests to be upgraded to native remoting connections
thorntail.management.http-interface-management-interface.sasl-protocol
The name of the protocol to be passed to the SASL mechanisms used for authentication.
thorntail.management.http-interface-management-interface.secure-socket-binding
The name of the socket binding configuration to use for the HTTPS management interface’s socket. When defined at least one of ssl-context or security-realm must also be defined.
thorntail.management.http-interface-management-interface.security-realm
The legacy security realm to use for the HTTP management interface.
thorntail.management.http-interface-management-interface.server-name
The name of the server used in the initial Remoting exchange and within the SASL mechanisms.
thorntail.management.http-interface-management-interface.socket-binding
The name of the socket binding configuration to use for the HTTP management interface’s socket.
thorntail.management.http-interface-management-interface.ssl-context
Reference to the SSLContext to use for this management interface.
thorntail.management.http.disable
Flag to disable HTTP access to management interface
thorntail.management.http.port
Port for HTTP access to management interface
thorntail.management.https.port
Port for HTTPS access to management interface
thorntail.management.identity-access.security-domain
Reference to the security domain to use to obtain the current identity performing a management request.
thorntail.management.ldap-connections.KEY.always-send-client-cert
If true, the client SSL certificate will be sent to LDAP server with every request; otherwise the client SSL certificate will not be sent when verifying the user credentials
thorntail.management.ldap-connections.KEY.handles-referrals-for
List of URLs that this connection handles referrals for.
thorntail.management.ldap-connections.KEY.initial-context-factory
The initial context factory to establish the LdapContext.
thorntail.management.ldap-connections.KEY.properties.KEY.value
The optional value of the property.
thorntail.management.ldap-connections.KEY.referrals
The referral handling mode for this connection.
thorntail.management.ldap-connections.KEY.search-credential
The credential to use when connecting to perform a search.
thorntail.management.ldap-connections.KEY.search-credential-reference
The reference to the search credential stored in CredentialStore under defined alias or clear text password.
thorntail.management.ldap-connections.KEY.search-dn
The distinguished name to use when connecting to the LDAP server to perform searches.
thorntail.management.ldap-connections.KEY.security-realm
The security realm to reference to obtain a configured SSLContext to use when establishing the connection.
thorntail.management.ldap-connections.KEY.url
The URL to use to connect to the LDAP server.
thorntail.management.management-operations-service.active-operations.KEY.access-mechanism
The mechanism used to submit a request to the server.
thorntail.management.management-operations-service.active-operations.KEY.address
The address of the resource targeted by the operation. The value in the final element of the address will be '<hidden>' if the caller is not authorized to address the operation’s target resource.
thorntail.management.management-operations-service.active-operations.KEY.caller-thread
The name of the thread that is executing the operation.
thorntail.management.management-operations-service.active-operations.KEY.cancelled
Whether the operation has been cancelled.
thorntail.management.management-operations-service.active-operations.KEY.domain-rollout
True if the operation is a subsidiary request on a domain process other than the one directly handling the original operation, executing locally as part of the rollout of the original operation across the domain.
thorntail.management.management-operations-service.active-operations.KEY.domain-uuid
Identifier of an overall multi-process domain operation of which this operation is a part, or undefined if this operation is not associated with such a domain operation.
thorntail.management.management-operations-service.active-operations.KEY.exclusive-running-time
Amount of time the operation has been executing with the exclusive operation execution lock held, or -1 if the operation does not hold the exclusive execution lock.
thorntail.management.management-operations-service.active-operations.KEY.execution-status
The current activity of the operation.
thorntail.management.management-operations-service.active-operations.KEY.operation
The name of the operation, or '<hidden>' if the caller is not authorized to address the operation’s target resource.
thorntail.management.management-operations-service.active-operations.KEY.running-time
Amount of time the operation has been executing.
thorntail.management.native-interface-management-interface.sasl-authentication-factory
The SASL authentication policy to use to secure this interface.
thorntail.management.native-interface-management-interface.sasl-protocol
The name of the protocol to be passed to the SASL mechanisms used for authentication.
thorntail.management.native-interface-management-interface.security-realm
The legacy security realm to use for the native management interface.
thorntail.management.native-interface-management-interface.server-name
The name of the server used in the initial Remoting exchange and within the SASL mechanisms.
thorntail.management.native-interface-management-interface.socket-binding
The name of the socket binding configuration to use for the native management interface’s socket.
thorntail.management.native-interface-management-interface.ssl-context
Reference to the SSLContext to use for this management interface.
thorntail.management.security-realms.KEY.jaas-authentication.assign-groups
Map the roles loaded by JAAS to groups.
thorntail.management.security-realms.KEY.jaas-authentication.name
The name of the JAAS configuration to use.
thorntail.management.security-realms.KEY.kerberos-authentication.remove-realm
After authentication should the realm name be stripped from the users name.
thorntail.management.security-realms.KEY.kerberos-server-identity.keytabs.KEY.debug
Should additional debug logging be enabled during TGT acquisition?
thorntail.management.security-realms.KEY.kerberos-server-identity.keytabs.KEY.for-hosts
A server can be accessed using different host names, this attribute specifies which host names this keytab can be used with.
thorntail.management.security-realms.KEY.kerberos-server-identity.keytabs.KEY.path
The path to the keytab.
thorntail.management.security-realms.KEY.kerberos-server-identity.keytabs.KEY.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.security-realms.KEY.ldap-authentication.advanced-filter
The fully defined filter to be used to search for the user based on their entered user ID. The filter should contain a variable in the form {0} - this will be replaced with the username supplied by the user.
thorntail.management.security-realms.KEY.ldap-authentication.allow-empty-passwords
Should empty passwords be accepted from the user being authenticated.
thorntail.management.security-realms.KEY.ldap-authentication.base-dn
The base distinguished name to commence the search for the user.
thorntail.management.security-realms.KEY.ldap-authentication.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authentication.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authentication.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authentication.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authentication.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authentication.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authentication.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authentication.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authentication.connection
The name of the connection to use to connect to LDAP.
thorntail.management.security-realms.KEY.ldap-authentication.recursive
Whether the search should be recursive.
thorntail.management.security-realms.KEY.ldap-authentication.user-dn
The name of the attribute which is the user’s distinguished name.
thorntail.management.security-realms.KEY.ldap-authentication.username-attribute
The name of the attribute to search for the user. This filter will then perform a simple search where the username entered by the user matches the attribute specified here.
thorntail.management.security-realms.KEY.ldap-authentication.username-load
The name of the attribute that should be loaded from the authenticated users LDAP entry to replace the username that they supplied, e.g. convert an e-mail address to an ID or correct the case entered.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.base-dn
The starting point of the search for the user.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.filter
The filter to use for the LDAP search.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.force
Authentication may have already converted the username to a distinguished name, force this to occur again before loading groups.
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.recursive
Should levels below the starting point be recursively searched?
thorntail.management.security-realms.KEY.ldap-authorization.advanced-filter-username-to-dn.user-dn-attribute
The attribute on the user entry that contains their distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.connection
The name of the connection to use to connect to LDAP.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.base-dn
The starting point of the search for the group.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.group-dn-attribute
Which attribute on a group entry is it’s distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.group-name
An enumeration to identify if groups should be referenced using a simple name or their distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.group-name-attribute
Which attribute on a group entry is it’s simple name.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.iterative
Should further searches be performed to identify groups that the groups identified are a member of?
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.prefer-original-connection
After following a referral should subsequent searches prefer the original connection or use the connection of the last referral.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.principal-attribute
The attribute on the group entry that references the principal.
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.recursive
Should levels below the starting point be recursively searched?
thorntail.management.security-realms.KEY.ldap-authorization.group-to-principal-group-search.search-by
Should searches be performed using simple names or distinguished names?
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.group-attribute
The attribute on the principal which references the group the principal is a member of.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.group-dn-attribute
Which attribute on a group entry is it’s distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.group-name
An enumeration to identify if groups should be referenced using a simple name or their distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.group-name-attribute
Which attribute on a group entry is it’s simple name.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.iterative
Should further searches be performed to identify groups that the groups identified are a member of?
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.parse-group-name-from-dn
Should the group name be extracted from the distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.prefer-original-connection
After following a referral should subsequent searches prefer the original connection or use the connection of the last referral.
thorntail.management.security-realms.KEY.ldap-authorization.principal-to-group-group-search.skip-missing-groups
If a non-existent group is referenced should it be quietly ignored.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.attribute
The attribute on the user entry that is their username.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.base-dn
The starting point of the search for the user.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.force
Authentication may have already converted the username to a distinguished name, force this to occur again before loading groups.
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.recursive
Should levels below the starting point be recursively searched?
thorntail.management.security-realms.KEY.ldap-authorization.username-filter-username-to-dn.user-dn-attribute
The attribute on the user entry that contains their distinguished name.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-access-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-access-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-access-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-access-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-search-time-cache.cache-failures
Should failures be cached?
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-search-time-cache.cache-size
The current size of the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-search-time-cache.eviction-time
The time in seconds until an entry should be evicted from the cache.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.by-search-time-cache.max-cache-size
The maximum size of the cache before the oldest items are removed to make room for new entries.
thorntail.management.security-realms.KEY.ldap-authorization.username-is-dn-username-to-dn.force
Authentication may have already converted the username to a distinguished name, force this to occur again before loading groups.
thorntail.management.security-realms.KEY.local-authentication.allowed-users
The comma separated list of users that will be accepted using the JBOSS-LOCAL-USER mechanism or '*' to accept all. If specified the default-user is always assumed allowed.
thorntail.management.security-realms.KEY.local-authentication.default-user
The name of the default user to assume if no user specified by the remote client.
thorntail.management.security-realms.KEY.local-authentication.skip-group-loading
Disable the loading of the users group membership information after local authentication has been used.
thorntail.management.security-realms.KEY.map-groups-to-roles
After a users group membership has been loaded should a 1:1 relationship be assumed regarding group to role mapping.
thorntail.management.security-realms.KEY.plug-in-authentication.mechanism
Allow the mechanism this plug-in is compatible with to be overridden from DIGEST.
thorntail.management.security-realms.KEY.plug-in-authentication.name
The short name of the plug-in (as registered) to use.
thorntail.management.security-realms.KEY.plug-in-authentication.properties.KEY.value
The optional value of the property.
thorntail.management.security-realms.KEY.plug-in-authorization.name
The short name of the plug-in (as registered) to use.
thorntail.management.security-realms.KEY.plug-in-authorization.properties.KEY.value
The optional value of the property.
thorntail.management.security-realms.KEY.properties-authentication.path
The path of the properties file containing the users.
thorntail.management.security-realms.KEY.properties-authentication.plain-text
Are the credentials within the properties file stored in plain text. If not the credential is expected to be the hex encoded Digest hash of 'username : realm : password'.
thorntail.management.security-realms.KEY.properties-authentication.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.security-realms.KEY.properties-authorization.path
The path of the properties file containing the users roles.
thorntail.management.security-realms.KEY.properties-authorization.relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.security-realms.KEY.secret-server-identity.credential-reference
The reference to credential for the secret / password stored in CredentialStore under defined alias or clear text password.
thorntail.management.security-realms.KEY.secret-server-identity.value
The secret / password - Base64 Encoded.
thorntail.management.security-realms.KEY.ssl-server-identity.alias
The alias of the entry to use from the keystore.
thorntail.management.security-realms.KEY.ssl-server-identity.enabled-cipher-suites
The cipher suites that can be enabled on the underlying SSLEngine.
thorntail.management.security-realms.KEY.ssl-server-identity.enabled-protocols
The protocols that can be enabled on the underlying SSLEngine.
thorntail.management.security-realms.KEY.ssl-server-identity.generate-self-signed-certificate-host
If the keystore does not exist and this attribute is set then a self signed certificate will be generated for the specified host name. This is not intended for production use.
thorntail.management.security-realms.KEY.ssl-server-identity.key-password
The password to obtain the key from the keystore.
thorntail.management.security-realms.KEY.ssl-server-identity.key-password-credential-reference
The reference to credential for the keystore key stored in CredentialStore under defined alias or clear text password.
thorntail.management.security-realms.KEY.ssl-server-identity.keystore-password
The password to open the keystore.
thorntail.management.security-realms.KEY.ssl-server-identity.keystore-password-credential-reference
The reference to credential for the keystore password stored in CredentialStore under defined alias or clear text password.
thorntail.management.security-realms.KEY.ssl-server-identity.keystore-path
The path of the keystore, will be ignored if the keystore-provider is anything other than JKS.
thorntail.management.security-realms.KEY.ssl-server-identity.keystore-provider
The provider for loading the keystore, defaults to JKS.
thorntail.management.security-realms.KEY.ssl-server-identity.keystore-relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.security-realms.KEY.ssl-server-identity.protocol
The protocol to use when creating the SSLContext.
thorntail.management.security-realms.KEY.truststore-authentication.keystore-password
The password to open the keystore.
thorntail.management.security-realms.KEY.truststore-authentication.keystore-password-credential-reference
The reference to credential for the keystore password stored in CredentialStore under defined alias or clear text password.
thorntail.management.security-realms.KEY.truststore-authentication.keystore-path
The path of the keystore, will be ignored if the keystore-provider is anything other than JKS.
thorntail.management.security-realms.KEY.truststore-authentication.keystore-provider
The provider for loading the keystore, defaults to JKS.
thorntail.management.security-realms.KEY.truststore-authentication.keystore-relative-to
The name of another previously named path, or of one of the standard paths provided by the system. If 'relative-to' is provided, the value of the 'path' attribute is treated as relative to the path specified by this attribute.
thorntail.management.security-realms.KEY.users-authentication.users.KEY.credential-reference
The reference to credential for the password stored in CredentialStore under defined alias or clear text password.
thorntail.management.security-realms.KEY.users-authentication.users.KEY.password
The user’s password.

D.25. MicroProfile

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile</artifactId>
</dependency>

D.25.1. MicroProfile Config

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-config</artifactId>
</dependency>

Configuration

thorntail.microprofile.config.config-source-providers.KEY.attribute-class
Class of the ConfigSourceProvider to load
thorntail.microprofile.config.config-sources.KEY.attribute-class
Class of the config source to load
thorntail.microprofile.config.config-sources.KEY.dir
Directory that is scanned to config properties for this config source (file names are key, file content are value)
thorntail.microprofile.config.config-sources.KEY.ordinal
Ordinal value for the config source
thorntail.microprofile.config.config-sources.KEY.properties
Properties configured for this config source

D.25.2. MicroProfile Fault Tolerance

This fraction implements the Eclipse MicroProfile Fault Tolerance API. The implementation depends on the Hystrix fraction, which is added transitively into your application. Use standard configuration mechanisms to configure Hystrix properties in your application.

D.25.2.1. Bulkhead fallback rejection

If you use the @Bulkhead pattern together with some @Fallback logic to limit the number of concurrent requests, an invocation may still result in an exception.

D.25.2.1.1. Semaphore Isolation

For semaphore-style @Bulkhead a BulkheadException may be thrown if the maximum concurrent limit is reached. To avoid that, set the thorntail.hystrix.command.default.fallback.isolation.semaphore.maxConcurrentRequests property to increase the limit.

D.25.2.1.2. Thread Isolation

For @Bulkhead used together with @Asynchronous a RejectedExecutionException may be thrown if the maximum concurrent limit is reached. To avoid that, set the thorntail.hystrix.threadpool.default.maximumSize property to increase the limit. Also don’t forget to set the thorntail.hystrix.threadpool.default.allowMaximumSizeToDivergeFromCoreSize property to true.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-fault-tolerance</artifactId>
</dependency>

Configuration

thorntail.microprofile.fault-tolerance.synchronous-circuit-breaker
Enable/disable synchronous circuit breaker functionality. If disabled, CircuitBreaker#successThreshold() of value greater than 1 is not supported and CircuitBreaker#failOn() configuration is ignored. Moreover, circuit breaker does not necessarily transition from CLOSED to OPEN immediately when a fault tolerance operation completes. However, applications are encouraged to disable this feature on high-volume circuits.

D.25.3. MicroProfile Health

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-health</artifactId>
</dependency>

Configuration

thorntail.microprofile.health.security-realm
Security realm configuration

D.25.4. MicroProfile JWT RBAC Auth

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-jwt</artifactId>
</dependency>

Configuration

thorntail.microprofile.jwt.default-missing-method-permissions-deny-access
If a JAX-RS resource has no class-level security metadata, then if this property is set to true and at least one resource method has security metadata all other resource methods without security metadata have an implicit @DenyAll, otherwise resource methods without security metadata are not secured
thorntail.microprofile.jwt.token.exp-grace-period
The JWT token expiration grace period in seconds
thorntail.microprofile.jwt.token.issued-by
The URI of the JWT token issuer
thorntail.microprofile.jwt.token.jwks-refresh-interval
The interval at which the JWKS URI should be queried for keys (in minutes).
thorntail.microprofile.jwt.token.jwks-uri
The JWKS URI from which to load public keys (if 'signer-pub-key' is set, this setting is ignored).
thorntail.microprofile.jwt.token.signer-pub-key
The public key of the JWT token signer. Can be prefixed 'file:' or 'classpath:' for key assets, otherwise the key contents are expected

D.25.5. MicroProfile Metrics

This fraction implements the MicroProfile Metrics 1.0 specification.

To use this in your project you need the following in your pom.xml

   <dependency>
      <groupId>io.thorntail</groupId>
      <artifactId>microprofile-metrics</artifactId>
    </dependency>

There is no need to include the MicroProfile Metrics API dependency, as it comes with the fraction.

By default the base metrics and vendor metrics of the server are exposed as required by the spec.

Note

Exposing application metrics currently only works if you chose war packaging of your application

<project>
  <groupId>org.example</groupId>
  <artifactId>thorntail-demo</artifactId>
  <packaging>war</packaging> 1
1
war packaging

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-metrics</artifactId>
</dependency>

D.25.6. MicroProfile OpenAPI

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-openapi</artifactId>
</dependency>

D.25.7. MicroProfile OpenTracing

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-opentracing</artifactId>
</dependency>

D.25.8. MicroProfile Rest Client

D.25.8.1. CDI Interceptors Support

In general, Rest Client proxies are not created by the CDI container and therefore method invocations do not pass through CDI interceptors. In Thorntail, however, you can associate business method interceptors (denoted by the @AroundInvoke annotation) with a Rest Client proxy by using interceptor bindings. This feature is non-portable. The primary use case is the support of Section D.25.2, “MicroProfile Fault Tolerance” annotations, for example:

import org.eclipse.microprofile.faulttolerance.Retry;

@Path("/v1")
interface MyClient {

    @Retry(maxRetries = 3) // Retry on any exception thrown
    @GET
    @Path("/hello")
    String hello();
}
Note

The org.eclipse.microprofile.faulttolerance.Asynchronous annotation is currently not supported because the underlying RESTEasy client is not able to handle the java.util.concurrent.Future return types.

D.25.8.2. RestClientProxy

In addition to the MicroProfile Rest Client specification, every Rest Client proxy implements io.smallrye.restclient.RestClientProxy interface which allows you to:

  • obtain the underlying javax.ws.rs.client.Client instance
  • release all associated resources, for example:

    public void hello() {
       MyClient myClient = RestClientBuilder.newBuilder().build(MyClient.class);
       myClient.hello();
       // Finally release all associated resources
       ((RestClientProxy) helloClient).close();
    }

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>microprofile-restclient</artifactId>
</dependency>

D.26. Monitor

Warning

This fraction is deprecated. Use the io.thorntail:microprofile-health fraction instead.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>monitor</artifactId>
</dependency>

Configuration

thorntail.monitor.security-realm
(not yet documented)

D.27. MSC

Primarily an internal fraction providing support for the JBoss Modular Container (MSC). JBoss MSC provides the underpinning for all services wired together supporting the container and the application.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>msc</artifactId>
</dependency>

D.28. Naming

Provides support for JNDI.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>naming</artifactId>
</dependency>

Configuration

thorntail.naming.bindings.KEY.attribute-class
The object factory class name for object factory bindings
thorntail.naming.bindings.KEY.binding-type
The type of binding to create, may be simple, lookup, external-context or object-factory
thorntail.naming.bindings.KEY.cache
If the external context should be cached
thorntail.naming.bindings.KEY.environment
The environment to use on object factory instance retrieval
thorntail.naming.bindings.KEY.lookup
The entry to lookup in JNDI for lookup bindings
thorntail.naming.bindings.KEY.module
The module to load the object factory from for object factory bindings
thorntail.naming.bindings.KEY.type
The type of the value to bind for simple bindings, this must be a primitive type
thorntail.naming.bindings.KEY.value
The value to bind for simple bindings

D.29. Guava

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>netflix-guava</artifactId>
</dependency>

D.30. RX-Java

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>netflix-rxjava</artifactId>
</dependency>

D.31. OpenTracing

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>opentracing</artifactId>
</dependency>

Configuration

thorntail.opentracing.servlet.skipPattern
The servlet skip pattern as a Java compilable Pattern. Optional. Ex.: /health-check

D.31.1. OpenTracing TracerResolver

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>opentracing-tracerresolver</artifactId>
</dependency>

D.32. Remoting

Primarily an internal fraction providing remote invocation support for higher-level fractions such as EJB.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>remoting</artifactId>
</dependency>

Configuration

thorntail.remoting.auth-realm
The authentication realm to use if no authentication CallbackHandler is specified.
thorntail.remoting.authentication-retries
Specify the number of times a client is allowed to retry authentication before closing the connection.
thorntail.remoting.authorize-id
The SASL authorization ID. Used as authentication user name to use if no authentication CallbackHandler is specifiedand the selected SASL mechanism demands a user name.
thorntail.remoting.buffer-region-size
The size of allocated buffer regions.
thorntail.remoting.connectors.KEY.authentication-provider
The "authentication-provider" element contains the name of the authentication provider to use for incoming connections.
thorntail.remoting.connectors.KEY.properties.KEY.value
The property value.
thorntail.remoting.connectors.KEY.sasl-authentication-factory
Reference to the SASL authentication factory to secure this connector.
thorntail.remoting.connectors.KEY.sasl-protocol
The protocol to pass into the SASL mechanisms used for authentication.
thorntail.remoting.connectors.KEY.sasl-security.include-mechanisms
The optional nested "include-mechanisms" element contains a whitelist of allowed SASL mechanism names. No mechanisms will be allowed which are not present in this list.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.forward-secrecy
The optional nested "forward-secrecy" element contains a boolean value which specifies whether mechanisms that implement forward secrecy between sessions are required. Forward secrecy means that breaking into one session will not automatically provide information for breaking into future sessions.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.no-active
The optional nested "no-active" element contains a boolean value which specifies whether mechanisms susceptible to active (non-dictionary) attacks are not permitted. "false" to permit, "true" to deny.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.no-anonymous
The optional nested "no-anonymous" element contains a boolean value which specifies whether mechanisms that accept anonymous login are permitted. "false" to permit, "true" to deny.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.no-dictionary
The optional nested "no-dictionary" element contains a boolean value which specifies whether mechanisms susceptible to passive dictionary attacks are permitted. "false" to permit, "true" to deny.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.no-plain-text
The optional nested "no-plain-text" element contains a boolean value which specifies whether mechanisms susceptible to simple plain passive attacks (e.g., "PLAIN") are not permitted. "false" to permit, "true" to deny.
thorntail.remoting.connectors.KEY.sasl-security.policy-sasl-policy.pass-credentials
The optional nested "pass-credentials" element contains a boolean value which specifies whether mechanisms that pass client credentials are required.
thorntail.remoting.connectors.KEY.sasl-security.properties.KEY.value
The property value.
thorntail.remoting.connectors.KEY.sasl-security.qop
The optional nested "qop" element contains a list of quality-of-protection values, in decreasing order of preference.
thorntail.remoting.connectors.KEY.sasl-security.reuse-session
The optional nested "reuse-session" boolean element specifies whether or not the server should attempt to reuse previously authenticated session information. The mechanism may or may not support such reuse, and other factors may also prevent it.
thorntail.remoting.connectors.KEY.sasl-security.server-auth
The optional nested "server-auth" boolean element specifies whether the server should authenticate to the client. Not all mechanisms may support this setting.
thorntail.remoting.connectors.KEY.sasl-security.strength
The optional nested "strength" element contains a list of cipher strength values, in decreasing order of preference.
thorntail.remoting.connectors.KEY.security-realm
The associated security realm to use for authentication for this connector.
thorntail.remoting.connectors.KEY.server-name
The server name to send in the initial message exchange and for SASL based authentication.
thorntail.remoting.connectors.KEY.socket-binding
The name of the socket binding to attach to.
thorntail.remoting.connectors.KEY.ssl-context
Reference to the SSLContext to use for this connector.
thorntail.remoting.endpoint-configuration.auth-realm
The authentication realm to use if no authentication CallbackHandler is specified.
thorntail.remoting.endpoint-configuration.authentication-retries
Specify the number of times a client is allowed to retry authentication before closing the connection.
thorntail.remoting.endpoint-configuration.authorize-id
The SASL authorization ID. Used as authentication user name to use if no authentication CallbackHandler is specifiedand the selected SASL mechanism demands a user name.
thorntail.remoting.endpoint-configuration.buffer-region-size
The size of allocated buffer regions.
thorntail.remoting.endpoint-configuration.heartbeat-interval
The interval to use for connection heartbeat, in milliseconds. If the connection is idle in the outbound directionfor this amount of time, a ping message will be sent, which will trigger a corresponding reply message.
thorntail.remoting.endpoint-configuration.max-inbound-channels
The maximum number of inbound channels to support for a connection.
thorntail.remoting.endpoint-configuration.max-inbound-message-size
The maximum inbound message size to be allowed. Messages exceeding this size will cause an exception to be thrown on the reading side as well as the writing side.
thorntail.remoting.endpoint-configuration.max-inbound-messages
The maximum number of concurrent inbound messages on a channel.
thorntail.remoting.endpoint-configuration.max-outbound-channels
The maximum number of outbound channels to support for a connection.
thorntail.remoting.endpoint-configuration.max-outbound-message-size
The maximum outbound message size to send. No messages larger than this well be transmitted; attempting to do so will cause an exception on the writing side.
thorntail.remoting.endpoint-configuration.max-outbound-messages
The maximum number of concurrent outbound messages on a channel.
thorntail.remoting.endpoint-configuration.receive-buffer-size
The size of the largest buffer that this endpoint will accept over a connection.
thorntail.remoting.endpoint-configuration.receive-window-size
The maximum window size of the receive direction for connection channels, in bytes.
thorntail.remoting.endpoint-configuration.sasl-protocol
Where a SaslServer or SaslClient are created by default the protocol specified it 'remoting', this can be used to override this.
thorntail.remoting.endpoint-configuration.send-buffer-size
The size of the largest buffer that this endpoint will transmit over a connection.
thorntail.remoting.endpoint-configuration.server-name
The server side of the connection passes it’s name to the client in the initial greeting, by default the name is automatically discovered from the local address of the connection or it can be overridden using this.
thorntail.remoting.endpoint-configuration.transmit-window-size
The maximum window size of the transmit direction for connection channels, in bytes.
thorntail.remoting.endpoint-configuration.worker
Worker to use
thorntail.remoting.heartbeat-interval
The interval to use for connection heartbeat, in milliseconds. If the connection is idle in the outbound directionfor this amount of time, a ping message will be sent, which will trigger a corresponding reply message.
thorntail.remoting.http-connectors.KEY.authentication-provider
The "authentication-provider" element contains the name of the authentication provider to use for incoming connections.
thorntail.remoting.http-connectors.KEY.connector-ref
The name (or names) of a connector in the Undertow subsystem to connect to.
thorntail.remoting.http-connectors.KEY.properties.KEY.value
The property value.
thorntail.remoting.http-connectors.KEY.sasl-authentication-factory
Reference to the SASL authentication factory to use for this connector.
thorntail.remoting.http-connectors.KEY.sasl-protocol
The protocol to pass into the SASL mechanisms used for authentication.
thorntail.remoting.http-connectors.KEY.sasl-security.include-mechanisms
The optional nested "include-mechanisms" element contains a whitelist of allowed SASL mechanism names. No mechanisms will be allowed which are not present in this list.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.forward-secrecy
The optional nested "forward-secrecy" element contains a boolean value which specifies whether mechanisms that implement forward secrecy between sessions are required. Forward secrecy means that breaking into one session will not automatically provide information for breaking into future sessions.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.no-active
The optional nested "no-active" element contains a boolean value which specifies whether mechanisms susceptible to active (non-dictionary) attacks are not permitted. "false" to permit, "true" to deny.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.no-anonymous
The optional nested "no-anonymous" element contains a boolean value which specifies whether mechanisms that accept anonymous login are permitted. "false" to permit, "true" to deny.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.no-dictionary
The optional nested "no-dictionary" element contains a boolean value which specifies whether mechanisms susceptible to passive dictionary attacks are permitted. "false" to permit, "true" to deny.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.no-plain-text
The optional nested "no-plain-text" element contains a boolean value which specifies whether mechanisms susceptible to simple plain passive attacks (e.g., "PLAIN") are not permitted. "false" to permit, "true" to deny.
thorntail.remoting.http-connectors.KEY.sasl-security.policy-sasl-policy.pass-credentials
The optional nested "pass-credentials" element contains a boolean value which specifies whether mechanisms that pass client credentials are required.
thorntail.remoting.http-connectors.KEY.sasl-security.properties.KEY.value
The property value.
thorntail.remoting.http-connectors.KEY.sasl-security.qop
The optional nested "qop" element contains a list of quality-of-protection values, in decreasing order of preference.
thorntail.remoting.http-connectors.KEY.sasl-security.reuse-session
The optional nested "reuse-session" boolean element specifies whether or not the server should attempt to reuse previously authenticated session information. The mechanism may or may not support such reuse, and other factors may also prevent it.
thorntail.remoting.http-connectors.KEY.sasl-security.server-auth
The optional nested "server-auth" boolean element specifies whether the server should authenticate to the client. Not all mechanisms may support this setting.
thorntail.remoting.http-connectors.KEY.sasl-security.strength
The optional nested "strength" element contains a list of cipher strength values, in decreasing order of preference.
thorntail.remoting.http-connectors.KEY.security-realm
The associated security realm to use for authentication for this connector.
thorntail.remoting.http-connectors.KEY.server-name
The server name to send in the initial message exchange and for SASL based authentication.
thorntail.remoting.local-outbound-connections.KEY.outbound-socket-binding-ref
Name of the outbound-socket-binding which will be used to determine the destination address and port for the connection.
thorntail.remoting.local-outbound-connections.KEY.properties.KEY.value
The property value.
thorntail.remoting.max-inbound-channels
The maximum number of inbound channels to support for a connection.
thorntail.remoting.max-inbound-message-size
The maximum inbound message size to be allowed. Messages exceeding this size will cause an exception to be thrown on the reading side as well as the writing side.
thorntail.remoting.max-inbound-messages
The maximum number of concurrent inbound messages on a channel.
thorntail.remoting.max-outbound-channels
The maximum number of outbound channels to support for a connection.
thorntail.remoting.max-outbound-message-size
The maximum outbound message size to send. No messages larger than this well be transmitted; attempting to do so will cause an exception on the writing side.
thorntail.remoting.max-outbound-messages
The maximum number of concurrent outbound messages on a channel.
thorntail.remoting.outbound-connections.KEY.properties.KEY.value
The property value.
thorntail.remoting.outbound-connections.KEY.uri
The connection URI for the outbound connection.
thorntail.remoting.port
Port for legacy remoting connector
thorntail.remoting.receive-buffer-size
The size of the largest buffer that this endpoint will accept over a connection.
thorntail.remoting.receive-window-size
The maximum window size of the receive direction for connection channels, in bytes.
thorntail.remoting.remote-outbound-connections.KEY.authentication-context
Reference to the authentication context instance containing the configuration for outbound connections.
thorntail.remoting.remote-outbound-connections.KEY.outbound-socket-binding-ref
Name of the outbound-socket-binding which will be used to determine the destination address and port for the connection.
thorntail.remoting.remote-outbound-connections.KEY.properties.KEY.value
The property value.
thorntail.remoting.remote-outbound-connections.KEY.protocol
The protocol to use for the remote connection.
thorntail.remoting.remote-outbound-connections.KEY.security-realm
Reference to the security realm to use to obtain the password and SSL configuration.
thorntail.remoting.remote-outbound-connections.KEY.username
The user name to use when authenticating against the remote server.
thorntail.remoting.required
(not yet documented)
thorntail.remoting.sasl-protocol
Where a SaslServer or SaslClient are created by default the protocol specified it 'remoting', this can be used to override this.
thorntail.remoting.send-buffer-size
The size of the largest buffer that this endpoint will transmit over a connection.
thorntail.remoting.server-name
The server side of the connection passes it’s name to the client in the initial greeting, by default the name is automatically discovered from the local address of the connection or it can be overridden using this.
thorntail.remoting.transmit-window-size
The maximum window size of the transmit direction for connection channels, in bytes.
thorntail.remoting.worker
Worker to use
thorntail.remoting.worker-read-threads
The number of read threads to create for the remoting worker.
thorntail.remoting.worker-task-core-threads
The number of core threads for the remoting worker task thread pool.
thorntail.remoting.worker-task-keepalive
The number of milliseconds to keep non-core remoting worker task threads alive.
thorntail.remoting.worker-task-limit
The maximum number of remoting worker tasks to allow before rejecting.
thorntail.remoting.worker-task-max-threads
The maximum number of threads for the remoting worker task thread pool.
thorntail.remoting.worker-write-threads
The number of write threads to create for the remoting worker.

D.33. Request Controller

Provides support for the JBoss EAP request-controller, allowing for graceful pause/resume/shutdown of the container.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>request-controller</artifactId>
</dependency>

Configuration

thorntail.request-controller.active-requests
The number of requests that are currently running in the server
thorntail.request-controller.max-requests
The maximum number of all types of requests that can be running in a server at a time. Once this limit is hit any new requests will be rejected.
thorntail.request-controller.track-individual-endpoints
If this is true requests are tracked at an endpoint level, which will allow individual deployments to be suspended

D.34. Resource Adapters

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>resource-adapters</artifactId>
</dependency>

Configuration

thorntail.resource-adapters.resource-adapters.KEY.admin-objects.KEY.class-name
Specifies the fully qualified class name of an administration object.
thorntail.resource-adapters.resource-adapters.KEY.admin-objects.KEY.config-properties.KEY.value
Custom defined config property value.
thorntail.resource-adapters.resource-adapters.KEY.admin-objects.KEY.enabled
Specifies if the administration object should be enabled.
thorntail.resource-adapters.resource-adapters.KEY.admin-objects.KEY.jndi-name
Specifies the JNDI name for the administration object.
thorntail.resource-adapters.resource-adapters.KEY.admin-objects.KEY.use-java-context
Setting this to false will bind the object into global JNDI.
thorntail.resource-adapters.resource-adapters.KEY.archive
Specifies the resource adapter archive.
thorntail.resource-adapters.resource-adapters.KEY.beanvalidationgroups
Specifies the bean validation groups that should be used.
thorntail.resource-adapters.resource-adapters.KEY.bootstrap-context
Specifies the unique name of the bootstrap context that should be used.
thorntail.resource-adapters.resource-adapters.KEY.config-properties.KEY.value
Custom defined config property value.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.allocation-retry
The allocation retry element indicates the number of times that allocating a connection should be tried before throwing an exception.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.allocation-retry-wait-millis
The allocation retry wait millis element specifies the amount of time, in milliseconds, to wait between retrying to allocate a connection.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.authentication-context
The Elytron authentication context which defines the javax.security.auth.Subject that is used to distinguish connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.authentication-context-and-application
Indicates that either application-supplied parameters, such as from getConnection(user, pw), or Subject (provided by Elytron after authenticating using configured authentication-context), are used to distinguish connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.background-validation
An element to specify that connections should be validated on a background thread versus being validated prior to use. Changing this value requires a server restart.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.background-validation-millis
The background-validation-millis element specifies the amount of time, in milliseconds, that background validation will run. Changing this value requires a server restart.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.blocking-timeout-wait-millis
The blocking-timeout-millis element specifies the maximum time, in milliseconds, to block while waiting for a connection before throwing an exception. Note that this blocks only while waiting for locking a connection, and will never throw an exception if creating a new connection takes an inordinately long time.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.capacity-decrementer-class
Class defining the policy for decrementing connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.capacity-decrementer-properties
Properties to inject in class defining the policy for decrementing connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.capacity-incrementer-class
Class defining the policy for incrementing connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.capacity-incrementer-properties
Properties to inject in class defining the policy for incrementing connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.class-name
Specifies the fully qualified class name of a managed connection factory or admin object.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.config-properties.KEY.value
Custom defined config property value.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.connectable
Enable the use of CMR. This feature means that a local resource can reliably participate in an XA transaction.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.elytron-enabled
Enables Elytron security for handling authentication of connections. The Elytron authentication-context to be used will be current context if no context is specified (see authentication-context).
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.enabled
Specifies if the resource adapter should be enabled.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.enlistment
Defines if lazy enlistment should be used if supported by the resource adapter.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.enlistment-trace
Defines if WildFly/IronJacamar should record enlistment traces.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.flush-strategy
Specifies how the pool should be flushed in case of an error.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.idle-timeout-minutes
Specifies the maximum time, in minutes, a connection may be idle before being closed. The actual maximum time depends also on the IdleRemover scan time, which is half of the smallest idle-timeout-minutes value of any pool. Changing this value requires a server restart.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.initial-pool-size
Specifies the initial number of connections a pool should hold.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.interleaving
An element to enable interleaving for XA connections.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.jndi-name
Specifies the JNDI name for the connection factory.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.max-pool-size
Specifies the maximum number of connections for a pool. No more connections will be created in each sub-pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.mcp
Defines the ManagedConnectionPool implementation. For example: org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.min-pool-size
Specifies the minimum number of connections for a pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.no-recovery
Specifies if the connection pool should be excluded from recovery.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.no-tx-separate-pool
Oracle does not like XA connections getting used both inside and outside a JTA transaction. To workaround the problem you can create separate sub-pools for the different contexts.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.pad-xid
Specifies whether the Xid should be padded.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.pool-fair
Defines if pool use should be fair.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.pool-prefill
Specifies if the pool should be prefilled. Changing this value requires a server restart.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.pool-use-strict-min
Specifies if the min-pool-size should be considered strict.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-authentication-context
The Elytron authentication context used for recovery (current authentication-context will be used if unspecified).
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-credential-reference
Credential (from Credential Store) to authenticate on recovery connection
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-elytron-enabled
Indicates that an Elytron authentication context will be used for recovery.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-password
The password used for recovery.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-plugin-class-name
The fully qualified class name of the recovery plugin implementation.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-plugin-properties
The properties for the recovery plugin.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-security-domain
The PicketBox security domain used for recovery.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.recovery-username
The user name used for recovery.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.same-rm-override
Using this attribute, you can unconditionally set whether javax.transaction.xa.XAResource.isSameRM(XAResource) returns true or false.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.security-application
Indicates that application-supplied parameters, such as from getConnection(user, pw), are used to distinguish connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.security-domain
Specifies the PicketBox security domain which defines the javax.security.auth.Subject that is used to distinguish connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.security-domain-and-application
Indicates that either application-supplied parameters, such as from getConnection(user, pw), or Subject (from PicketBox security domain), are used to distinguish connections in the pool.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.sharable
Enable the use of sharable connections, which allows lazy association to be enabled if supported.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.tracking
Defines if IronJacamar should track connection handles across transaction boundaries.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.use-ccm
Enable the use of a cached connection manager.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.use-fast-fail
Whether to fail a connection allocation on the first try if it is invalid (true) or keep trying until the pool is exhausted of all potential connections (false).
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.use-java-context
Setting this to false will bind the object into global JNDI.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.validate-on-match
This specifies if connection validation should be done when a connection factory attempts to match a managed connection. This is typically exclusive to the use of background validation.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.wrap-xa-resource
Specifies whether XAResource instances should be wrapped in an org.jboss.tm.XAResourceWrapper instance.
thorntail.resource-adapters.resource-adapters.KEY.connection-definitions.KEY.xa-resource-timeout
The value is passed to XAResource.setTransactionTimeout(), in seconds.
thorntail.resource-adapters.resource-adapters.KEY.module
Specifies the module from which resource adapter will be loaded
thorntail.resource-adapters.resource-adapters.KEY.statistics-enabled
Define whether runtime statistics are enabled or not.
thorntail.resource-adapters.resource-adapters.KEY.transaction-support
Specifies the transaction support level of the resource adapter.
thorntail.resource-adapters.resource-adapters.KEY.wm-elytron-security-domain
Defines the name of the Elytron security domain that should be used.
thorntail.resource-adapters.resource-adapters.KEY.wm-security
Toggle on/off wm.security for this resource adapter. In case of false all wm-security-* parameters are ignored, even the defaults.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-default-groups
Defines a default groups list that should be added to the used Subject instance.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-default-principal
Defines a default principal name that should be added to the used Subject instance.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-domain
Defines the name of the PicketBox security domain that should be used.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-mapping-groups
List of groups mappings.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-mapping-required
Defines if a mapping is required for security credentials.
thorntail.resource-adapters.resource-adapters.KEY.wm-security-mapping-users
List of user mappings.

D.35. Security

Provides underlying security infrastructure to support JAAS and other security APIs.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>security</artifactId>
</dependency>

Configuration

thorntail.security.classic-vault.code
Fully Qualified Name of the Security Vault Implementation.
thorntail.security.classic-vault.vault-options
Security Vault options.
thorntail.security.deep-copy-subject-mode
Sets the copy mode of subjects done by the security managers to be deep copies that makes copies of the subject principals and credentials if they are cloneable. It should be set to true if subject include mutable content that can be corrupted when multiple threads have the same identity and cache flushes/logout clearing the subject in one thread results in subject references affecting other threads.
thorntail.security.elytron-key-managers.KEY.legacy-jsse-config
The name of the legacy security domain that contains a JSSE configuration that can be used to export the key manager.
thorntail.security.elytron-key-stores.KEY.legacy-jsse-config
The name of the legacy security domain that contains a JSSE configuration that can be used to export the key store.
thorntail.security.elytron-realms.KEY.apply-role-mappers
Indicates to the realm if it should apply the role mappers defined in the legacy domain to the roles obtained from authenticated Subjects or not.
thorntail.security.elytron-realms.KEY.legacy-jaas-config
The name of the legacy security domain to which authentication will be delegated.
thorntail.security.elytron-trust-managers.KEY.legacy-jsse-config
The name of the legacy security domain that contains a JSSE configuration that can be used to export the trust manager.
thorntail.security.elytron-trust-stores.KEY.legacy-jsse-config
The name of the legacy security domain that contains a JSSE configuration that can be used to export the trust store.
thorntail.security.initialize-jacc
Indicates if this subsystem should be in charge of initializing JACC related services.
thorntail.security.security-domains.KEY.cache-type
Adds a cache to speed up authentication checks. Allowed values are 'default' to use simple map as the cache and 'infinispan' to use an Infinispan cache.
thorntail.security.security-domains.KEY.classic-acl.acl-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-acl.acl-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.classic-acl.acl-modules.KEY.module
Name of JBoss Module where the login module is located.
thorntail.security.security-domains.KEY.classic-acl.acl-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-audit.provider-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-audit.provider-modules.KEY.module
Name of JBoss Module where the mapping module code is located.
thorntail.security.security-domains.KEY.classic-audit.provider-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-authentication.login-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-authentication.login-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.classic-authentication.login-modules.KEY.module
Name of JBoss Module where the login module is located.
thorntail.security.security-domains.KEY.classic-authentication.login-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-authorization.policy-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-authorization.policy-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.classic-authorization.policy-modules.KEY.module
Name of JBoss Module where the login module is located.
thorntail.security.security-domains.KEY.classic-authorization.policy-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-identity-trust.trust-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-identity-trust.trust-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.classic-identity-trust.trust-modules.KEY.module
Name of JBoss Module where the login module is located.
thorntail.security.security-domains.KEY.classic-identity-trust.trust-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-jsse.additional-properties
Additional properties that may be necessary to configure JSSE.
thorntail.security.security-domains.KEY.classic-jsse.cipher-suites
Comma separated list of cipher suites to enable on SSLSockets.
thorntail.security.security-domains.KEY.classic-jsse.client-alias
Preferred alias to use when the KeyManager chooses the client alias.
thorntail.security.security-domains.KEY.classic-jsse.client-auth
Boolean attribute to indicate if client’s certificates should also be authenticated on the server side.
thorntail.security.security-domains.KEY.classic-jsse.key-manager
JSEE Key Manager factory
thorntail.security.security-domains.KEY.classic-jsse.keystore
Configures a JSSE key store
thorntail.security.security-domains.KEY.classic-jsse.protocols
Comma separated list of protocols to enable on SSLSockets.
thorntail.security.security-domains.KEY.classic-jsse.server-alias
Preferred alias to use when the KeyManager chooses the server alias.
thorntail.security.security-domains.KEY.classic-jsse.service-auth-token
Token to retrieve PrivateKeys from the KeyStore.
thorntail.security.security-domains.KEY.classic-jsse.trust-manager
JSEE Trust Manager factory
thorntail.security.security-domains.KEY.classic-jsse.truststore
Configures a JSSE trust store
thorntail.security.security-domains.KEY.classic-mapping.mapping-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.classic-mapping.mapping-modules.KEY.module
Name of JBoss Module where the mapping module code is located.
thorntail.security.security-domains.KEY.classic-mapping.mapping-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.classic-mapping.mapping-modules.KEY.type
Type of mapping this module performs. Allowed values are principal, role, attribute or credential..
thorntail.security.security-domains.KEY.jaspi-authentication.auth-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.jaspi-authentication.auth-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.jaspi-authentication.auth-modules.KEY.login-module-stack-ref
Reference to a login module stack name previously configured in the same security domain.
thorntail.security.security-domains.KEY.jaspi-authentication.auth-modules.KEY.module
Name of JBoss Module where the mapping module code is located.
thorntail.security.security-domains.KEY.jaspi-authentication.auth-modules.KEY.module-options
List of module options containing a name/value pair.
thorntail.security.security-domains.KEY.jaspi-authentication.login-module-stacks.KEY.login-modules.KEY.code
Class name of the module to be instantiated.
thorntail.security.security-domains.KEY.jaspi-authentication.login-module-stacks.KEY.login-modules.KEY.flag
The flag controls how the module participates in the overall procedure. Allowed values are requisite, required, sufficient or optional.
thorntail.security.security-domains.KEY.jaspi-authentication.login-module-stacks.KEY.login-modules.KEY.module
Name of JBoss Module where the login module is located.
thorntail.security.security-domains.KEY.jaspi-authentication.login-module-stacks.KEY.login-modules.KEY.module-options
List of module options containing a name/value pair.

D.36. Topology

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>topology</artifactId>
</dependency>

D.36.1. OpenShift

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>topology-openshift</artifactId>
</dependency>

D.36.2. Topology UI

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>topology-webapp</artifactId>
</dependency>

Configuration

thorntail.topology.web-app.expose-topology-endpoint
Flag to enable or disable the topology web endpoint
thorntail.topology.web-app.proxied-service-mappings
Service name to URL path proxy mappings

D.37. Transactions

Provides support for the Java Transaction API (JTA) according to JSR-907.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>transactions</artifactId>
</dependency>

Configuration

thorntail.transactions.average-commit-time
The average time of transaction commit in nanoseconds, measured from the moment the client calls commit until the transaction manager determines that the commit attempt was successful.
thorntail.transactions.commit-markable-resources.KEY.batch-size
Batch size for this CMR resource
thorntail.transactions.commit-markable-resources.KEY.immediate-cleanup
Immediate cleanup associated to this CMR resource
thorntail.transactions.commit-markable-resources.KEY.jndi-name
JNDi name of this CMR resource
thorntail.transactions.commit-markable-resources.KEY.name
table name for storing XIDs
thorntail.transactions.default-timeout
The default timeout for a transaction managed by the transaction manager.
thorntail.transactions.enable-statistics
Whether transaction statistics should be gathered.
thorntail.transactions.enable-tsm-status
Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
thorntail.transactions.hornetq-store-enable-async-io
Whether AsyncIO should be enabled for the journal store.
thorntail.transactions.jdbc-action-store-drop-table
Configure if jdbc action store should drop tables.
thorntail.transactions.jdbc-action-store-table-prefix
Optional prefix for table used to write transaction logs in configured jdbc action store.
thorntail.transactions.jdbc-communication-store-drop-table
Configure if jdbc communication store should drop tables.
thorntail.transactions.jdbc-communication-store-table-prefix
Optional prefix for table used to write transaction logs in configured jdbc communication store.
thorntail.transactions.jdbc-state-store-drop-table
Configure if jdbc state store should drop tables.
thorntail.transactions.jdbc-state-store-table-prefix
Optional prefix for table used to write transaction logs in configured jdbc state store.
thorntail.transactions.jdbc-store-datasource
Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false".
thorntail.transactions.journal-store-enable-async-io
Whether AsyncIO should be enabled for the journal store. For this settings being active journal natives libraries needs to be available.
thorntail.transactions.jts
If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full.
thorntail.transactions.log-store.expose-all-logs
Whether to expose all logs like orphans etc. By default only a subset of transaction logs is exposed.
thorntail.transactions.log-store.transactions.KEY.age-in-seconds
The time since this transaction was prepared or when the recovery system last tried to recover it.
thorntail.transactions.log-store.transactions.KEY.id
The id of this transaction.
thorntail.transactions.log-store.transactions.KEY.jmx-name
The JMX name of this transaction.
thorntail.transactions.log-store.transactions.KEY.participants.KEY.eis-product-name
The JCA enterprise information system’s product name.
thorntail.transactions.log-store.transactions.KEY.participants.KEY.eis-product-version
The JCA enterprise information system’s product version
thorntail.transactions.log-store.transactions.KEY.participants.KEY.jmx-name
The JMX name of this participant.
thorntail.transactions.log-store.transactions.KEY.participants.KEY.jndi-name
JNDI name of this participant.
thorntail.transactions.log-store.transactions.KEY.participants.KEY.status
Reports the commitment status of this participant (can be one of Pending, Prepared, Failed, Heuristic or Readonly).
thorntail.transactions.log-store.transactions.KEY.participants.KEY.type
The type name under which this record is stored.
thorntail.transactions.log-store.transactions.KEY.type
The type name under which this record is stored.
thorntail.transactions.log-store.type
Specifies the implementation type of the logging store.
thorntail.transactions.maximum-timeout
If the default timeout is zero then this value is consulted to set the maximum timeout (in seconds) for a transaction managed by the transaction manager.
thorntail.transactions.node-identifier
Used to set the node identifier on the core environment. Each Xid that Transaction Manager creates will have this identifier encoded within it and ensures Transaction Manager will only recover branches which match the specified identifier. It is imperative that this identifier is unique between Application Server instances which share either an object store or access common resource managers.
thorntail.transactions.number-of-aborted-transactions
The number of aborted (i.e. rolledback) transactions.
thorntail.transactions.number-of-application-rollbacks
The number of transactions that have been rolled back by application request. This includes those that timeout, since the timeout behavior is considered an attribute of the application configuration.
thorntail.transactions.number-of-committed-transactions
The number of committed transactions.
thorntail.transactions.number-of-heuristics
The number of transactions which have terminated with heuristic outcomes.
thorntail.transactions.number-of-inflight-transactions
The number of transactions that have begun but not yet terminated.
thorntail.transactions.number-of-nested-transactions
The total number of nested (sub) transactions created.
thorntail.transactions.number-of-resource-rollbacks
The number of transactions that rolled back due to resource (participant) failure.
thorntail.transactions.number-of-system-rollbacks
The number of transactions that have been rolled back due to internal system errors.
thorntail.transactions.number-of-timed-out-transactions
The number of transactions that have rolled back due to timeout.
thorntail.transactions.number-of-transactions
The total number of transactions (top-level and nested) created
thorntail.transactions.object-store-path
Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It’s not used when jdbc journal store is used.
thorntail.transactions.object-store-relative-to
References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Undefine this attribute to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path.
thorntail.transactions.port
Port for transaction manager
thorntail.transactions.process-id-socket-binding
The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
thorntail.transactions.process-id-socket-max-ports
The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
thorntail.transactions.process-id-uuid
Indicates whether the transaction manager should use a UUID based process id.
thorntail.transactions.recovery-listener
Used to specify if the recovery system should listen on a network socket or not.
thorntail.transactions.socket-binding
Used to reference the correct socket binding to use for the recovery environment.
thorntail.transactions.statistics-enabled
Whether transaction statistics should be gathered.
thorntail.transactions.status-port
Status port for transaction manager
thorntail.transactions.status-socket-binding
Used to reference the correct socket binding to use for the transaction status manager.
thorntail.transactions.use-hornetq-store
Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log.It’s alternative to jdbc based store.
thorntail.transactions.use-jdbc-store
Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It’s alternative to journal based store.
thorntail.transactions.use-journal-store
Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file system file per transaction log. The journal one consists from one file for all the transactions. It’s alternative to jdbc based store.

D.38. Undertow

Provides basic HTTP support, including Java Servlets, JavaServer Pages (JSP), and JavaServer Pages Standard Tag Library (JSTL) according to JSR-340, JSR-245 and JSR-52.

Maven Coordinates

<dependency>
  <groupId>io.thorntail</groupId>
  <artifactId>undertow</artifactId>
</dependency>

Configuration

thorntail.ajp.enable
Determine if AJP should be enabled
thorntail.ajp.port
Set the port for the default AJP listener
thorntail.deployment
Map of security configuration by deployment
thorntail.http.port
Set the port for the default HTTP listener
thorntail.https.certificate.generate
Should a self-signed certificate be generated
thorntail.https.certificate.generate.host
Hostname for the generated self-signed certificate
thorntail.https.key.alias
Alias to the server certificate key entry in the keystore
thorntail.https.key.password
Password to the server certificate
thorntail.https.keystore.embedded
Should an embedded keystore be created
thorntail.https.keystore.password
Password to the server keystore
thorntail.https.keystore.path
Path to the server keystore
thorntail.https.only
Only enable the HTTPS Listener
thorntail.https.port
Set the port for the default HTTPS listener
thorntail.undertow.application-security-domains.KEY.enable-jacc
Enable authorization using JACC
thorntail.undertow.application-security-domains.KEY.enable-jaspi
Enable JASPI authentication for the associated deployments.
thorntail.undertow.application-security-domains.KEY.http-authentication-factory
The HTTP Authentication Factory to be used by deployments that reference the mapped security domain.
thorntail.undertow.application-security-domains.KEY.integrated-jaspi
Should integrated JASPI be used or allow AsHoc identity creation.
thorntail.undertow.application-security-domains.KEY.override-deployment-config
Should the authentication configuration in the deployment be overridden by the factory.
thorntail.undertow.application-security-domains.KEY.referencing-deployments
The deployments currently referencing this mapping.
thorntail.undertow.application-security-domains.KEY.security-domain
The SecurityDomain to be used by deployments that reference the mapped security domain.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.client-ssl-context
Reference to the SSL context used to secure back-channel logout connection.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.cookie-name
Name of the cookie
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.credential-reference
The credential reference to decrypt the private key entry.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.domain
The cookie domain that will be used.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.http-only
Set Cookie httpOnly attribute.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.key-alias
Alias of the private key entry used for signing and verifying back-channel logout connection.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.key-store
Reference to key store containing a private key entry.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.path
Cookie path.
thorntail.undertow.application-security-domains.KEY.single-sign-on-setting.secure
Set Cookie secure attribute.
thorntail.undertow.buffer-caches.KEY.buffer-size
The size of an individual buffer, in bytes.
thorntail.undertow.buffer-caches.KEY.buffers-per-region
The numbers of buffers in a region
thorntail.undertow.buffer-caches.KEY.max-regions
The maximum number of regions
thorntail.undertow.byte-buffer-pools.KEY.buffer-size
The size of the buffer
thorntail.undertow.byte-buffer-pools.KEY.direct
If this is true the buffer pool will use direct buffers, this is recommended for best performance
thorntail.undertow.byte-buffer-pools.KEY.leak-detection-percent
The percentage of buffers that will be allocated with a leak detector. This should only be larger than zero if you are experiencing issues with buffers leaking.
thorntail.undertow.byte-buffer-pools.KEY.max-pool-size
The maximum amount of buffers to keep in the pool. If more buffers are required at runtime they will be allocated dynamically. Setting this to zero effectively disables pooling.
thorntail.undertow.byte-buffer-pools.KEY.thread-local-cache-size
The maximum number of buffers to cache on each thread. The actual number may be lower depending on the calculated usage pattern.
thorntail.undertow.default-security-domain
The default security domain used by web deployments
thorntail.undertow.default-server
The default server to use for deployments
thorntail.undertow.default-servlet-container
The default servlet container to use for deployments
thorntail.undertow.default-virtual-host
The default virtual host to use for deployments
thorntail.undertow.filter-configuration.custom-filters.KEY.class-name
Class name of HttpHandler
thorntail.undertow.filter-configuration.custom-filters.KEY.module
Module name where class can be loaded from
thorntail.undertow.filter-configuration.custom-filters.KEY.parameters
Filter parameters
thorntail.undertow.filter-configuration.error-pages.KEY.code
Error page code
thorntail.undertow.filter-configuration.error-pages.KEY.path
Error page path
thorntail.undertow.filter-configuration.expression-filters.KEY.expression
The expression that defines the filter
thorntail.undertow.filter-configuration.expression-filters.KEY.module
Module to use to load the filter definitions
thorntail.undertow.filter-configuration.mod-clusters.KEY.advertise-frequency
The frequency (in milliseconds) that mod-cluster advertises itself on the network
thorntail.undertow.filter-configuration.mod-clusters.KEY.advertise-path
The path that mod-cluster is registered under.
thorntail.undertow.filter-configuration.mod-clusters.KEY.advertise-protocol
The protocol that is in use.
thorntail.undertow.filter-configuration.mod-clusters.KEY.advertise-socket-binding
The multicast group and port that is used to advertise.
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.max-attempts
Maximum number of failover attempts by reverse proxy when sending the request to the backend server.
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.aliases
The nodes aliases
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.cache-connections
The number of connections to keep alive indefinitely
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.contexts.KEY.requests
The number of requests against this context
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.contexts.KEY.status
The status of this context
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.elected
The elected count
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.flush-packets
If received data should be immediately flushed
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.load
The current load of this node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.load-balancing-group
The load balancing group this node belongs to
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.max-connections
The maximum number of connections per IO thread
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.open-connections
The current number of open connections
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.ping
The nodes ping
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.queue-new-requests
If a request is received and there is no worker immediately available should it be queued
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.read
The number of bytes read from the node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.request-queue-size
The size of the request queue
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.status
The current status of this node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.timeout
The request timeout
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.ttl
The time connections will stay alive with no requests before being closed, if the number of connections is larger than cache-connections
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.uri
The URI that the load balancer uses to connect to the node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.nodes.KEY.written
The number of bytes transferred to the node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.sticky-session
If sticky sessions are enabled
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.sticky-session-cookie
The session cookie name
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.sticky-session-force
If this is true then an error will be returned if the request cannot be routed to the sticky node, otherwise it will be routed to another node
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.sticky-session-path
The path of the sticky session cookie
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.sticky-session-remove
Remove the session cookie if the request cannot be routed to the correct host
thorntail.undertow.filter-configuration.mod-clusters.KEY.balancers.KEY.wait-worker
The number of seconds to wait for an available worker
thorntail.undertow.filter-configuration.mod-clusters.KEY.broken-node-timeout
The amount of time that must elapse before a broken node is removed from the table
thorntail.undertow.filter-configuration.mod-clusters.KEY.cached-connections-per-thread
The number of connections that will be kept alive indefinitely
thorntail.undertow.filter-configuration.mod-clusters.KEY.connection-idle-timeout
The amount of time a connection can be idle before it will be closed. Connections will not time out once the pool size is down to the configured minimum (as configured by cached-connections-per-thread)
thorntail.undertow.filter-configuration.mod-clusters.KEY.connections-per-thread
The number of connections that will be maintained to backend servers, per IO thread.
thorntail.undertow.filter-configuration.mod-clusters.KEY.enable-http2
If the load balancer should attempt to upgrade back end connections to HTTP2. If HTTP2 is not supported HTTP or HTTPS will be used as normal
thorntail.undertow.filter-configuration.mod-clusters.KEY.failover-strategy
Determines how a failover node is chosen, in the event that the node to which a session has affinity is not available.
thorntail.undertow.filter-configuration.mod-clusters.KEY.health-check-interval
The frequency of health check pings to backend nodes
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-enable-push
If push should be enabled for HTTP/2 connections
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-header-table-size
The size of the header table used for HPACK compression, in bytes. This amount of memory will be allocated per connection for compression. Larger values use more memory but may give better compression.
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-initial-window-size
The flow control window size that controls how quickly the client can send data to the server
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-max-concurrent-streams
The maximum number of HTTP/2 streams that can be active at any time on a single connection
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-max-frame-size
The max HTTP/2 frame size
thorntail.undertow.filter-configuration.mod-clusters.KEY.http2-max-header-list-size
The maximum size of request headers the server is prepared to accept
thorntail.undertow.filter-configuration.mod-clusters.KEY.management-access-predicate
A predicate that is applied to incoming requests to determine if they can perform mod cluster management commands. Provides additional security on top of what is provided by limiting management to requests that originate from the management-socket-binding
thorntail.undertow.filter-configuration.mod-clusters.KEY.management-socket-binding
The socket binding of the mod_cluster management address and port. When using mod_cluster two HTTP listeners should be defined, a public one to handle requests, and one bound to the internal network to handle mod cluster commands. This socket binding should correspond to the internal listener, and should not be publicly accessible.
thorntail.undertow.filter-configuration.mod-clusters.KEY.max-ajp-packet-size
The maximum size for AJP packets. Increasing this will allow AJP to work for requests/responses that have a large amount of headers. This is an advanced option, and must be the same between load balancers and backend servers.
thorntail.undertow.filter-configuration.mod-clusters.KEY.max-request-time
The max amount of time that a request to a backend node can take before it is killed
thorntail.undertow.filter-configuration.mod-clusters.KEY.max-retries
The number of times to attempt to retry a request if it fails. Note that if a request is not considered idempotent then it will only be retried if the proxy can be sure it was not sent to the backend server).
thorntail.undertow.filter-configuration.mod-clusters.KEY.request-queue-size
The number of requests that can be queued if the connection pool is full before requests are rejected with a 503
thorntail.undertow.filter-configuration.mod-clusters.KEY.security-key
The security key that is used for the mod-cluster group. All members must use the same security key.
thorntail.undertow.filter-configuration.mod-clusters.KEY.security-realm
The security realm that provides the SSL configuration
thorntail.undertow.filter-configuration.mod-clusters.KEY.ssl-context
Reference to the SSLContext to be used by this filter.
thorntail.undertow.filter-configuration.mod-clusters.KEY.use-alias
If an alias check is performed
thorntail.undertow.filter-configuration.mod-clusters.KEY.worker
The XNIO worker that is used to send the advertise notifications
thorntail.undertow.filter-configuration.request-limits.KEY.max-concurrent-requests
Maximum number of concurrent requests
thorntail.undertow.filter-configuration.request-limits.KEY.queue-size
Number of requests to queue before they start being rejected
thorntail.undertow.filter-configuration.response-headers.KEY.header-name
Header name
thorntail.undertow.filter-configuration.response-headers.KEY.header-value
Value for header
thorntail.undertow.filter-configuration.rewrites.KEY.redirect
If this is true then a redirect will be done instead of a rewrite
thorntail.undertow.filter-configuration.rewrites.KEY.target
The expression that defines the target. If you are redirecting to a constant target put single quotes around the value
thorntail.undertow.handler-configuration.files.KEY.cache-buffer-size
Size of the buffers, in bytes.
thorntail.undertow.handler-configuration.files.KEY.cache-buffers
Number of buffers
thorntail.undertow.handler-configuration.files.KEY.case-sensitive
Use case sensitive file handling
thorntail.undertow.handler-configuration.files.KEY.directory-listing
Enable directory listing?
thorntail.undertow.handler-configuration.files.KEY.follow-symlink
Enable following symbolic links
thorntail.undertow.handler-configuration.files.KEY.path
Path on filesystem from where file handler will serve resources
thorntail.undertow.handler-configuration.files.KEY.safe-symlink-paths
Paths that are safe to be targets of symbolic links
thorntail.undertow.handler-configuration.reverse-proxies.KEY.cached-connections-per-thread
The number of connections that will be kept alive indefinitely
thorntail.undertow.handler-configuration.reverse-proxies.KEY.connection-idle-timeout
The amount of time a connection can be idle before it will be closed. Connections will not time out once the pool size is down to the configured minimum (as configured by cached-connections-per-thread)
thorntail.undertow.handler-configuration.reverse-proxies.KEY.connections-per-thread
The number of connections that will be maintained to backend servers, per IO thread.
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.enable-http2
If this is true then the proxy will attempt to use HTTP/2 to connect to the backend. If it is not supported it will fall back to HTTP/1.1.
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.instance-id
The instance id (aka JVM route) that will be used to enable sticky sessions
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.outbound-socket-binding
Outbound socket binding for this host
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.path
Optional path if host is using non root resource
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.scheme
What kind of scheme is used
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.security-realm
The security realm that provides the SSL configuration for the connection to the host
thorntail.undertow.handler-configuration.reverse-proxies.KEY.hosts.KEY.ssl-context
Reference to the SSLContext to be used by this handler.
thorntail.undertow.handler-configuration.reverse-proxies.KEY.max-request-time
The maximum time that a proxy request can be active for, before being killed
thorntail.undertow.handler-configuration.reverse-proxies.KEY.max-retries
The number of times to attempt to retry a request if it fails. Note that if a request is not considered idempotent then it will only be retried if the proxy can be sure it was not sent to the backend server).
thorntail.undertow.handler-configuration.reverse-proxies.KEY.problem-server-retry
Time in seconds to wait before attempting to reconnect to a server that is down
thorntail.undertow.handler-configuration.reverse-proxies.KEY.request-queue-size
The number of requests that can be queued if the connection pool is full before requests are rejected with a 503
thorntail.undertow.handler-configuration.reverse-proxies.KEY.session-cookie-names
Comma separated list of session cookie names. Generally this will just be JSESSIONID.
thorntail.undertow.instance-id
The cluster instance id
thorntail.undertow.servers.KEY.ajp-listeners.KEY.allow-encoded-slash
If a request comes in with encoded / characters (i.e. %2F), will these be decoded.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.allow-equals-in-cookie-value
If this is true then Undertow will allow non-escaped equals characters in unquoted cookie values. Unquoted cookie values may not contain equals characters. If present the value ends before the equals sign. The remainder of the cookie value will be dropped.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.allow-unescaped-characters-in-url
If this is true Undertow will accept non-encoded characters that are disallowed by the URI specification. This defaults to false, and in general should not be needed as most clients correctly encode characters. Note that setting this to true can be considered a security risk, as allowing non-standard characters can allow request smuggling attacks in some circumstances.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.always-set-keep-alive
If this is true then a Connection: keep-alive header will be added to responses, even when it is not strictly required by the specification.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.buffer-pipelined-data
If we should buffer pipelined requests.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.buffer-pool
The listeners buffer pool
thorntail.undertow.servers.KEY.ajp-listeners.KEY.bytes-received
The number of bytes that have been received by this listener
thorntail.undertow.servers.KEY.ajp-listeners.KEY.bytes-sent
The number of bytes that have been sent out on this listener
thorntail.undertow.servers.KEY.ajp-listeners.KEY.decode-url
If this is true then the parser will decode the URL and query parameters using the selected character encoding (UTF-8 by default). If this is false they will not be decoded. This will allow a later handler to decode them into whatever charset is desired.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.disallowed-methods
A comma separated list of HTTP methods that are not allowed
thorntail.undertow.servers.KEY.ajp-listeners.KEY.error-count
The number of 500 responses that have been sent by this listener
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-ajp-packet-size
The maximum supported size of AJP packets. If this is modified it has to be increased on the load balancer and the backend server.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-buffered-request-size
Maximum size of a buffered request, in bytes. Requests are not usually buffered, the most common case is when performing SSL renegotiation for a POST request, and the post data must be fully buffered in order to perform the renegotiation.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-connections
The maximum number of concurrent connections. Only values greater than 0 are allowed. For unlimited connections simply undefine this attribute value.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-cookies
The maximum number of cookies that will be parsed. This is used to protect against hash vulnerabilities.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-header-size
The maximum size of a http request header, in bytes.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-headers
The maximum number of headers that will be parsed. This is used to protect against hash vulnerabilities.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-parameters
The maximum number of parameters that will be parsed. This is used to protect against hash vulnerabilities. This applies to both query parameters, and to POST data, but is not cumulative (i.e. you can potentially have max parameters * 2 total parameters).
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-post-size
The maximum size of a post that will be accepted, in bytes.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.max-processing-time
The maximum processing time taken by a request on this listener
thorntail.undertow.servers.KEY.ajp-listeners.KEY.no-request-timeout
The length of time in milliseconds that the connection can be idle before it is closed by the container.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.processing-time
The total processing time of all requests handed by this listener
thorntail.undertow.servers.KEY.ajp-listeners.KEY.read-timeout
Configure a read timeout for a socket, in milliseconds. If the given amount of time elapses without a successful read taking place, the socket’s next read will throw a {@link ReadTimeoutException}.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.receive-buffer
The receive buffer size, in bytes.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.record-request-start-time
If this is true then Undertow will record the request start time, to allow for request time to be logged. This has a small but measurable performance impact
thorntail.undertow.servers.KEY.ajp-listeners.KEY.redirect-socket
If this listener is supporting non-SSL requests, and a request is received for which a matching <security-constraint> requires SSL transport, undertow will automatically redirect the request to the socket binding port specified here.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.request-count
The number of requests this listener has served
thorntail.undertow.servers.KEY.ajp-listeners.KEY.request-parse-timeout
The maximum amount of time (in milliseconds) that can be spent parsing the request
thorntail.undertow.servers.KEY.ajp-listeners.KEY.resolve-peer-address
Enables host dns lookup
thorntail.undertow.servers.KEY.ajp-listeners.KEY.rfc6265-cookie-validation
If cookies should be validated to ensure they comply with RFC6265.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.scheme
The listener scheme, can be HTTP or HTTPS. By default the scheme will be taken from the incoming AJP request.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.secure
If this is true then requests that originate from this listener are marked as secure, even if the request is not using HTTPS.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.send-buffer
The send buffer size, in bytes.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.socket-binding
The listener socket binding
thorntail.undertow.servers.KEY.ajp-listeners.KEY.tcp-backlog
Configure a server with the specified backlog.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.tcp-keep-alive
Configure a channel to send TCP keep-alive messages in an implementation-dependent manner.
thorntail.undertow.servers.KEY.ajp-listeners.KEY.url-charset
URL charset
thorntail.undertow.servers.KEY.ajp-listeners.KEY.worker
The listeners XNIO worker
thorntail.undertow.servers.KEY.ajp-listeners.KEY