Last Modified: Oct 19, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 16.1.6, 16.1.6.1
Opened: Jun 14, 2023 Severity: 4-Minor
Below logs seen in var/log/restjavad-gc.log.0.current 2025-06-30T11:26:44.894-0300: 1016831.746: [GC (Allocation Failure) 319643K->179860K(506816K), 0.0321369 secs] 2025-06-30T11:26:45.425-0300: 1016832.277: [GC (Allocation Failure) 319636K->179846K(506816K), 0.0088917 secs] 2025-06-30T11:26:45.945-0300: 1016832.797: [GC (Allocation Failure) 319622K->179885K(506816K), 0.0081733 secs] 2025-06-30T11:26:46.668-0300: 1016833.520: [GC (Allocation Failure) 319661K->179972K(506816K), 0.0067179 secs]
This log entry alone is harmless and indicates normal JVM memory management. If these occur very frequently (e.g., many per second) and pause times grow longer (hundreds of ms or seconds), or if post-GC usage remains consistently high (>80% of heap),it would indicate an operational impact.
JVM heap has available capacity. A new object allocation request arrives that cannot fit into the current free space in the heap’s young generation (or the relevant memory pool). The JVM triggers a Garbage Collection cycle to free memory.
None
None