Actually it doesn't work. Do you have any idea how can I help you find out the problem?
how it behaves:
When a user continuously use the PLSQL Developer, then it works. But when user leaves PLSQL Developer without any interaction (and mostly minimize the main program window) and then returns back after let say 15 minutes, after first few "keyboard stroke" applications freezes - it is obviously trying to reach database (e.g. code asistant activates and "try to help" ), but connection is invalid (i'm sure it was closed by oracle due to inactivity) and it takes a long time (tens seconds) application "find out" that connection is invalid.
It should be solved using "Check connections" and "Check all sessions" , but as I said, it does not help.
But, if user leaves PLSQL Developer without any interaction, then returns back and immediately clicks on "Sessions-Log Of - All" and then reconnect the session, there's no lag, all operations (including reconnect) is very quick.
So, based on this observation, Im convinced "Check connections" and "Check all sessions" does not work as intended.