Multidomain MDM
- Multidomain MDM 10.4
- All Products
Infinispan Element and Attribute
| Default Value
| Description
|
---|---|---|
locking acquire-timeout
| 60000
| Maximum time during which the Hub Server can try to acquire a lock.
|
transaction stop-timeout
| 30000
| When a cache stops, this attribute sets the maximum time that Infinispan waits while the Hub Server finishes remote and local transactions.
|
transport cluster
| infinispan-cluster
| Name for the underlying group communication cluster.
|
transport stack
| UDP
| Type of configuration: UDP or TCP. The configurations are defined in the jgroups-udp.xml file and the
jgroups-tcp.xml file.
|
transport node-name
| $node$
| Name of the current node. The Hub Server sets this attribute.
The node-name defaults to a combination of the host name and a random number. The number differentiates multiple nodes on the same host.
|
transport machine
| $machine$
| ID of the machine where the node runs. The Hub Server sets this attribute.
|
expiration lifespan
| --
| Maximum lifespan of a cache entry in milliseconds. When a cache entry exceeds its lifespan, the entry expires within the cluster. If you need to optimize performance, increase the lifespan for the following caches: DISABLE_WHEN_LOCK, DATA_OBJECTS, and REPOS_OBJECTS.
For example, you can increase the lifespan from one hour (3600000) to one day (86400000).
Each cache has its own default value for this attribute. To find the default values, open the
inifinspanConfig.xml file.
|
expiration interval
| --
| Maximum interval for checking the lifespan. If you need to optimize performance, increase the interval for the following caches: DISABLE_WHEN_LOCK, DATA_OBJECTS, and REPOS_OBJECTS.
For example, you can increase the interval from five seconds (5000) to five minutes (300000).
Each cache has its own default value for this attribute. To find the default values, open the
inifinspanConfig.xml file.
|