It's choking on the log4j. If you change the root logger in framework/base/config/log4j.xml from ALL to INFO, back to normal.
----- Original Message ---- From: Adrian Crum <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, December 10, 2007 11:39:37 AM Subject: Re: FOP Issues So much has changed between trunk and R4 that it would be a very time consuming task to go through a list of changed files to see which one caused the problem. That's why I suggested a profiler - it would spot the culprit right away. Chris Howe wrote: > It helps if one (me) reads before applying a solution. I had applied Christian's patch to trunk and came up empty. I just did a c/o of 4.0 and viola...works OOTB. Adrian, I share your sentiments on the issue. That was the most draining exercise I've gone through with OFbiz in I don't know how long. Are there really that many files where the culprit could be? > > ----- Original Message ---- > From: Adrian Crum <[EMAIL PROTECTED]> > To: [email protected] > Sent: Monday, December 10, 2007 9:44:23 AM > Subject: Re: FOP Issues > > > https://issues.apache.org/jira/browse/OFBIZ-1401 > > Chris Howe wrote: > > >>I am having some trouble with FOP. It appears that performance > > suffers > >> exponentially for each additional page that is written in the body >> (overflowing to the next page). Two pages takes about a minute to > > render. > >> Five pages takes about 10 minutes. Ten pages takes about a half >> hour. Plenty of memory available in the JVM, plenty of CPU > > available as > >> well. It completes the screen renderer quickly and gets stuck in > > the FOP > >> portion. Any hints or OOTB templates that would mimic the page >> overflow that I can test to see if it's choking on my template or if > > it's > >> just choking period? I've tried it with both .93 and .94. >> >> >> > > > > > >
