[weld-issues] [JBoss JIRA] Resolved: (WELD-366) TRACE level logging on Weld causes infinite loop

David Allen (JIRA) jira-events at lists.jboss.org
Thu Jan 7 18:53:30 EST 2010


     [ https://jira.jboss.org/jira/browse/WELD-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Allen resolved WELD-366.
------------------------------

    Fix Version/s: 1.0.1.CR1
       Resolution: Done


The problem was with the toString() on the AbstractAttributeBackedBeanStore which was using an iterator that might be broken.  It was iterating over 100's of millions of names.  The toString() was changed to just print the class name of the actual bean store which makes better sense for the trace messages.

> TRACE level logging on Weld causes infinite loop
> ------------------------------------------------
>
>                 Key: WELD-366
>                 URL: https://jira.jboss.org/jira/browse/WELD-366
>             Project: Weld
>          Issue Type: Bug
>    Affects Versions: 1.0.0.CR1
>            Reporter: David Allen
>            Assignee: David Allen
>             Fix For: 1.0.1.CR1
>
>
> Setting the logging level to TRACE on org.jboss.weld causes an infinite loop somewhere that halts deployment and undeployments of Weld archives.  It is either something in the logging system, or a poorly written toString() on some object.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list