You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Holger Haag (JIRA)" <ji...@apache.org> on 2006/07/28 13:12:13 UTC

[jira] Created: (BETWIXT-54) CyclicReferenceException Logging

CyclicReferenceException Logging
--------------------------------

                 Key: BETWIXT-54
                 URL: http://issues.apache.org/jira/browse/BETWIXT-54
             Project: Commons Betwixt
          Issue Type: Improvement
         Environment: /
            Reporter: Holger Haag
            Priority: Trivial
         Attachments: betwixt-cyclic-reference-logging.patch

I got screwed last night because of a CyclicReferenceException without additional info (debug level not switched on). 

So I've increased the priority of some log entries from debug to error and added some more information (class names of all objects in the stack). 

I think this will make debugging CyclicReferenceException much easier.

Patch attached.



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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Closed: (BETWIXT-54) CyclicReferenceException Logging

Posted by "Robert Burrell Donkin (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/BETWIXT-54?page=all ]

Robert Burrell Donkin closed BETWIXT-54.
----------------------------------------

    Resolution: Fixed

hi holgar

thanks for the patch

i've committed a variation upon the patch. i'm a little concerned that logging to error is a little high. so, i've logged to info but included the information in the exception which should be printed out when caught.

please give this a try. if this isn't good enough then i'll consider turning up the log level again.

robert

> CyclicReferenceException Logging
> --------------------------------
>
>                 Key: BETWIXT-54
>                 URL: http://issues.apache.org/jira/browse/BETWIXT-54
>             Project: Commons Betwixt
>          Issue Type: Improvement
>         Environment: /
>            Reporter: Holger Haag
>            Priority: Trivial
>         Attachments: betwixt-cyclic-reference-logging.patch
>
>
> I got screwed last night because of a CyclicReferenceException without additional info (debug level not switched on). 
> So I've increased the priority of some log entries from debug to error and added some more information (class names of all objects in the stack). 
> I think this will make debugging CyclicReferenceException much easier.
> Patch attached.

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Commented: (BETWIXT-54) CyclicReferenceException Logging

Posted by "Holger Haag (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/BETWIXT-54?page=comments#action_12425458 ] 
            
Holger Haag commented on BETWIXT-54:
------------------------------------

I haven't tested it, but it seems sufficient. Thanks for applying the patch :-) Holger

> CyclicReferenceException Logging
> --------------------------------
>
>                 Key: BETWIXT-54
>                 URL: http://issues.apache.org/jira/browse/BETWIXT-54
>             Project: Commons Betwixt
>          Issue Type: Improvement
>         Environment: /
>            Reporter: Holger Haag
>            Priority: Trivial
>         Attachments: betwixt-cyclic-reference-logging.patch
>
>
> I got screwed last night because of a CyclicReferenceException without additional info (debug level not switched on). 
> So I've increased the priority of some log entries from debug to error and added some more information (class names of all objects in the stack). 
> I think this will make debugging CyclicReferenceException much easier.
> Patch attached.

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


[jira] Updated: (BETWIXT-54) CyclicReferenceException Logging

Posted by "Holger Haag (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/BETWIXT-54?page=all ]

Holger Haag updated BETWIXT-54:
-------------------------------

    Attachment: betwixt-cyclic-reference-logging.patch

Patch

> CyclicReferenceException Logging
> --------------------------------
>
>                 Key: BETWIXT-54
>                 URL: http://issues.apache.org/jira/browse/BETWIXT-54
>             Project: Commons Betwixt
>          Issue Type: Improvement
>         Environment: /
>            Reporter: Holger Haag
>            Priority: Trivial
>         Attachments: betwixt-cyclic-reference-logging.patch
>
>
> I got screwed last night because of a CyclicReferenceException without additional info (debug level not switched on). 
> So I've increased the priority of some log entries from debug to error and added some more information (class names of all objects in the stack). 
> I think this will make debugging CyclicReferenceException much easier.
> Patch attached.

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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org