A recent change made OJP JDBC connection close fully synchronous, increasing close-path latency and coupling caller flow to terminate-session RPC completion. This update restores async close as the default while preserving a configurable synchronous mode.

• Close semantics (driver runtime)

  • Connection.close() now defaults to asynchronous session termination.
  • Added opt-in synchronous behavior via ojp.jdbc.connection.close.synchronous=true.
  • Sync mode preserves prior blocking/error propagation behavior; async mode logs termination failures.

• Configuration surface

  • New constant/property key: ojp.jdbc.connection.close.synchronous (default false).
  • Property is now recognized consistently across:
    • ojp.properties (including datasource-prefixed entries),
    • system properties / environment overrides,
    • DriverManager.getConnection(url, info) Properties.

• Execution model

  • Async termination runs on a dedicated bounded daemon executor (instead of shared common pool) to isolate close-task scheduling.

• Docs + contract updates

  • JDBC configuration docs updated to reflect async-by-default behavior and sync override.
  • Connection/property-loading unit coverage updated for the new close mode toggle.

# default behavior: async close (non-blocking)
ojp.jdbc.connection.close.synchronous=false

# opt in to blocking close semantics
ojp.jdbc.connection.close.synchronous=true

# datasource-scoped override
myApp.ojp.jdbc.connection.close.synchronous=true