**Describe the bug** Running the realtime reporter from the SQL Developer extension produces sometimes no output due to a `ORA-00001: unique constraint (UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_INFO_TMP_PK) violated` **Provide version info** ``` 19.0.0.0.0 19.0.0 PL/SQL procedure successfully completed. UT_VERSION ------------------------------------------------------------ v3.1.8.3169-develop BANNER BANNER_FULL BANNER_LEGACY CON_ID -------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------------------------------------------------------------------- -------------------------------------------------------------------------------- ---------- Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production 0 Version 19.4.0.0.0 PARAMETER VALUE ------------------------------ ---------------------------------------------------------------- NLS_LANGUAGE ENGLISH NLS_TERRITORY SWITZERLAND NLS_CURRENCY SFr. NLS_ISO_CURRENCY SWITZERLAND NLS_NUMERIC_CHARACTERS .' NLS_CALENDAR GREGORIAN NLS_DATE_FORMAT DD.MM.YYYY HH24:MI:SS NLS_DATE_LANGUAGE ENGLISH NLS_SORT BINARY NLS_TIME_FORMAT HH24:MI:SSXFF NLS_TIMESTAMP_FORMAT DD.MM.RR HH24:MI:SSXFF PARAMETER VALUE ------------------------------ ---------------------------------------------------------------- NLS_TIME_TZ_FORMAT HH24:MI:SSXFF TZR NLS_TIMESTAMP_TZ_FORMAT DD.MM.RR HH24:MI:SSXFF TZR NLS_DUAL_CURRENCY SF NLS_COMP BINARY NLS_LENGTH_SEMANTICS BYTE NLS_NCHAR_CONV_EXCP FALSE 17 rows selected. PORT_STRING ------------------------------------------------------------ x86_64/Linux 2.4.xx ``` **Information about client software** utPLSQL for SQL Developer 1.0.0 (or current development version) **To Reproduce** 1. Run a small test in SQL Developer's realtime reporter 2. Rerun test 3. Repeat step 2 until the test is not executed anmore, you get an `initializing...` message for In the SQL Developer logs I find the following: ``` 2019-07-28 11:00:51 SEVERE org.utplsql.sqldev.runner.UtplsqlRunner: Error while producing events for reporter id 1c8f3d5e77a64bbdb523d52c91c47e72: PreparedStatementCallback; SQL [DECLARE l_reporter ut_realtime_reporter := ut_realtime_reporter(); BEGIN l_reporter.set_reporter_id(?); l_reporter.output_buffer.init(); sys.dbms_output.enable(NULL); ut_runner.run( a_paths => ut_varchar2_list( 'PLSCOPE.test_dd_util.test_get_view_source' ), a_reporters => ut_reporters(l_reporter) ); sys.dbms_output.disable; END; ]; ORA-00001: unique constraint (UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_INFO_TMP_PK) violated ORA-06512: at "UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_BASE", line 32 ORA-06512: at "UT3_LATEST_RELEASE.UT_OUTPUT_REPORTER_BASE", line 34 ORA-06512: at line 4 ; nested exception is java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_INFO_TMP_PK) violated ORA-06512: at "UT3_LATEST_RELEASE.UT_OUTPUT_BUFFER_BASE", line 32 ORA-06512: at "UT3_LATEST_RELEASE.UT_OUTPUT_REPORTER_BASE", line 34 ORA-06512: at line 4 ``` as a consequence of this failure the consumer thread does not find result rows. **Expected behavior** Repeat test runs without technical issues.