Rank: Newbie
Groups: Member
Joined: 10/14/2015
Posts: 7
|
Our web application has been running fine in Windows Azure for years. I use Visual Studio 2013 and EO.2013 (pdf). Recently I got a new PC and reinstalled my development software including VS 2013.
One of the differences is that Microsoft Azure Tools was upgraded from 2.3 to 2.9.
I’m able to run my project fine on my new PC however when I deploy it to Azure I start getting exceptions. The exceptions are thrown by either the merge, save or clone functions. Always the same exception (thread was being aborted) but not always failing on the same function.
Can you offer any insight as to what might be going on or how I can fix this?
Below are some example stack traces for all three functions:
********** Save **********
Exception Type: System.Threading.ThreadAbortException
Exception: Thread was being aborted.
Stack Trace:
at System.GC._Collect(Int32 generation, Int32 mode)
at EO.Pdf.Internal.h8.a.a(Boolean A_0)
at EO.Pdf.Internal.h8.a.a(h8 A_0, Byte[] A_1)
at EO.Pdf.Internal.h8..ctor(Byte[] A_0)
at EO.Pdf.Internal.h4.a(Byte[] A_0)
at EO.Pdf.Internal.h4.c(Byte[] A_0)
at EO.Pdf.Internal.et.a.a(et A_0, Random A_1)
at EO.Pdf.Internal.et.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Save(Stream stream)
at EO.Pdf.Internal.m9.b()
at EO.Pdf.Internal.m9.h()
at EO.Pdf.PdfField.b()
at EO.Pdf.Internal.kb.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Save(Stream stream)
********** Merge **********
Exception Type: System.Threading.ThreadAbortException
Exception: Thread was being aborted.
Stack Trace:
at System.GC._Collect(Int32 generation, Int32 mode)
at EO.Pdf.Internal.h8.a.a(Boolean A_0)
at EO.Pdf.Internal.h8.a.a(h8 A_0, Byte[] A_1)
at EO.Pdf.Internal.h8..ctor(Byte[] A_0)
at EO.Pdf.Internal.h4.a(Byte[] A_0)
at EO.Pdf.Internal.h4.c(Byte[] A_0)
at EO.Pdf.Internal.et.a.a(et A_0, Random A_1)
at EO.Pdf.Internal.et.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Save(Stream stream)
at EO.Pdf.Internal.m9.b()
at EO.Pdf.Internal.m9.h()
at EO.Pdf.PdfField.b()
at EO.Pdf.Internal.kb.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Merge(PdfDocument[] docs)
********** Clone **********
Exception Type: System.Threading.ThreadAbortException
Exception: Thread was being aborted.
Stack Trace:
at System.GC._Collect(Int32 generation, Int32 mode)
at EO.Pdf.Internal.h8.a.a(Boolean A_0)
at EO.Pdf.Internal.h8.a.a(h8 A_0, Byte[] A_1)
at EO.Pdf.Internal.h8..ctor(Byte[] A_0)
at EO.Pdf.Internal.h4.b(Byte[] A_0)
at EO.Pdf.Internal.h4.d(Byte[] A_0)
at EO.Pdf.Internal.et.a.a(et A_0, Random A_1)
at EO.Pdf.Internal.et.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Save(Stream stream)
at EO.Pdf.Internal.m9.b()
at EO.Pdf.Internal.m9.h()
at EO.Pdf.PdfField.b()
at EO.Pdf.Internal.kb.b()
at EO.Pdf.PdfDocument.a()
at EO.Pdf.PdfDocument.Clone(Int32 fromPage, Int32 pageCount)
at EO.Pdf.PdfDocument.Clone()
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Hi,
This appears to be that the Clone/Merge/Save takes too long which causes Azure to kill the request. So you may want to check the time out value settings (for example, if this runs in an ASP.NET application, then ASP.NET would have a time out value indicating how long a page can take to run) and adjust it.
Thanks!
|
Rank: Newbie
Groups: Member
Joined: 10/14/2015
Posts: 7
|
Thank you for the suggestion, it worked!
For reference in case anyone else runs into a similar Azure issue:
Increasing the timeout through the web.config file resolved this for me. Example: Under the <system.web> section, I set the executionTimeout value to 300 seconds:
<httpRuntime executionTimeout="300" />
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Great. Glad to hear that it worked for you!
|