Ok.  So investigating this I figured out that the logging automatically uses
log4j when it's available...  But my default logging level was set to debug,
hence the millions of lines of log output.  Lol.  Long day researching what
turned out to be a far simpler problem than I imagined...

In any case, thanks for the help

~Brian

___________________________________________________
Brian Trezise
Staff Software Engineer
IntelliData, Inc
22288 E Princeton Dr
aurora, colorado 80018
T: 720.524.4864
[EMAIL PROTECTED]


-----Original Message-----
From: Brian Trezise [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 21, 2008 9:36 AM
To: [email protected]
Subject: RE: Logging question

Ok... We use Log4j logging on all of our systems, and I'm familiar with
configuring it within my applications; however I'm not sure how to tell FOP
to use it.  Do I need to write a custom listener or something to that
effect?

___________________________________________________
Brian Trezise
Staff Software Engineer
IntelliData, Inc
22288 E Princeton Dr
aurora, colorado 80018
T: 720.524.4864
[EMAIL PROTECTED]


-----Original Message-----
From: Jeremias Maerki [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 21, 2008 2:04 AM
To: [email protected]
Subject: Re: Logging question

I'm afraid, Joerg is on the wrong track here. "No route found!" is a
log message from the Dijkstra shortest-path algorithm implementation in
Apache XML Graphics Commons. It has nothing to do with DTD access on the
internet.

This whole thing is really about properly configuring the logging
environment:
http://xmlgraphics.apache.org/fop/0.95/embedding.html#basic-logging

So, how you configure it largely depends on the logging subsystem that
is used by Apache Commons Logging. It's a good idea to familiarize
yourself with:
http://commons.apache.org/logging/commons-logging-1.0.4/docs/guide.html

The easiest is probably to use java.util.logging. I've written a Wiki
page some time ago demonstrating the basics:
http://wiki.apache.org/xmlgraphics-fop/HowTo/SetupJDK14Logging

On 21.08.2008 00:15:57 J.Pietschmann wrote:
> Brian Trezise wrote:
> > Using FOP 0.95, I'm generating a single-page PDF document in a web
server,
> > and it's taking nigh on 20 seconds to generate.  When I prototyped this
it
> > was running<  1 second.  The only difference is that when I prototyped I
> > generated the Source object from a File, and on the webserver I'm
pulling it
> > from a runtime-generated org.jdom.Document that I converted to a
> > ByteArrayInputStream.
> >
> > I have a suspicion that a part of the problem is that for some reason
using
> > the ByteArrayStream as an input I'm getting thousands of lines in my log
> > file.
> Very unlikely.
> 
> The problem is probably here:
> > 20 Aug 2008 15:46:58,937 - No route found!
> 
> I suspect you include a DTD in your SVGs, FOP tries to
> load the DTD from the w3c web server, but a firewall or
> something blocks this, and FOP waits for the network stack
> timeout.
> You can check this if you can log in onto the server and
> try a ping or traceroute to www.w3.org.
> 
> You can try the following solutions:
> - Write or get an EntityResolver which provides an empty DTD,
>   or the SVG DTD from local storage (if you rely on the declaration
>   of the xmlns:svg in the DTD), and set this on the XML parser you
>   use for the SVGs. The details are somewhat gory but you should
>   find them in the mail archives.
> - Remove the DOCTYPE from your SVGs (don't do this if you rely on
>   the declaration of the xmlns:svg in the DTD)
> - Ask the network staff to unblock access to www.w3.org (not
>   recommended)
> 
> J.Pietschmann
> 



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to