your - sql keepalive
When SQL Developer is idle I lose my connection (4)
My problem is this: I am running Oracle 10G on windows 98 on a virtual machine using VMWare on my desktop computer. I can connect to several users (SYS, HR, OE, ... ) with SQL Developer (which is on my desktop not on the virtual machine) but if a don't run any SQL statement for a short while, say about 2 minutes, I lose my connection and get an error like connection closed or IO-fault:connection reset by peer.
Could this have anything to do with the sp_reset_connection?
When I open SQL Plus on my virtual machine itself I don't lose the connection at all, even if it has been idle for 30 minutes or longer. So now I'm thinking there could be a problem between the Virtual Machine and my desktop computer. Before this all worked fine.
I tried closing recently installed anti-malware apps without any result. Anybody has an idea what I could do to fix this problem?
Kind regards, Veek
I stumbled upon the Keep-ALive Extension and tried it as well but without succes. Standard it is set to a 2 minute interval. I've changed this value to 1 and to 60 minutes but as soon as I stop running statements for a short while I lose my connection. There must be something else. I've already installed the newest SQL Developer version but still it is the same. (I did import the settings from my earlier release maybe I have to try without importing them.) Any other suggestions perhaps?
Go to Tools > Monitor Sessions... and select your Connection. Set the refresh value to 60 (seconds).
While monitoring, your connection will not be lost.
Oracle SQL Developer Version 18.104.22.168
MinChen Chai has created Keep-Alive Extension exactly for your situation: https://sites.google.com/site/keepaliveext
It will continually send TCP keep-alive packets and prevent server disconnection by inactivity timeout.
This extension works for SQL Developer 4:
DISCLAIMER: I'm the developer of the extension. I hope the answer is not considered advertising, because this extension is open source (and the previous non-open-source extensions were accepted as an answer).