-
Bug
-
Resolution: Fixed
-
P3
-
11.0.19, 17.0.7-oracle, 24
-
b25
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8348201 | 21.0.7 | Paul Hohensee | P3 | Resolved | Fixed | master |
When improving the container information in JDK-8287011, the values for limit and max for kernel memory got mixed up. Code looks like this:
```
OSContainer::print_container_helper(st, kmem_usage, "kernel_memory_usage_in_bytes");
OSContainer::print_container_helper(st, kmem_limit, "kernel_memory_max_usage_in_bytes");
OSContainer::print_container_helper(st, kmem_max_usage, "kernel_memory_limit_in_bytes");
```
This information is displayed in hs_err-files and it gives the impression that we've hit the kernel limit (if we are at peak usage) even though we haven't.
```
OSContainer::print_container_helper(st, kmem_usage, "kernel_memory_usage_in_bytes");
OSContainer::print_container_helper(st, kmem_limit, "kernel_memory_max_usage_in_bytes");
OSContainer::print_container_helper(st, kmem_max_usage, "kernel_memory_limit_in_bytes");
```
This information is displayed in hs_err-files and it gives the impression that we've hit the kernel limit (if we are at peak usage) even though we haven't.
- backported by
-
JDK-8348201 Kmem limit and max values swapped when printing container information
- Resolved
- relates to
-
JDK-8287011 Improve container information
- Resolved
- links to
-
Commit(master) openjdk/jdk21u-dev/ab69b0d1
-
Commit(master) openjdk/jdk/6cdebf0e
-
Review(master) openjdk/jdk11u-dev/2988
-
Review(master) openjdk/jdk17u-dev/3227
-
Review(master) openjdk/jdk21u-dev/1341
-
Review(master) openjdk/jdk/21906
(3 links to)