Bug Report + Feature Request – Incorrect session state indicators and missing reconnect option after connection loss

[adrian_star]

Hello,
I would like to report an issue related to session state handling in PL/SQL Developer, along with a suggested usability improvement.

​

Bug description​

In situations where the database session is lost (e.g., due to network issues), the application does not immediately reflect the disconnected state in the user interface.

Observed behavior:

• The connection appears to be active at first glance
• In the top bar (connection/session indicator), the session still looks valid
• In the ribbon under the Session section, buttons such as:
  • Execute
  • Commit
  • Rollback
  • remain enabled (all buttons are active)

This creates a misleading impression that:

• The session is still active
• There may be uncommitted changes in the database

Only after attempting an action does the user receive an error indicating that the connection has been lost.

Why this is a problem​

This behavior may lead to:

• Confusion about the actual session state
• Incorrect assumptions about pending transactions
• Potential user errors (e.g., attempting to commit/rollback when no session exists)

Expected behavior​

When the session is no longer valid:

• Session-related actions (Execute, Commit, Rollback) should be:
  • Disabled or
  • Visually marked as inactive / invalid (e.g., grayed out or highlighted as error state)
• The connection/session indicator should clearly reflect the disconnected state

Feature Request – Improved reconnection workflow​

To improve usability, I would also suggest enhancements in the Connections window:

• Add a context menu option:
  • “Reconnect”
  • or
• Automatically switch the existing option to:
  • “Connect” when the session is inactive

This would allow users to quickly restore their session without needing to re-navigate or manually reselect the connection (in the ribbon under the Session section).

​

Benefits​

These improvements would:

• Provide clear and immediate feedback about connection state
• Reduce user confusion and potential mistakes
• Improve reliability of UI indicators
• Streamline reconnection workflow after network interruptions

This issue impacts everyday usability.
Thank you for reviewing this report and considering the proposed improvements.


Best regards,
Adrian

 

[Marco Kalter]

Can you go to Preferences > Oracle > Connection, and check if the "Check connection" and "Check all sessions" options are enabled? If not, can you enable it and try again?

 

[adrian_star]

In my case both options was disabled. I've activated them. When the connection is lost, the 'Commit' and 'Rollback' buttons activate.