Hi,
I know this was an error reported a good long while ago (2010) by someone else, but when I have PLSQLDev open and the network is lost, the PLSQL just hangs infinitely. The network reconnects, but PLSQLDev never frees up.

You, Marco, suggested it was the client at fault in that it never returns a response back to PLSQLDev's call.

I know it's probably not a major issue for anyone else in the grand scheme of things, but because I suspend my laptop between sites, I get this issue everytime I bring my laptop back up. Only resolution is to have to kill PLSQLDev in taskmanager and then reopen.

Could a process be set up on a separate thread that periodically checks the network connection, and if down kills off all Oracle processes currently in operation - can't see that this would hurt anything - any transactional processes are already shafted at this point anyway.

Just a thought. Thanks for your time.

+1
I am connecting to various customer DBs using several types of VPN and yes - killing the hanged Developer windows in task manager is my daily routine :-)

Hi,

for me is it not a minor issue. I use multiconnecions. When i work in one window some minutes, and just change to another open window to have a look at, a have to wait and wait for reconnect.

I have the same problem using multiconnections. I find it quicker to disconnect the VPN, which causes PSD to stop/cancel it's connection attempt. I then log off all, reconnect the VPN and then reconnect the sessions.
It's still a pain, but does not take as long as waiting for the hung session to reconnect.

I find this behaviour of PSD very annoying too. PSD should quickly enough detect network disconnections of any form and recover from them. PSD should not freeze forever then, giving the user no other option but to kill it!

Any feedback on this, Marco?

I've also got another scenario - possibly related i'm not sure.

Currently, i'm connected to the office via VPN. I have an RDP session open to a windows 10 Pro VM on the company network.
In PLSQLDev (and only in that), when I run a query, it just freezes PLSQLDev (not responding spinny circle). I'm able to run other programs on that machine as normal at that point.
I have to disconnect from RDP and reconnect and the result of the query will be there waiting.
This happens for every single query run.

It doesn't happen for Oracle SQL Developer.

Still having lost connection = PSD hang issues in 13.0.5.

In my case I'm running Debug against a package when the connection is lost - a pop-up window appears to tell me that the connection is lost.

If I then try to re-login, exit, compile, etc. I get a message telling me that I can't as there is an active window. Shortly after that PSD hangs and I have to kill through the task manager.

Still a problem... how many years will this bug remain unfixed? PL/SQL Dev is a great product, but this bug makes it seem so unstable. Also, I tend to leave a bunch of SQL Windows open with ongoing analyses, don't always remember to save them to a file, and from time to time when I have to do the 'kill and restart' dance, the saved files get lost. So then it becomes more than just a slight nuisance.