|
List Info
Thread: Created: (JBSEAM-1835) Improve debug logging
|
|
| Created: (JBSEAM-1835) Improve debug
logging |
 
United States |
2007-08-21 09:27:18 |
Improve debug logging
---------------------
Key: JBSEAM-1835
URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
Project: JBoss Seam
Issue Type: Task
Reporter: Christian Bauer
Priority: Blocker
This should be logged at TRACE level:
(http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Events]
Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
(http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component]
instantiating Seam component: org.jboss.seam.core.events
(http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component]
initializing new instance of: org.jboss.seam.core.events
(http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG [Component]
done initializing: org.jboss.seam.core.events
I have thousands of lines of these making DEBUG completely
useless. I still want to see all other instantiations etc.
from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issues lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
| Commented: (JBSEAM-1835) Improve debug
logging |
United States |
2007-08-21 11:48:18 |
[ http://jira.jboss.com/jira/browse/JBS
EAM-1835?page=comments#action_12373190 ]
Gavin King commented on JBSEAM-1835:
------------------------------------
OK, go ahead and make that change.
> Improve debug logging
> ---------------------
>
> Key: JBSEAM-1835
> URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Events] Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] instantiating Seam component:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] initializing new instance of:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG
completely useless. I still want to see all other
instantiations etc. from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
| Updated: (JBSEAM-1835) Improve logging |
United States |
2007-08-23 07:30:18 |
[ http://jira.jboss.com/jira/browse/JBSEAM-1835?page=all
]
Pete Muir updated JBSEAM-1835:
------------------------------
Summary: Improve logging (was: Improve debug logging)
> Improve logging
> ---------------
>
> Key: JBSEAM-1835
> URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Events] Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] instantiating Seam component:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] initializing new instance of:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG
completely useless. I still want to see all other
instantiations etc. from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
| Commented: (JBSEAM-1835) Improve debug
logging |
United States |
2007-08-23 07:30:18 |
[ http://jira.jboss.com/jira/browse/JBS
EAM-1835?page=comments#action_12373492 ]
Pete Muir commented on JBSEAM-1835:
-----------------------------------
Can we also consider reducing the amount of stuff we spew
out at INFO level and putting it at DEBUG (as that is when
it is *actually* useful):
* Which jars are being scanned
* Which namespaces are available (why is this even useful at
all?)
* That seam.properties has been read (it doesn't even say
*which* jar its been read from).
> Improve debug logging
> ---------------------
>
> Key: JBSEAM-1835
> URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Events] Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] instantiating Seam component:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] initializing new instance of:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG
completely useless. I still want to see all other
instantiations etc. from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
| Commented: (JBSEAM-1835) Improve
logging |
United States |
2007-08-23 10:11:18 |
[ http://jira.jboss.com/jira/browse/JBS
EAM-1835?page=comments#action_12373535 ]
Christian Bauer commented on JBSEAM-1835:
-----------------------------------------
The Context logging a new HTTP session at INFO is also
filling up the log on the production box.
> Improve logging
> ---------------
>
> Key: JBSEAM-1835
> URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Events] Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] instantiating Seam component:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] initializing new instance of:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG
completely useless. I still want to see all other
instantiations etc. from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
| Commented: (JBSEAM-1835) Improve
logging |
United States |
2007-08-23 10:35:51 |
[ http://jira.jboss.com/jira/browse/JBS
EAM-1835?page=comments#action_12373540 ]
Christian Bauer commented on JBSEAM-1835:
-----------------------------------------
TRACE for this:
[testng] 17:32:16,025 DEBUG [SpringELResolver] No Spring
BeanFactory found. Skipping.
> Improve logging
> ---------------
>
> Key: JBSEAM-1835
> URL: http://
jira.jboss.com/jira/browse/JBSEAM-1835
> Project: JBoss Seam
> Issue Type: Task
> Reporter: Christian Bauer
> Priority: Blocker
>
> This should be logged at TRACE level:
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Events] Processing
event:org.jboss.seam.postSetVariable.org.jboss.seam.core.man
ager
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] instantiating Seam component:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] initializing new instance of:
org.jboss.seam.core.events
> (http-127.0.0.1-8080-1hread) 16:24:55,596 DEBUG
[Component] done initializing: org.jboss.seam.core.events
> I have thousands of lines of these making DEBUG
completely useless. I still want to see all other
instantiations etc. from Component though.
--
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.atl
assian.com/software/jira
_______________________________________________
jbossseam-issues mailing list
jbossseam-issueslists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossseam-issu
es
|
|
[1-6]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|