DBMS Output capture in SQL Developer under the JDK 17 minimum runtime

Recent SQL Developer releases list JDK 17 as the minimum runtime, moving worksheet behavior onto a newer Java baseline than earlier installations targeted. The DBMS Output pane is one place that boundary shows: it polls a session's DBMS_OUTPUT buffer, and whether it uses repeated GET_LINE calls or a GET_ARRAY batch affects when lines appear and how much of the buffer is drained per poll.

What stays unclear is whether the capture behavior changed because of the JDK baseline, because of a SQL Developer release, or because of the JDBC driver in use. Extension loading adds another variable: extensions built against JDK 8 APIs may not load without a compatibility mode, and a disabled extension could change what the worksheet displays.

Confirm the release and runtime in Help > About, and compare the Java Runtime field with java -version on the machine that launches the tool. A worksheet running DBMS_OUTPUT.PUT_LINE inside a PL/SQL block gives a simple reference point.

• Is the DBMS Output polling change tied to the JDK 17 minimum, or to the SQL Developer release that introduced it?
• Does the behavior differ between a worksheet connection and one using a different JDBC driver?
• Which installations in a mixed-JDK estate can keep the older capture behavior?