> Are you sure a server restart is required after this particular time > out (or whatever it is) is encountered? I am able to simply close and > restart my browser to work around issue 1475. If you have a repro that > requres a server restart, it would potentially indicate the problem is > more serious.
I think Gary found that the issue was due to batch jobs running at midnight each day (which kick any logged-in users out of the system and also seem to kill all DB connections also). ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/
