Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » BIRT » Turning off BIRT loggin in web.xml
Turning off BIRT loggin in web.xml [message #657976] Fri, 04 March 2011 18:59 Go to next message
James Mising name is currently offline James Mising nameFriend
Messages: 26
Registered: November 2010
Junior Member
Hello,

I am trying to figure out how to turn off logging via the web.xml.

Currently I am trying:

<context-param>
<param-name>BIRT_VIEWER_LOG_LEVEL</param-name>
<param-value>OFF</param-value>
</context-param>

But when I run the report, I still see logging (mainly lots of INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 38
h) What am I doing incorrectly?


Thanks in advance.


James

[Updated on: Fri, 04 March 2011 20:37]

Report message to a moderator

Re: Turning off BIRT loggin in web.xml [message #658444 is a reply to message #657976] Tue, 08 March 2011 14:50 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

Can you post what packages are logging? You may also want to look at the viewer.properties file which contains a section for loggers.

Jason
Re: Turning off BIRT loggin in web.xml [message #658534 is a reply to message #658444] Tue, 08 March 2011 21:04 Go to previous messageGo to next message
James Mising name is currently offline James Mising nameFriend
Messages: 26
Registered: November 2010
Junior Member
I have looked in the viewer.properties file and read the part about logging, but not sure how to use that to adjust logging levels. I would be happy just to turn logging off for right now.

# [LOGGERS]
# "logger."+class=level
# if no level is specified or the text "DEFAULT",
# then the default level from the web.xml will be used
logger.org.eclipse.datatools.connectivity.oda=DEFAULT
logger.org.eclipse.datatools.enablement.oda=DEFAULT

Forgive me if this is not what you were asking for what packages are logging, but I have a report with crosstabs and lots of data. We are trying to clean up our log files and there is a lot of this everytime a report is run that I am trying to limit to SEVERE logs or even just turn off for right now and cant get it work:

INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 20
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 21
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 22
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 23
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 24
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 25
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 26
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 27
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 28
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 29
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 30
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 31
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 32
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 33
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 34
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 35
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 36
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 37
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 38
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 39
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 40
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 41
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 42
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 43
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 44
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 45
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 46
Mar 8, 2011 3:52:35 PM org.eclipse.birt.report.item.crosstab.core.re.executor.Table ColumnGenerator generateColumns
INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 47
Mar 8, 2011 3:52:36 PM org.eclipse.birt.report.data.oda.jdbc.Connection close
WARNING: JDBC connection: com.mysql.jdbc.JDBC4Connection@5c0c68d is closed
Mar 8, 2011 3:54:16 PM org.apache.tomcat.util.http.Parameters processParameters
WARNING: Parameters: Invalid chunk '' ignored.

BIRT is a wonderful tool and has provided a great way for us to display various data.


Thanks,


James

[Updated on: Wed, 09 March 2011 14:25]

Report message to a moderator

Re: Turning off BIRT loggin in web.xml [message #658733 is a reply to message #658534] Wed, 09 March 2011 16:02 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

James,

Are you getting logs in the viewer logs directory or in the app servers
log directory. I have the viewer deployed in tomcat and I had to turn
off its logs in apache-tomcat-5.5.20\conf\logging.properties

Jason

On 3/8/2011 4:04 PM, James wrote:
> I have look in the viewer.properties file and read the part about
> logging, but not sure how to use that to adjust logging levels. I would
> be happy just to turn logging off for right now.
>
> # [LOGGERS]
> # "logger."+class=level
> # if no level is specified or the text "DEFAULT",
> # then the default level from the web.xml will be used
> logger.org.eclipse.datatools.connectivity.oda=DEFAULT
> logger.org.eclipse.datatools.enablement.oda=DEFAULT
> Forgive me if this is not what you were asking for what packages are
> logging, but I have a report with crosstabs and lots of data. We are
> trying to clean up our log files and there is a lot of this everytime a
> report is run that I am trying to limit to SEVERE logs or even just turn
> off for right now and cant get it work:
>
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 20
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 21
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 22
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 23
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 24
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 25
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 26
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 27
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 28
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 29
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 30
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 31
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 32
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 33
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 34
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 35
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 36
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 37
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 38
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 39
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 40
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 41
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 42
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 43
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 44
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 45
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 46
> Mar 8, 2011 3:52:35 PM
> org.eclipse.birt.report.item.crosstab.core.re.executor.Table
> ColumnGenerator generateColumns
> INFO: Type: COLUMN_EDGE, Measure: 0, Data Position: 47
> Mar 8, 2011 3:52:36 PM org.eclipse.birt.report.data.oda.jdbc.Connection
> close
> WARNING: JDBC connection: mailto:com.mysql.jdbc.JDBC4Connection@5c0c68d
> is closed
> Mar 8, 2011 3:54:16 PM org.apache.tomcat.util.http.Parameters
> processParameters
> WARNING: Parameters: Invalid chunk '' ignored.
>
> BIRT is a wonderful tool and has provided a great way for us to display
> various data.
>
>
> Thanks,
>
>
> James
Re: Turning off BIRT loggin in web.xml [message #658736 is a reply to message #658733] Wed, 09 March 2011 16:20 Go to previous messageGo to next message
James Mising name is currently offline James Mising nameFriend
Messages: 26
Registered: November 2010
Junior Member
in the app servers log directory (catalina log file), and I do not have permission to the logging.properties file, that would be a sysadmin configuration. What is the setting to turn it off in that file if I ask?


Thanks,


James
Re: Turning off BIRT loggin in web.xml [message #658986 is a reply to message #658736] Thu, 10 March 2011 15:51 Go to previous messageGo to next message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

James,

I am still looking into this. I just set the log levels in the
logging.properties to OFF but this may not be what you want.

Jason

On 3/9/2011 11:20 AM, James wrote:
> in the app servers log directory (catalina log file), and I do not have
> permission to the logging.properties file, that would be a sysadmin
> configuration. What is the setting to turn it off in that file if I ask?
>
>
> Thanks,
>
>
> James
Re: Turning off BIRT loggin in web.xml [message #659072 is a reply to message #658986] Thu, 10 March 2011 21:31 Go to previous messageGo to next message
James Mising name is currently offline James Mising nameFriend
Messages: 26
Registered: November 2010
Junior Member
Thanks Jason.

I did work with the sys admin on changing the logging setting in the logging properties file in Tomcat. I think he changed it just to WARNING, but i don't think it was BIRT specific but for all logging meaning there would be no way to control the log level setting from within the app (web.xml). I am concerned because we are about to turn logging on wide open for everything for debugging, and I would like to adjust BIRT to not show everything because it takes up more space than anything else logged and is a lot to go through. Thanks again for your help and thanks for BIRT, its wonderful.


James
Re: Turning off BIRT loggin in web.xml [message #659229 is a reply to message #659072] Fri, 11 March 2011 15:26 Go to previous message
Jason Weathersby is currently offline Jason WeathersbyFriend
Messages: 9167
Registered: July 2009
Senior Member

James,

If you are trying to debug BIRT and set the log level in the web.xml of
the BIRT app, the log messages for the BIRT code should by default show
up in the WebViewer/logs directory.

Jason

On 3/10/2011 4:31 PM, James wrote:
> Thanks Jason.
>
> I did work with the sys admin on changing the logging setting in the
> logging properties file in Tomcat. I think he changed it just to
> WARNING, but i don't think it was BIRT specific but for all logging
> meaning there would be no way to control the log level setting from
> within the app (web.xml). I am concerned because we are about to turn
> logging on wide open for everything for debugging, and I would like to
> adjust BIRT to not show everything because it takes up more space than
> anything else logged and is a lot to go through. Thanks again for your
> help and thanks for BIRT, its wonderful.
>
>
> James
Previous Topic:Removing margin (whitespace) between table cells
Next Topic:Adding fields to database table causes error What is best practice?
Goto Forum:
  


Current Time: Sat Apr 20 04:36:06 GMT 2024

Powered by FUDForum. Page generated in 0.03882 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top