I suspect that the embedding of the full font file is not thread safe, only
the subset. I'll check it out.
Paulo
On Wed, May 28, 2014 at 11:02 AM, iText mailing list wrote:
> On 5/28/2014 11:11 AM, Kostas wrote:
>
> Note that we are using iTextSharp version 5.4.5.0.
>
>
> Hmm... That's strang
On 5/28/2014 11:11 AM, Kostas wrote:
Note that we are using iTextSharp version 5.4.5.0.
Hmm... That's strange. I expected you to say it was a version predating
5.4.2.0 because that's when we made the FontFactoryImp class threadsafe.
---
On 5/28/2014 10:31 AM, Kostas wrote:
> We are using iTexSharp in an ASP.NET MVC web site and we have noticed
> that when two requests arrive that utilize the same iTextSharp
> functionality we get an exception.
Which version of iTextSharp are you using?
--
Note that we are using iTextSharp version 5.4.5.0.
From: Kostas [mailto:k...@dataverse.gr]
Sent: Wednesday, May 28, 2014 11:32 AM
To: itext-questions@lists.sourceforge.net
Subject: [iText-questions] Problems when using iTextSharp in a multithreaded
application.
We are using iTexSharp in
We are using iTexSharp in an ASP.NET MVC web site and we have noticed that
when two requests arrive that utilize the same iTextSharp functionality we
get an exception.
No apparent problem exist when testing in one request at a time.
Here is the exception:
System.Reflection.TargetInvocationExc
