Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330586

Summary:	BIRT Logging on JBoss 5.1 LogLevel not working
Product:	z_Archived	Reporter:	l30thelion
Component:	BIRT	Assignee:	Yu Chen <yChen>
Status:	VERIFIED FIXED	QA Contact:	Xiaoying Gu <bluesoldier>
Severity:	normal
Priority:	P3	CC:	bluesoldier, subra.tata
Version:	2.3.1
Target Milestone:	3.7.0 M7
Hardware:	PC
OS:	Windows XP
Whiteboard:	Obsolete

Description l30thelion

2010-11-18 11:51:18 EST

Creating bug from forum conversation: http://www.birt-exchange.org/org/forum/index.php/topic/20961-birt-logging-on-jboss-5-1-loglevel-not-working/

Environment:
JDK 1.6
JBoss 5.1
Birt 2.3.1

** Not using Birt Viewer, using Report Engine directly
**(this is not an issue when running JBoss 4.2.3, it only started happening when we moved the JBoss 5.1)

Exact problem posted somewhere else: http://www.eclipse.org/forums/index.php?t=msg&goto=531361&

Problem Description:
On JBoss 4.2.3 I am able to configure the log Level with success, not so on JBoss 5.1. Even though the log Level is set properly it is ignored and FINEST/FINE is always used, causing excessive logging which we don't want. It seems that JBoss 5.1 LogManager's leveObject property is always set to "ALL" even though the Level is set to Level.SEVERE (see image below).

Comment 1 Xiaoying Gu

2010-11-19 00:18:36 EST

(In reply to comment #0)
> Creating bug from forum conversation:
> http://www.birt-exchange.org/org/forum/index.php/topic/20961-birt-logging-on-jboss-5-1-loglevel-not-working/
> 
> Environment:
> JDK 1.6
> JBoss 5.1
> Birt 2.3.1
> 
> ** Not using Birt Viewer, using Report Engine directly
> **(this is not an issue when running JBoss 4.2.3, it only started happening
> when we moved the JBoss 5.1)
> 
> Exact problem posted somewhere else:
> http://www.eclipse.org/forums/index.php?t=msg&goto=531361&
> 
> Problem Description:
> On JBoss 4.2.3 I am able to configure the log Level with success, not so on
> JBoss 5.1. Even though the log Level is set properly it is ignored and
> FINEST/FINE is always used, causing excessive logging which we don't want. It
> seems that JBoss 5.1 LogManager's leveObject property is always set to "ALL"
> even though the Level is set to Level.SEVERE (see image below).


Do you have this issue if deploy the report viewer on JBoss 5.1?

Comment 2 l30thelion

2010-11-22 16:40:02 EST

(In reply to comment #1)
> (In reply to comment #0)
> > Creating bug from forum conversation:
> > http://www.birt-exchange.org/org/forum/index.php/topic/20961-birt-logging-on-jboss-5-1-loglevel-not-working/
> > 
> > Environment:
> > JDK 1.6
> > JBoss 5.1
> > Birt 2.3.1
> > 
> > ** Not using Birt Viewer, using Report Engine directly
> > **(this is not an issue when running JBoss 4.2.3, it only started happening
> > when we moved the JBoss 5.1)
> > 
> > Exact problem posted somewhere else:
> > http://www.eclipse.org/forums/index.php?t=msg&goto=531361&
> > 
> > Problem Description:
> > On JBoss 4.2.3 I am able to configure the log Level with success, not so on
> > JBoss 5.1. Even though the log Level is set properly it is ignored and
> > FINEST/FINE is always used, causing excessive logging which we don't want. It
> > seems that JBoss 5.1 LogManager's leveObject property is always set to "ALL"
> > even though the Level is set to Level.SEVERE (see image below).
> 
> 
> Do you have this issue if deploy the report viewer on JBoss 5.1?

I have not attempted to deploy using the report viewer on JBoss 4 or 5, so I am not sure if this happens or not, sorry.

Seems that JBoss takes over logging, is there a way to avoid this?

Comment 3 Yu Chen

2011-04-20 22:28:34 EDT

Fixed. Please try our 3.7 build.

Comment 4 Xiaoying Gu

2011-04-20 22:56:11 EDT

Verified with daily build 3.7.0.v201104210630.

Comment 5 Subra T

2014-12-29 05:24:14 EST

We are using BIRT 2.5.2 and facing the same issue. Is there any patch is available instead of migration to 3.7 level as we are in production and it is urgent.

Comment 6 Subra T

2015-01-05 05:36:07 EST

Any more updates for patch for version no. 2.5.2?