To identify the issue, we first need to look at the core dump that’s automatically generated during and JVM crash.
Stack: [0x00007f81746e1111,0x00007f81747e2111], sp=0x00007c82747dc075, free space=2000k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libc.so.6+0xe5281] gaih_inet.constprop.7+0x311
C [libc.so.6+0xe6d1b] getaddrinfo+0x12b
C [libnet.so+0x5e56] Java_java_net_Inet6AddressImpl_lookupAllHostAddr+0x96
j java.net.Inet6AddressImpl.lookupAllHostAddr(Ljava/lang/String;)[Ljava/net/InetAddress;+0 java.base@11.0.13
Next, we can run the following command to further identify if the kubernete cluster is indeed with ipv6 enabled and if artifactory is on ipv6:
bash-4.4$ cat /etc/hosts
# Kubernetes-managed hosts file (host network).
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Netstat command shows artifactory java is on tcp6
bash-4.4$ netstat -tulpn | grep LISTEN
tcp 0 0 127.0.0.1:8046 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8047 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8049 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8086 0.0.0.0:* LISTEN 4350/jf-metadata
tcp 0 0 127.0.0.1:8061 0.0.0.0:* LISTEN 4521/jf-event
tcp 0 0 127.0.0.1:8062 0.0.0.0:* LISTEN 4521/jf-event
tcp 0 0 127.0.0.1:8036 0.0.0.0:* LISTEN 4864/jf-observabili
tcp 0 0 127.0.0.1:8070 0.0.0.0:* LISTEN 4883/node
tcp 0 0 127.0.0.1:8071 0.0.0.0:* LISTEN 5039/jf-integration
tcp 0 0 127.0.0.1:8072 0.0.0.0:* LISTEN 5039/jf-integration
tcp6 0 0 :::8045 :::* LISTEN 5286/java
tcp6 0 0 127.0.0.1:8015 :::* LISTEN 5286/java
tcp6 0 0 :::8081 :::* LISTEN 5286/java
tcp6 0 0 :::8082 :::* LISTEN 4130/jf-router
tcp6 0 0 127.0.0.1:8091 :::* LISTEN 5286/java
tcp6 0 0 127.0.0.1:8040 :::* LISTEN 5286/java
Stack: [0x00007f81746e1111,0x00007f81747e2111], sp=0x00007c82747dc075, free space=2000k
Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libc.so.6+0xe5281] gaih_inet.constprop.7+0x311
C [libc.so.6+0xe6d1b] getaddrinfo+0x12b
C [libnet.so+0x5e56] Java_java_net_Inet6AddressImpl_lookupAllHostAddr+0x96
j java.net.Inet6AddressImpl.lookupAllHostAddr(Ljava/lang/String;)[Ljava/net/InetAddress;+0 java.base@11.0.13
Next, we can run the following command to further identify if the kubernete cluster is indeed with ipv6 enabled and if artifactory is on ipv6:
bash-4.4$ cat /etc/hosts
# Kubernetes-managed hosts file (host network).
127.0.0.1 localhost
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Netstat command shows artifactory java is on tcp6
bash-4.4$ netstat -tulpn | grep LISTEN
tcp 0 0 127.0.0.1:8046 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8047 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8049 0.0.0.0:* LISTEN 4130/jf-router
tcp 0 0 127.0.0.1:8086 0.0.0.0:* LISTEN 4350/jf-metadata
tcp 0 0 127.0.0.1:8061 0.0.0.0:* LISTEN 4521/jf-event
tcp 0 0 127.0.0.1:8062 0.0.0.0:* LISTEN 4521/jf-event
tcp 0 0 127.0.0.1:8036 0.0.0.0:* LISTEN 4864/jf-observabili
tcp 0 0 127.0.0.1:8070 0.0.0.0:* LISTEN 4883/node
tcp 0 0 127.0.0.1:8071 0.0.0.0:* LISTEN 5039/jf-integration
tcp 0 0 127.0.0.1:8072 0.0.0.0:* LISTEN 5039/jf-integration
tcp6 0 0 :::8045 :::* LISTEN 5286/java
tcp6 0 0 127.0.0.1:8015 :::* LISTEN 5286/java
tcp6 0 0 :::8081 :::* LISTEN 5286/java
tcp6 0 0 :::8082 :::* LISTEN 4130/jf-router
tcp6 0 0 127.0.0.1:8091 :::* LISTEN 5286/java
tcp6 0 0 127.0.0.1:8040 :::* LISTEN 5286/java