BigMemory Max 4.3.7 is the latest release. It includes Ehcache 2.10.7.

Fixes are cumulative from version to version.


New Features

BigMemory Max 4.3 introduces following new capabilities:

  1. Terracotta Management Console (TMC) extended to support WAN Replication Service: The WAN tab enables monitoring of information about the following aspects of the WAN Replication Service:
    1. WAN's topology and configuration information
    2. Performance statistics and details of their deployment, such as the orchestrator topology, configuration, and status of each WAN-enabled cache. 
  2. Support for Java 8
  3. Support for RedHat EL7 (server)
  4. Ability to restrict TMC access to execute adhoc (BigMemory) SQL (BigMemory 4.3.1)
  5. Support for SUSE Linux Enterprise 12 (BigMemory 4.3.1)
  6. A simpler version (IP whitelist) of access restrictions has been added (restricting access to a list of provided IP addresses) (BigMemory 4.3.2)
  7. Failover Tuning – Data consistency for cross-data center clustering (BigMemory 4.3.3)
  8. Support for Tomcat 8 (BigMemory 4.3.3)
  9. Quartz no longer supported (BigMemory 4.3.3)
  10.  Added Docker to Terracotta kit for SAG Install (BigMemory 4.3.4) 
  11. Support for Windows Server 2016 (BigMemory 4.3.4)

Summary of Changes in 4.3.7

New in Terracotta BigMemory 4.3.7

Resolved

Known Issues

Summary of Changes in 4.3.6.5

Resolved

Known Issues

Summary of Changes in 4.3.6.4

Resolved

Known Issues

Summary of Changes in 4.3.6.3

Resolved

Known Issues

Summary of Changes in 4.3.6.2

Resolved

Known Issues

Summary of Changes in 4.3.6.1

Resolved

Known Issues

Summary of Changes in 4.3.6

Resolved

Known Issues

Summary of Changes in 4.3.5.2

Resolved

Known Issues

Summary of Changes in 4.3.5.1

Resolved

Known Issues

Summary of Changes in 4.3.5

Resolved

Known Issues

Summary of Changes in 4.3.4.6

Resolved

Known Issues

Summary of Changes in 4.3.4.5

Resolved

Known Issues

Summary of Changes in 4.3.4.4

Resolved

Known Issues

Summary of Changes in 4.3.4.3

Resolved

Known Issues


Summary of Changes in 4.3.4.2

Resolved

Known Issues

Summary of Changes in 4.3.4

Resolved

Known Issues

Summary of Changes in 4.3.3.1

Resolved

Known Issues

Summary of Changes in 4.3.3

Resolved

Known Issues


Summary of Changes in 4.3.2.2

Resolved

  • 6785 – Resolved issue where excessive number of threads were created by Jersey Client causing issues with memory resources.
  • 6764 – Resolved issue where due to network issues, client connections were not cleared after clients were disconnected thereby causing the license policy to reject connections for new clients. 

Known Issues

  • 4984 - Port 9520 is no longer valid.  Actual IP address will show versus the loopback one.
  • 5477 - When user kills Master Orchestrator and Replica Orchestrator, some caches in Region 1 return "OrchestratorAlive" to be "true".

Summary of Changes in 4.3.2.1

Resolved

  • 6569 – Resolved startup error when terracotta is launched from wrapper script or Command Central
  • 6636 - Resolved memory leak issue caused by Jersey 2.6 client listeners

 Known Issues

  • 4984 - Port 9520 is no longer valid.  Actual IP address will show versus the loopback one.

  • 5477 - When user kills Master Orchestrator and Replica Orchestrator, some caches in Region 1 return "OrchestratorAlive" to be "true".

Summary of Changes in 4.3.2

Resolved

Known Issues

  • 4984 - Port 9520 is no longer valid.  Actual IP address will show versus the loopback one.
  • 5477 - When user kills Master Orchestrator and Replica Orchestrator, some caches in Region 1 return "OrchestratorAlive" to be "true".

Summary of Changes in 4.3.1.2

Resolved

Known Issues

Summary of Changes in 4.3.1.1

Resolved

Known Issues

Summary of Changes in 4.3.1

Resolved

Known Issues

Summary of Changes in 4.3.0.1

Resolved

Known Issues

Known Issues in 4.3.0