Problem Report: when exceeded idle time

ScottMattes

Member³
PLSD 10.0.5
Win 7
Oracle 11

So I have a Test Window open and a debug session going. It is taking so long that I start looking at something else. Eventually I come back it looks like the debug session is still going so I clicked the Break button and up comes an error window telling my that I exceeded idle limit and my connection to the DB has been closed. But the Test Window does not reset to a non-running state (Break button is still active, status still shows Executing... and I cannot close the Test Window or close PLSD.

PLSD seems to know to tell me that connection was closed due to idle time exceeded, I don't understand why it freezes up like this instead of just going back to a non-running state.
 
We'll check it out. The workaround is obviously to remove the maximum idle time from your resource profile. That's not very useful in a development environment.
 
Back
Top