|
Thanks for the reply, Duane.
The performance issue isn't really for multiple jobs running the Java,
just one. But they run it over and over.
It's for adding an overlay/watermark to a PDF. That alone I know is
resource intensive. If you've ever seen the PDF spec, adding a single
character means changing almost the entire document, XREF, etc.
Adding a watermark I'm sure is very string intensive too.
What we're seeing is each time this is called, from the same job mind
you, a new little job spawns, then when it's done that job goes away.
That's where I thought the resources might be going. But personally I
believe it's the manipulation of the PDF file itself that's causing
what seems to be a lot of lag. It's just a lot of work!
I did show them how to recompile the JAR files on their system so
hopefully that will help. This is on V6R1 as well.
Brad
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.