Connection issue with utplsql-cli and multiple reporters

[al-hexagon]

2024-11-15 06:40:07 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_TFS_JUNIT_REP_NEW, ID: 3CD0F310D73B47348A0747748AF24391
2024-11-15 06:40:12 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_COVERAGE_COBERTURA_REP_NEW, ID: 79B64FFB0A0B4935A307DD326FD56013
java.sql.SQLTimeoutException: ORA-01013: user requested cancel of current operation

	at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:1157)
	at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:1054)
	at oracle.jdbc.driver.T2CCallableStatement.executeForDescribe(T2CCallableStatement.java:764)
	at oracle.jdbc.driver.T2CCallableStatement.executeForRows(T2CCallableStatement.java:1007)
	at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1205)
	at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3666)
	at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3778)
	at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4251)
	at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1081)
	at org.utplsql.api.outputBuffer.OutputBufferProvider.hasOutput(OutputBufferProvider.java:67)
	at org.utplsql.api.outputBuffer.OutputBufferProvider.getCompatibleOutputBuffer(OutputBufferProvider.java:33)
	at org.utplsql.api.compatibility.CompatibilityProxy.getOutputBuffer(CompatibilityProxy.java:187)
	at org.utplsql.api.reporter.DefaultReporter.initOutputBuffer(DefaultReporter.java:21)
	at org.utplsql.api.reporter.Reporter.init(Reporter.java:50)
	at org.utplsql.cli.ReporterManager.initReporters(ReporterManager.java:95)
	at org.utplsql.cli.RunAction.initReporters(RunAction.java:222)
	at org.utplsql.cli.RunAction.doRun(RunAction.java:71)
	at org.utplsql.cli.RunAction.run(RunAction.java:122)
	at org.utplsql.cli.RunPicocliCommand.run(RunPicocliCommand.java:265)
	at org.utplsql.cli.Cli.runPicocliWithExitCode(Cli.java:47)
	at org.utplsql.cli.Cli.main(Cli.java:17)
Caused by: Error : 1013, Position : 0, Sql = declare    l_result int;begin    begin        execute immediate '       begin            :x := case ' || dbms_assert.simple_sql_name( :1  ) || '() is of (ut_output_reporter_base) when true then 1 else 0 end;       end;'       using out l_result;   end;   :2  := l_result;end;, OriginalSql = declare    l_result int;begin    begin        execute immediate '       begin            :x := case ' || dbms_assert.simple_sql_name( ? ) || '() is of (ut_output_reporter_base) when true then 1 else 0 end;       end;'       using out l_result;   end;   ? := l_result;end;, Error Msg = ORA-01013: user requested cancel of current operation

	at oracle.jdbc.driver.T2CConnection.checkError(T2CConnection.java:1170)
	... 20 more

this happens frequently without any pattern. Typlically it looks like this:

2024-11-15 06:15:07 [main] INFO  org.utplsql.cli.RunAction - 
2024-11-15 06:15:07 [main] DEBUG o.u.c.d.TestedDataSourceProvider - Try connecting jdbc:oracle:oci8:****/****@######
2024-11-15 06:15:09 [main] INFO  o.u.c.d.TestedDataSourceProvider - Use connection string jdbc:oracle:oci8:****/****@#####
2024-11-15 06:15:11 [main] INFO  org.utplsql.cli.RunAction - Successfully connected to database. UtPLSQL core: v3.1.10.3349
2024-11-15 06:15:11 [main] INFO  org.utplsql.cli.RunAction - Oracle-Version: 19.0.0.0.0
2024-11-15 06:15:15 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_TFS_JUNIT_REP_NEW, ID: 0F92B9EA282F4ABBBFD840FFC4AE1886
2024-11-15 06:15:15 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_COVERAGE_COBERTURA_REP_NEW, ID: AB6C473B14A5415789CC9703CCC77B9E
2024-11-15 06:15:15 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_COVERAGE_HTML_REPORTER, ID: 2C1C1B6E9B0F4A26AFBBB7572D0A49F1
2024-11-15 06:15:16 [main] DEBUG org.utplsql.api.reporter.Reporter - Database-reporter initialized, Type: UT_DOCUMENTATION_REPORTER, ID: AFA09F6B1D9D49CDAB19FE02857D4C8F
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.cli.RunTestRunnerTask - Running tests now.
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.cli.RunTestRunnerTask - --------------------------------------
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - TestRunner initialized
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Running on utPLSQL v3.1.10.3349
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Initializing reporters
2024-11-15 06:15:19 [pool-1-thread-1] INFO  org.utplsql.api.TestRunner - Running tests

i added the timeout parameter --ora-stuck-timeout=60 but it doesn't look like that it has any affect.

Interesstingly im running the same sources with same scripts on two different servers. One server is working fine and the other one is failing frequently. The used cdb / pdb is configured identically. The used pdb-base is identically, the servers are hosted on ms-azure and are setup identically. There are no entries in alert.log, no incidents, no crash-dumps, ... nothing. It just looks like an timeout which doesn't follow any pattern.

How can i debug the issue?