Table of Contents

Search

  1. Preface
  2. Upgrade Overview
  3. Pre-Upgrade Tasks
  4. Database Tasks
  5. Application Server Tasks
  6. Hub Store Upgrade
  7. Hub Server Upgrade (In-place Upgrade)
  8. Process Server Upgrade (In-place Upgrade)
  9. Post-Upgrade Tasks
  10. Search Configuration Upgrade
  11. Hierarchies Upgrade
  12. ActiveVOS Post-Installation Tasks for the Application Server
  13. ActiveVOS Post-Upgrade Tasks for Business Entity Adapter
  14. ActiveVOS Post-Upgrade Tasks for Subject Areas Adapter
  15. Appendix A: Troubleshooting the Upgrade Process
  16. Appendix B: Frequently Asked Questions
  17. Appendix C: Processing Existing ActiveVOS Tasks
  18. Appendix D: Configuring Metadata Caching

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Upgrading from Version 10.1, 10.2, 10.3, 10.4, or 10.5

Infinispan Attributes

Infinispan Attributes

The following table summarizes default Infinispan attribute values and indicates how the attributes map to the former JBoss attribute:
Infinispan Element and Attribute
Default Value
Description
JBoss Attribute
locking acquire-timeout
60000
Maximum time during which the Hub Server can try to acquire a lock.
lockAcquisitionTimeout
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.
sync replTimeout
transport cluster
infinispan-cluster
Name for the underlying group communication cluster.
clustering
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.
jgroupsConfig
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.
eviction timeToLive
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.
eviction timeToLive

0 COMMENTS

We’d like to hear from you!