DO NOT REPLY [Bug 45104] Possible Thread Safety Problem in FOP 0.93

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown DO NOT REPLY [Bug 45104] Possible Thread Safety Problem in FOP 0.93

by Bugzilla from bugzilla@apache.org :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

https://issues.apache.org/bugzilla/show_bug.cgi?id=45104


Anoop Sehdev <anoop.sehdev@...> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |anoop.sehdev@...




--- Comment #3 from Anoop Sehdev <anoop.sehdev@...>  2008-07-18 05:39:07 PST ---
Hi,

We are using FOP 0.20.5. We have recently started noticing that sometimes PDFs
we generate are having problems with font embedding.

Some times the CIDSystemInfo section gets written as follows:

/CIDSystemInfo << /Registry (/CIDSystemInfo << /Registry (Adobe/CIDSystemInfo
<< /Registry (AdobeAdobe)/Ordering (UCS)/Ordering ()/Ordering
(UCSUCS)/Supplement )/Supplement )/Supplement 000 >> >> >>

where as it should be :

/CIDSystemInfo << /Registry (Adobe)/Ordering (UCS)/Supplement 0 >>

It clearly shows that there are threading issues. I am not sure if this issue
also exists in latest version of FOP.

Regards
Anoop Sehdev

(In reply to comment #2)

> I kinda of assumed that there wouldn't be much help available.  But I wanted to
> at least put this out there in case anybody might have seen something similar
> in the past, or in case someone else runs across it in the future.
> We have load tested this project many times, to no avail.  Additionally, we
> identified a few different areas where the data mixup could potentially occur,
> but those were easily tested under heavy load with no negative results.  It
> seems like there's some missing piece to the puzzle that we haven't been able
> to identify yet.  The thinking here is that it might have something to do with
> how FOP handles things when running on WebSphere on a bogged-down mainframe.
> We have occasional CPU spikes, but the majority of these came when we had a
> configuration mixup that caused our CPU to run at 100% at peak times for a
> couple weeks.  Outside of that time frame, we've only had a handful of
> occurrences out of around 230,000 hits.  It's just too few to really get a
> handle on it.  Besides, our company's direction for PDF generation has shifted
> away from FOP.  I'm in the process of rewriting this last project now anyway.
> I was mostly posting this issue in case others had been experiencing anything
> similar or if there was just something glaring that you could point out to me.
> Thanks for your time.  I truly appreciate your reply.
> Best regards--
> John Lulich


--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.