OK, am still getting this exception intermittently, it is unstable and I still cannot pin it down to particular input, but a full stack trace:

May 3, 2007 10:04:57 PM org.apache.fop.cli.Main startFOP
SEVERE: Exception
java.lang.IndexOutOfBoundsException: Index: 23, Size: 18
at org.apache.fop.cli.InputHandler.transformTo (InputHandler.java:168) at org.apache.fop.cli.InputHandler.renderTo (InputHandler.java:115)
        at org.apache.fop.cli.Main.startFOP(Main.java:160)
        at org.apache.fop.cli.Main.main(Main.java:191)

---------

java.lang.IndexOutOfBoundsException: Index: 23, Size: 18
        at java.util.ArrayList.RangeCheck(ArrayList.java:546)
        at java.util.ArrayList.get(ArrayList.java:321)
at org.apache.fop.layoutmgr.PageBreakingAlgorithm.computeDemerits (PageBreakingAlgorithm.java:644) at org.apache.fop.layoutmgr.BreakingAlgorithm.considerLegalBreak (BreakingAlgorithm.java:726) at org.apache.fop.layoutmgr.PageBreakingAlgorithm.considerLegalBreak (PageBreakingAlgorithm.java:309) at org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints (BreakingAlgorithm.java:485) at org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints (BreakingAlgorithm.java:403) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout (AbstractBreaker.java:338) at org.apache.fop.layoutmgr.AbstractBreaker.doLayout (AbstractBreaker.java:263) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout (PageSequenceLayoutManager.java:157) at org.apache.fop.area.AreaTreeHandler.endPageSequence (AreaTreeHandler.java:385) at org.apache.fop.fo.pagination.PageSequence.endOfNode (PageSequence.java:148) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement (FOTreeBuilder.java:378) at org.apache.fop.fo.FOTreeBuilder.endElement (FOTreeBuilder.java:194) at org.apache.xalan.transformer.TransformerIdentityImpl.endElement (TransformerIdentityImpl.java:1101) at org.apache.xerces.parsers.AbstractSAXParser.endElement (Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement (Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl $FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument (Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
        at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xalan.transformer.TransformerIdentityImpl.transform (TransformerIdentityImpl.java:484) at org.apache.fop.cli.InputHandler.transformTo (InputHandler.java:165) at org.apache.fop.cli.InputHandler.renderTo (InputHandler.java:115)
        at org.apache.fop.cli.Main.startFOP(Main.java:160)
        at org.apache.fop.cli.Main.main(Main.java:191)

It seems to happen a lot more often when footnotes get moved (I have my XSLT->FO transform set to turn links into footnotes), but the same footnote can be fine in one place and cause the crash in a different page. I have occasional warnings about paragraph overflows which come and go independent of the crash. The values in the range check are not consistent. The size seems to range from 21-23 and the index from 12-18 lately. I originally got an index of 14 and a size of 12.

Is there a way I can tell what page FOP was processing just prior to the crash or otherwise get an idea of what markup is directly involved?

Sincerely,

Eric Vought

"Three passions, simple but overwhelmingly strong, have governed my life: the longing for love, the search for knowledge, and the unbearable pity for the suffering of mankind."

---Bertrand Russell



Attachment: PGP.sig
Description: This is a digitally signed message part

Reply via email to