I hear ya, damn little Sprites! Maybe you could look at other PDF generating tools? Jasper reports, iText, Birt, and OpenReports are a few free OS ones. Maybe way out of your scope, but thought I'd suggest.
I setup a OpenReports server recently for evaluation. Its pretty kewl. Are your reports complex with graphs and such? If not, For a excel style basic columnar report, once you have your SQL in hand, it takes about five minutes to setup the report in OpenReports that is HTML based with pagination, has export to xls, csv, and pdf....and can be schedule to be sent via email in pdf, csv, or xls format by the end user. I have not got it to run under JRun yet, but setting up under Tomcat is well...cake. Another thing maybe for your users...instead of generating the report on demand, setup a scheduled report that can be generated at night and sent via email. Maybe a delay in satisfaction, but a better chance at 100% satisfaction, eh? DK On 5/12/06, Stephen Cassady <[EMAIL PROTECTED]> wrote: > Hey Douglas - > He he he. The better option is absolutely being performed (lol, I wouldn't > understand anyone who didn't attempt to resolve the problem first, and then > build a secondary solution in place of fixing the first). > > The issue seems to be isolated to PDF creation through ColdFusion. Standard > Edition (so not threaded) - building some PDFS of hundreds of pages, > generating creation times of minutes. Although users are asked to "be > patient", reloading the request page in the middle of the request, or > restarting the PDF creation does happen (or, more than one user creating > large PDF requests at one time). Given enough requests, the poor little Java > Sprite (not a technical term - just my imaginary worker building the PDF) > looks at the backlog and just plain walks off the job, taking down JRun with > him. > > The solution may require Enterprise, but there is a cost barrier that can > not be addressed at this time. > > There are some environmental issues for JRun (memory et. all) that are being > looked at as well at this moment. I'll double check against the list of good > reads that you've provided (and thank you!) > > So, given an understanding of the problem, we've already isolated some of > the PDF production by user role, limiting some of the bigger creation > scripts to specific users. > > Now I'm going beyond the action of addressing the issue within the > limitations I have, and would like to figure out a process to restart JRun > if/when this happens again. > > Unfortunately I don't have a reasonable enough knowledge of Java or querying > the server for a responsive JRun (note, the service is still running, just > non-responsive) and then restart service. > > Alas, > Stephen Cassady > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:240315 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
