History | Log In     View a printable version of the current page. Get help!  
   HOME       BROWSE PROJECT       FIND ISSUES   
    QUICK SEARCH:  
Issue Details (XML | Word)

Key: JBSEAM-2232
Type: Task Task
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Christian Bauer
Votes: 8
Watchers: 4
Operations

If you were logged in you would be able to see more operations.
Seam

Reduce debug log level for events

Created: 09/Nov/07 06:29 AM   Updated: 19/Mar/08 07:28 PM
Component/s: Core
Affects Version/s: None
Fix Version/s: 2.1.0.BETA2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
This issue duplicates:
JBSEAM-1835 Improve logging Critical Closed
 


 Description  « Hide
Debug logging with Seam 2.x is completely useless. The most critical information in the debug log is the instantiation and lookup of components, however, if you enable DEBUG for

org.jboss.seam.Component, you get thousands of these:

12:26:06,282 DEBUG [Component] instantiating Seam component: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] initializing new instance of: org.jboss.seam.core.events
12:26:06,282 DEBUG [Component] done initializing: org.jboss.seam.core.events

We need to exclude the event firing from debug logging, even if we hardcode it. And, are these events really useful? I have no idea why and when I'd want to listen to "context variable initialized" events.


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order:
[ Permlink | « Hide ]
Matthew Lieder [09/Nov/07 09:53 AM]
Hear, hear! Debug logging is definitely very unhelpful as it works now.

[ Permlink | « Hide ]
Max Rydahl Andersen [09/Nov/07 10:49 AM]
I know of one usecase where these events are usefull, namely to allow the tooling to listen for events and put a breakpoint automatically when a specific event happens. Tracing down when something is initialized is usefull.

I would suggest we move the event logging to a TRACE level instead or somehow allow users to enable/disable logging for the events they want.

[ Permlink | « Hide ]
Tobias Frech [20/Nov/07 10:19 AM]
I have no problem with too many debug messages. But the INFO level should be production useable.

The RuleBasedIdentity component logs a WARN each time a session is created! It would be great if someone sanitized the log messages for a typical SEAM application. I think Drools isn't used a lot so far. Thus a typical application should print log statements on the console until everything is initialized (perhaps even lazily) but then normal operation of the application should log no further messages on the INFO level.

[ Permlink | « Hide ]
Matthew Lieder [20/Nov/07 10:25 AM]
Guys, vote for this issue if you want it fixed; that's mostly how they've been prioritizing fixes lately. Given how easy this is to rectify, I'm guessing as soon as it gets their attention they'll fix it :).

[ Permlink | « Hide ]
Pete Muir [20/Nov/07 10:39 AM]
I would prefer to address this with a consistent overview rather than altering log levels ad hoc.

So, please, comment here with log levels you would like to see changed so that we can get a good idea of what is useful, and whats not.

[ Permlink | « Hide ]
Tobias Frech [20/Nov/07 10:44 AM]
The WARN message is only printed if the Drools libs are present.

[ Permlink | « Hide ]
Vladimir Kovalyuk [21/Jan/08 08:50 AM]
I have to skip the following messages:

1. related to Events component (too verbose :) )
2. seam component not found (before creating, a lot of unsuccessful attempts to concat some prefixes like org.jboss.seam.core.actions etc)
3. instantiating seam component
4. initializing new instance of
5. done initializing

I'll be fine with fine-prepared exception when seam can't create component.


Powered by Atlassian JIRA™ the Professional Issue Tracker. (Enterprise Edition, Version: 3.6.5-#161) - Bug/feature request - Contact Administrators