Aspose Email unhandled exceptions

Aspose.Email Product Family
1

Hello,

I use Aspose.Email in a window service application. The service create many threads and every thread use Aspose.Email to download email (POP3 and IMAP).
Some customers have reported to me that sometimes the service stops. Checking the Windows event viewer I see two types of recurring errors. This is the log:

Framework Version: v4.0.30319
Description: The process was terminated due to an
unhandled exception.

Exception Info: System.IO.IOException
Stack:
 at
System.Net.Security._SslStream.ProcessWrite(Byte[], Int32, Int32,
System.Net.AsyncProtocolRequest)
 at
System.Net.Security.SslStream.Write(Byte[], Int32, Int32)
 at œ.Œ.Write(Byte[], Int32, Int32)
 at œ.‑.Flush()
 at …Send(., System.String)
 at
Aspose.Email.Pop3.Pop3Client.Disconnect()
 at
Aspose.Email.Pop3.Pop3Client.Dispose(Boolean)
 at Aspose.Email.CredentialsByHostClient.Finalize()


Description: The process was terminated due to an
unhandled exception.
Exception Info:
System.Collections.Generic.KeyNotFoundException
Stack:
 at .ž€.€(.€)
 at .ž€.€()
 at
System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean)
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object, Boolean)
 at
System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext,
System.Threading.ContextCallback, System.Object)
 at
System.Threading.ThreadHelper.ThreadStart()


I’m using the 5.3.0.0 version. Someone have already reported such kind of errors? I might update the libraries, but I would only do if they include fixes for such problems.

Thanks.


2

Hi Alessandro,


Thank you for writing to Aspose support team.

You are using quite an older version and it is recommended that test this issue with the latest library. For trial purpose, you may apply for a temporary license for 30 days to check the complete functionality.

The log provided above is not that much helpful to identify the problem. You may please log the activity as mentioned in this article and share the generated log. We will try to provide assistance as soon as possible.