"Page subsequences exhausted" on some machines but not others

["Karnowski, David" <dk...@etrade.com>]

Hello,

We are getting:
  "Page subsequences exhausted. Using previous subsequence."
on some machines but not others when using the exact same version of FOP,
Java, JAR files, and using the same XML and XSL files.

Any ideas? Could this be due to lack of RAM or some other OS-related
difference between the machines? All our machines are running Solaris.

Here's the error on the two machines where it doesn't work:
	[INFO] FOP 0.20.4rc
	[INFO] building formatting object tree
	[INFO] [1]
	[ERROR] Page subsequences exhausted. Using previous subsequence.
	[INFO] [2]
	Exception in thread "main" java.lang.NoClassDefFoundError
        at org.apache.fop.layout.LineArea.addSpacedWord(Unknown Source)
        at org.apache.fop.layout.LineArea.addText(Unknown Source)
        at org.apache.fop.fo.FOText.addRealText(Unknown Source)
        ...

Here's what happens when we run the exact same command using the exact same
XML & XSL files on the machines where the process works fine:
	[INFO] FOP 0.20.4rc
	[INFO] building formatting object tree
	[INFO] [1]
	[INFO] Parsing of document complete, stopping renderer

Thanks,
David

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

Re: "Page subsequences exhausted" on some machines but not others

["J.Pietschmann" <j3...@yahoo.de>]

Karnowski, David wrote:
> We are getting:
>   "Page subsequences exhausted. Using previous subsequence."
> on some machines but not others when using the exact same version of FOP,
> Java, JAR files, and using the same XML and XSL files.
> 
> Any ideas? Could this be due to lack of RAM or some other OS-related
> difference between the machines? All our machines are running Solaris.

The AWT renderer relies on the local graphic subsystem for some calculations.

> 	[INFO] FOP 0.20.4rc
This is an outdated release known to have some really inconvenient bugs.
You should upgrade.

J.Pietschmann


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

RE: "Page subsequences exhausted" on some machines but not others

[Victor Mote <vi...@outfitr.com>]

Karnowski, David wrote:

> We are getting:
>   "Page subsequences exhausted. Using previous subsequence."
> on some machines but not others when using the exact same version of FOP,
> Java, JAR files, and using the same XML and XSL files.
>
> Any ideas? Could this be due to lack of RAM or some other OS-related
> difference between the machines? All our machines are running Solaris.
>
> Here's the error on the two machines where it doesn't work:
> 	[INFO] FOP 0.20.4rc
> 	[INFO] building formatting object tree
> 	[INFO] [1]
> 	[ERROR] Page subsequences exhausted. Using previous subsequence.
> 	[INFO] [2]
> 	Exception in thread "main" java.lang.NoClassDefFoundError
>         at org.apache.fop.layout.LineArea.addSpacedWord(Unknown Source)
>         at org.apache.fop.layout.LineArea.addText(Unknown Source)
>         at org.apache.fop.fo.FOText.addRealText(Unknown Source)
>         ...
>
> Here's what happens when we run the exact same command using the
> exact same
> XML & XSL files on the machines where the process works fine:
> 	[INFO] FOP 0.20.4rc
> 	[INFO] building formatting object tree
> 	[INFO] [1]
> 	[INFO] Parsing of document complete, stopping renderer

I suppose anything is possible, but I doubt that this is a machine or o/s
difference. I would start by examining whether the XSL files are really the
same. The error you are getting indicates that you are running out of
page-sequence-master children to accommodate your page-sequence, which is a
stylesheet problem. From within the your FOP script, "cat" the stylesheets
to log files & make sure they are really the same. Look also for
<xsl:include> or <xsl:import> elements in your stylesheet that are resolving
to different places on the different machines (eg. files on the local
machine). I'm not sure how to definitively find such a problem, but I would
at least investigate the possibility.

The "NoClassDefFoundError" usually indicates a CLASSPATH problem. I think
this is a separate problem, but may also be triggered by a difference in
environments -- perhaps a script shared by all three machines that is
pointing to local paths that are different between the machines. Again, you
may need to echo some environment variables to your log file to see what is
going on.

Victor Mote


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org