Network connection interrupted when PLSQL idle for long time

[Mikio]

I have this issue on some machines where they will lose all network communication when they leave PLSQL Developer open and leave it idle for some time.

It is strange that they first lose connection to other applications; then PLSQL will error out and then all network traffic begins again.

version installed: 8.0.1.1502

 

[Marco Kalter]

To avoid long idle times you can enable the "Check Connection" option (Tools > Preferences > Oracle / Connection).

 

[Mikio]

Ok, will try. But why would this affect the entire machine losing connection to all other applications running on the machine? Is it interrupting the IP stack or something?

 

[jure]

Hi!

This also happens to me, even with "Check Connection" checked.

It happens when you leave a window open which is left inactive for about half an hour (no one executes any commands in it). To me this mostly happens with SQL Window and Command window, but then again these are the types of windows that I use most often.
If a user wants to close such a window it usually takes about 30s to do so. Meanwhile the PL/SQL Developer is not responding to any commands - if user tries to execute any command, it freezes until the inactive window is closed.
If you have multiple inactive windows open the fastest thing is to log off and back on to the database.

To me it also seems this is more reproducible when you connect to a database over a network (i.e. not to a local database on the computer where PL/SQL Developer is running).

This issue has been around for a long time (at least since v.6 of PL/SQL Developer).

I hope this can help you in tracking the issue. This is actually one thing that bothers me and my coworkers the most in PL/SQL Developer.

Cheers,
Jure

 

[6502]

I had this connection timeout problem too while working on a remote Linux server. It appeared no matter what tool I used (tried different IDEs).

The "check connection"-option solved it for me.

Does anybody know whether the origin of this "timeout" is located in the windows client or the remote host?

Regards
Cornel