You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2002/04/22 14:02:34 UTC
DO NOT REPLY [Bug 6395] -
FOP stalls when it is executed by java application
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6395>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6395
FOP stalls when it is executed by java application
j3322ptm@yahoo.de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From j3322ptm@yahoo.de 2002-04-22 12:02 -------
The reason is probably that the stderr (or stdout) buffer is full. FOP
writes by default quite a few logging messages. You'll have to read them
or otherwise discard them. If the buffer is full,FOP hangs in an attempt
to write some log output. If the invoking java application is closed, so
are the file handles piping stderr and stdout output, and FOP resumes work.
It is recommended not to use exec() for executing FOP, look at the guidelines
how to embed FOP directly into your Java application.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org