Please, investigate possible flaky test which was found for example in:
https://master-jenkins-csb-amq-clients-qe.apps.ocp-c1.prod.psi.redhat.com/view/AMQ_Clients/job/tests/job/linux/job/dtests-amq-clients-java/1404/
... [16:58:52] [INFO] dtestlib.Test :: 95/100 JAMQClients111Tests/test_connect_to_wrong_port_with_short_connect_timeout [tst/warn/fail/err/abrt/skip/flaky_cnt:997/40/0/0/0/0/0, dur:3813.1] [16:58:53] [PASS] dtestlib.Test :: Ping Services ['amqp/5672:True', 'openwire/61616:True', 'stomp/61613:True', 'hornetqcore/5445:True', 'web/8161:True', 'mqtt/1883:True', 'jmx/1099:True'] # result:True (exp. True), dur.:-1.00 [16:58:53] [PASS] dtestlib.Test :: Pre-Check test environment (exp. True) # result:True (exp. True), dur.:-1.00 [16:59:00] [WARNING] dtestlib.Test :: [root@10.0.135.235]$ /opt/miniconda3/envs/tn/bin/python3 -u /var/dtests/node_data/clients/cli_wrapper.py -DDTESTS_PID=13366 -DC_KILLTIME=30 -DC_HANG_ANALYSIS_ENA=0 -DC_CRASH_ANALYSIS_ENA=0 -DC_CRASH_FILE_DELETE_ENA=0 java -jar /var/dtests/node_data/clients/aac1.jar sender --timeout 2 --log-msgs dict --broker-uri 'failover:(amqp://10.0.135.235:1883)?jms.connectTimeout=1&failover.maxReconnectAttempts=1&failover.startupMaxReconnectAttempts=1' --conn-auth-mechanisms PLAIN --conn-username admin --conn-password admin --count 1 # ecode:1 (exp. False), dur.:6.62 [16:59:00] [FAIL] dtestlib.Test :: Client should fail in less than 5 seconds # result:False (exp. True), dur.:-1.00 err_cnt:1 [16:59:00] [WARNING] dtestlib.Test :: Client should throw java.io.IOException # result:True (exp. True), dur.:-1.00 ...
The test fails all three times. It is not clear if this can happen only on specific OSes/java versions.