Open smlambert opened 1 year ago
Issue is that this machine cant create the jmx/rmi agent to connect too..
java -Xmx256m -Djavax.net.ssl.keyStore=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/src/test.jlm/net/adoptopenjdk/test/jlm/testkeys -Djavax.net.ssl.trustStore=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/src/test.jlm/net/adoptopenjdk/test/jlm/testkeys -Djavax.net.ssl.keyStoreType=JKS -Djavax.net.ssl.trustStoreType=JKS -Djavax.net.ssl.keyStorePassword=passphrase -Djavax.net.ssl.trustStorePassword=passphrase -Dcom.sun.management.jmxremote.password.file=/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/tmp/jmxremote.password -XX:+UseCompressedOops -classpath /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/aqa-systemtest/openjdk.test.jlm/bin:/home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/jvmtest/system/systemtest_prereqs/junit/junit.jar net.adoptopenjdk.test.jlm.remote.ClassProfiler server /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/results/scls_server.log /home/jenkins/workspace/Test_openjdk11_hs_sanity.system_s390x_linux/aqa-tests/TKG/output_16763999393111/TestJlmRemoteClassAuth_0/20230214-191102-TestJlmRemoteClassAuth/results/scls_server.csv auth controlRole control1 localhost 1234
Cannot connect to port localhost:1234 , even though no firewall is running.
I'm curious - does that command line work ok elsewhere? It has localhost 1234
at the end of it but when I had a quick play yesterday localhost
seemed ok - it was only access via the external interfaces IPs that were being blocked (which is what the original failure description has) so I'm somewhat surprised it fails. Are you sure that the thing listening on 1234 is started by the test automatically? Does that command work on "known good" machines?
I dug the command out of the test run output, as thats the point it was hanging...
To make it easy for the infrastructure team to repeat and diagnose, please answer the following questions:
All TestJlmRemote system test targets and NioLoad system test targets fail (see TRSS view)
Test_
job on https://ci.adoptopenjdk.net which showed the failure https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_sanity.system_s390x_linux/679/Any other details: