logging

[2006 IR Open Discussion]

By: Edgar Dollin - edollin

logging

2003-03-17 18:37

I am new to jasperreports and have selected it to build an application with large and complex reporting requirements. Needless to say I am impressed with it's capabilities.

 

Possibly this is getting used to jasper but I really missed control of the system log. It would be nice to trace through a log to see what was happening and when. log4j has gained a tremendous amount of support in the open source community and if desired I would be willing to slowly add logging support (as I debug my own applications of course).

 

Let me know, thanks.

 

Edgar

 

 

 

 

 

By: Suraj Amin - suraj_amin

RE: logging

2003-03-21 22:42

Hi,

 

I need to suppress the compile time debug messages produced by Digester, SAX & MethodUtils.

 

--

Regards,

Suraj Amin

 

Homepage: http://www.geocities.com/suraj_amin/

 

/* I'm a self-made man, but I think if I had it to do over again, I'd call in someone else. */

 

 

 

 

 

 

By: Suraj Amin - suraj_amin

RE: logging

2003-03-24 22:32

Hi,

 

Do I presume that curently there is no way of suppressing the compile time debug messages?

 

--

Regards,

Suraj Amin

 

Homepage: http://www.geocities.com/suraj_amin/

 

/* Living is a constant process of deciding what we are going to do.. */

 

 

 

 

 

 

By: Suraj Amin - suraj_amin

RE: logging

2003-03-21 04:48

I agree with you Edgar. It would be great to have log4j as the logging mechanism.

 

On a different note, is there any way to stop the debug messages.

 

--

Regards,

Suraj Amin

 

Homepage: http://www.geocities.com/suraj_amin/

 

/* Every day is a new start and a chance to make right what went wrong yesterday. */

 

 

 

 

 

 

By: Teodor Danciu - teodord

RE: logging

2003-03-21 05:08

 

Hi,

 

I'll introduce Jakarta Commons Logging starting

with the next release.

 

What debug messages you want to suppress?

 

Thank you,

Teodor

 

 

 

 

 

By: Edgar Dollin - edollin

RE: logging

2003-03-21 05:50

Some additional comments on logging. Rather than using log4j directly, I would reccomend using jakarta commons logging. This would enable the use of most of the logging facilities (jdk 1.4, log4j, etc.) at the choice of the user.

 

All the messags could be 'debug', i.e. we turn on logging of the particular class with the log configuration. If you wanted to do a set of informational messages, I would log such things as the 'exact' text of sql queries, report compilation start / end, compiler error messages, report execution start with parameter values, in general major events within jasper.

 

Thanks

 

Edgar

 

 

 

 

By: Teodor Danciu - teodord

RE: logging

2003-03-25 00:56

 

Hi,

 

Can you post some of these debug messages?

I'm not sure I undestand where they come from

and why.

 

Thank you,

Teodor

 

 

 

 

 

By: Suraj Amin - suraj_amin

RE: logging

2003-03-25 05:58

Hi,

 

Following are the top 15 lines of the debug messages:

 

[25 Mar 2003 16:06:58,125] Digester: DEBUG: Pushing body text ''

[25 Mar 2003 16:06:58,125] Digester: DEBUG: New match='jasperReport'

[25 Mar 2003 16:06:58,125] Digester: DEBUG: Fire begin() for FactoryCreateRule[className=dori.jasper.engine.xml.JasperDesignFactory, attributeName=null]

[25 Mar 2003 16:06:58,125] Digester: DEBUG: [FactoryCreateRule]{jasperReport} New factory dori.jasper.engine.xml.JasperDesignFactory

[25 Mar 2003 16:06:58,187] Digester: DEBUG: [FactoryCreateRule]{jasperReport} New dori.jasper.engine.design.JasperDesign

[25 Mar 2003 16:06:58,187] Digester: DEBUG: Fire begin() for SetNextRule[methodName=setJasperDesign, paramType=dori.jasper.engine.design.JasperDesign]

[25 Mar 2003 16:06:58,187] sax: DEBUG: ignorableWhitespace(

)

[25 Mar 2003 16:06:58,187] sax: DEBUG: startElement(,queryString,queryString)

[25 Mar 2003 16:06:58,187] Digester: DEBUG: Pushing body text ''

[25 Mar 2003 16:06:58,187] Digester: DEBUG: New match='jasperReport/queryString'

[25 Mar 2003 16:06:58,203] Digester: DEBUG: Fire begin() for FactoryCreateRule[className=dori.jasper.engine.xml.JRQueryFactory, attributeName=null]

 

--

Regards,

Suraj Amin

 

Homepage: http://www.geocities.com/suraj_amin/

 

/* Everyone is necessarily the hero of his own life story. */

 

 

 

 

By: Suraj Amin - suraj_amin

RE: logging

2003-03-26 03:42

Hi,

 

I figured the problem. Disgestor's log4j appendor was conflicting with my apps. I had set DEBUG level to my root appender.

 

--

Regards,

Suraj Amin

 

Homepage: http://www.geocities.com/suraj_amin/

 

/* There are two ways of spreading light: to be the candle, or the mirror that reflects it. */

[bdrnotixia.com]

Hello,

Jasper report is embedded in my PLM software.

Each time I generating a reports, Jasper dump 10 millions lines of log in my terminal.... I guess I have activated the debug mode but I really don't know how to desactivate it....

 

Can somebody help me!

 

Some traces:

 

9695 [Thread-7] DEBUG org.apache.commons.digester.Digester   Fire body() for FactoryCreateRule[className=net.sf.jasperreports.engine.xml.JasperDesignFactory, attributeName=null, creationFactory=net.sf.jasperreports.engine.xml.JasperDesignFactory@202bb129]
89695 [Thread-7] DEBUG org.apache.commons.digester.Digester   Fire body() for SetNextRule[methodName=setJasperDesign, paramType=net.sf.jasperreports.engine.design.JasperDesign]
89695 [Thread-7] DEBUG org.apache.commons.digester.Digester   Popping body text ''
89695 [Thread-7] DEBUG org.apache.commons.digester.Digester   Fire end() for SetNextRule[methodName=setJasperDesign, paramType=net.sf.jasperreports.engine.design.JasperDesign]
89695 [Thread-7] DEBUG org.apache.commons.digester.Digester [setNextRule]{jasperReport} Call net.sf.jasperreports.engine.xml.JRXmlLoader.setJasperDesign(net.sf.jasperreports.engine.design.JasperDesign@147c0b3f)
89695 [Thread-7] DEBUG org.apache.commons.beanutils.MethodUtils Matching name=setJasperDesign on class net.sf.jasperreports.engine.xml.JRXmlLoader
89695 [Thread-7] DEBUG org.apache.commons.beanutils.MethodUtils Found straight match: public void net.sf.jasperreports.engine.xml.JRXmlLoader.setJasperDesign(net.sf.jasperreports.engine.design.JasperDesign)
89695 [Thread-7] DEBUG org.apache.commons.beanutils.MethodUtils isPublic:true
89696 [Thread-7] DEBUG org.apache.commons.digester.Digester   Fire end() for FactoryCreateRule[className=net.sf.jasperreports.engine.xml.JasperDesignFactory, attributeName=null, creationFactory=net.sf.jasperreports.engine.xml.JasperDesignFactory@202bb129]
89696 [Thread-7] DEBUG org.apache.commons.digester.Digester [FactoryCreateRule]{jasperReport} Pop net.sf.jasperreports.engine.design.JasperDesign
89696 [Thread-7] DEBUG org.apache.commons.digester.Digester.sax endPrefixMapping()
89696 [Thread-7] DEBUG org.apache.commons.digester.Digester.sax endPrefixMapping(xsi)
89696 [Thread-7] DEBUG org.apache.commons.digester.Digester.sax endDocument()
Wed Sep 23 14:24:46 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
Wed Sep 23 14:24:46 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
Wed Sep 23 14:24:46 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
Wed Sep 23 14:24:46 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
Wed Sep 23 14:24:46 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
Wed Sep 23 14:24:47 EDT 2009 >>>> ! ERROR, TRYING TO ACCESS CONVERSION TABLE FROM THE PAST, FALLIN BACK ON THE NEAREST TABLE IN THE FUTURE.
90642 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 1812864414: created for SaleOrder
90645 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 1812864414: filling report
90648 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 1812864414: adding page 1
90648 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 1812864414: title
90668 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 1812864414: page header
90668 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 1812864414: column header
90675 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 1812864414: detail
90695 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 1812864414: column footer
90697 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRFillSubreport Fill 1812864414: creating subreport filler
90698 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 524286420: created for TotalSubReport
90699 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRFillSubreport Band height validation for subreport "TotalSubReport" succeeded in the current page context (height = 792, top margin = 30, bottom margin = 30)
90699 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRFillSubreport Fill 1812864414: starting 524286420
90699 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRThreadSubreportRunner Fill 524286420: starting thread Thread[TotalSubReport subreport filler,6,main]
90699 [TotalSubReport subreport filler] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 524286420: filling report
90700 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRThreadSubreportRunner Fill 524286420: waiting for fill result
90702 [TotalSubReport subreport filler] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 524286420: detail
90706 [TotalSubReport subreport filler] DEBUG net.sf.jasperreports.engine.fill.JRVerticalFiller Fill 524286420: detail
90709 [TotalSubReport subreport filler] DEBUG net.sf.jasperreports.engine.fill.JRBaseFiller Fill 524286420: ended
90709 [TotalSubReport subreport filler] DEBUG net.sf.jasperreports.engine.fill.JRThreadSubreportRunner Fill 524286420: notifying of completion
90709 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRThreadSubreportRunner Fill 524286420: notified of fill result
90709 [Thread-7] DEBUG net.sf.jasperreports.engine.fill.JRFillSubreport Fill 1812864414: subreport 524286420 finished
90710 [Thread-7] DEBUG net.sf.jasper

 

THANKS!!
 

 

[teodord]

Hi,

 

Not sure what your PLM software is, but it probably has debug level logging enabled by default, is just that it has filters for all its own logging channels. And for any new library added to the software, there is no filter.

You have to find your logging configuration files in your PLM and add filters for JR classes as well.

I'm not an expert on logging and I can't say which logging library is used in your PLM, just by looking at the log.

So I can't tell you which config file to look for.

 

I hope this helps.
Teodor

 

[bdrnotixia.com]

Thank you for your quick answrer.

 

I figure out this morning that by simply removing from my lib the package log4j.jar was the solution. I know logger have any logs in my terminal.

 

 

Thanks.