if the connection goes south, all bets are off
there should be a jdbc timeout that tells SQLDev that it's OK to 'give up' on a connection, but that TIMEOUT is VERY long, so as not to drop connections for long running queries.
I looked pretty diligently within SQL Developer to find a "JDBC Timeout" setting but was not able to find it. If I do find it and shorten it, is the theory that there will be a message telling me why it failed to connect? I am only getting a "Succes" message when I "Test" the connection through its properties window.
we don't surface the jdbc settings, b/c they would get folks in trouble
>>telling me why it failed to connect?
no, you would just get a timeout message, faster
I rebooted the Amazon Oracle RDS and all of the sudden SQL Developer was able to connect again. Maybe it would be a good idea for the SQL Developer team to make the JDBC Timeout configurable, as we have basically no options except to continually kill SQL Developer with MS Windows task manager if the connection hangs.
The part that boggles my mind is that I get a "Success" message when I test the DB connection, but then it hangs when I attempt to connect. But this is one of those situations where it is best for me to just move on rather that try to figure out what happened.