JDK-8299901 : java/nio/channels/Channels/ReadXBytes.java failed with unexpected exit code 137
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.nio
  • Affected Version: 21
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86_64
  • Submitted: 2023-01-10
  • Updated: 2023-01-10
  • Resolved: 2023-01-10
Related Reports
Duplicate :  
JDK-8289470 - java/nio/channels/Channels/ReadXBytes.java failed with "exit code: 137"
Description
It looks like a resource limit was reached while executing this test

----------messages:(7/372)----------
command: testng -Xmx12G ReadXBytes
reason: User specified action: run testng/othervm/timeout=900 -Xmx12G ReadXBytes 
started: Tue Jan 10 08:29:54 UTC 2023
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules java.base --add-exports java.base/jdk.internal.util=ALL-UNNAMED
finished: Tue Jan 10 08:30:15 UTC 2023
elapsed time (seconds): 20.643
----------configuration:(4/111)----------
Boot Layer
  add modules: java.base                   
  add exports: java.base/jdk.internal.util ALL-UNNAMED

----------System.out:(9/433)----------
Seed from RandomFactory = 3821886816863103978L
test ReadXBytes.readAllBytes(1): success
test ReadXBytes.readAllBytes(120): success
test ReadXBytes.readAllBytes(28846): success
test ReadXBytes.readAllBytes(885268): success
test ReadXBytes.readAllBytes(1626682542): success
test ReadXBytes.readAllBytesAtEOF(): success
test ReadXBytes.readAllBytesFromBeyondMaxLengthFile(): success
test ReadXBytes.readAllBytesFromEmptyFile(): success


top shows

----------------------------------------
[2023-01-10 08:30:17] [/bin/top, -b, -n, 1] timeout=20000
----------------------------------------
top - 08:30:17 up 42 days, 12:11,  0 users,  load average: 7.44, 7.50, 7.77
Tasks: 261 total,   1 running, 260 sleeping,   0 stopped,   0 zombie
%Cpu(s): 21.6 us, 62.8 sy,  0.0 ni,  6.9 id,  0.9 wa,  0.0 hi,  6.1 si,  1.7 st
MiB Mem :  23751.1 total,  14888.4 free,   8284.5 used,    578.1 buff/cache
MiB Swap:   4096.0 total,      0.0 free,   4096.0 used.  14850.0 avail Mem 


zero swap is free

limits

[2023-01-10 08:30:16] [/bin/bash, -c, ulimit -a] timeout=20000
----------------------------------------
core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 94679
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 16384
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 94679
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

There were 3 other tests executing

Channels/TransferTo -- which I think might be a bit of  memory hog
AsynschronousSocketChannel/StressLoopback
AsynschronousSocketChannel/Basic

most likely an OCI node infra config issue
Comments
it is usually the OS's choice, the process has requested additional memory which could not be fulfiiled, even though it is virtual memory and there is a significant amount of physical memory available, which results in the process being terminated (SIGKILL). But swap at zero would be indicative of a resource expansion issue.
10-01-2023
Exit code 137 so looks like something killed the process.
10-01-2023