[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2232) Reduce debug log level for events
Tobias Frech (JIRA)
jira-events at lists.jboss.org
Tue Nov 20 10:21:18 EST 2007
[ http://jira.jboss.com/jira/browse/JBSEAM-2232?page=comments#action_12388451 ]
Tobias Frech commented on JBSEAM-2232:
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.
> Reduce debug log level for events
> Key: JBSEAM-2232
> URL: http://jira.jboss.com/jira/browse/JBSEAM-2232
> Project: JBoss Seam
> Issue Type: Task
> Components: Core
> Reporter: Christian Bauer
> Priority: Critical
> 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.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues