Open JustDerb opened 11 years ago
Started initial stress test at 12:24am. Will run overnight and log when first exceptions noticed.
Error thrown sometime this morning, just witnessed now (11:16am).
Exception thrown: IOException (InnerException = SocketException) in ImapClient.cs
, line 1987.
Server still running as of now. ( WOOT! )
Received massive stack of IOExceptions in the same place as before. Sometime between 3:10 and 4:30. Closing the server was the only way to bypass all the exceptions in the debugger.
We should really consider logging this to the DB/Console. The DB has a field for the current timestamp which we can use to get better estimates on total runtime.
If the debugger is attached, it will halt on the exception when Gmail closes it. This is intended, but the exception just kills the thread, which in less then 10 min will end up being spawned again. This is by design since we do not want to edit the S22 library (It would require a lot of changes)
Stress test beginning at 18:48:05 (precisely).
Ended test around 22:20 due to SqlException with invalid input for pluginkeyvalue
table.
Issue has been taken care of (as of 52e6bafc94731e02066552b7aa7aa1f64e91dddc, 515c649b7bca2bdd9a3179821dbf450f63cdce35).
Stress test beginning at 22:35:44 (precisely).
Stress tested. Looks all good!
"vshost.exe crashed" after attempting to run server detached from debugger. Logs indicate last attempt to log out of/into GMail was around 3:22:27.
The primary IOException being thrown and it's location. The source file is ImapClient.cs
.
Gmail with IMAP IDLE shows that you need to log back in every 10 minutes to avoid a stale connection. Testing now to see if this is the case.