[infinispan-issues] [JBoss JIRA] Commented: (ISPN-867) ExternalizerTable TRACE logging too verbose

Galder Zamarreño (JIRA) jira-events at lists.jboss.org
Mon Jan 10 13:01:49 EST 2011


    [ https://issues.jboss.org/browse/ISPN-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574463#comment-12574463 ] 

Galder Zamarreño commented on ISPN-867:
---------------------------------------

I had originally added this trace logging to figure out when known type was not present in the writers table that should have been. This was relatively straightforward in the 4.x days cos I knew exactly the types that were in the writers map. To so a similar thing would require to keep track on the types added but it's not worth it since I haven't heard again from the NPEs that we used to have. They should be solved by now. So, I'm removing this trace log message for the time being.

> ExternalizerTable TRACE logging too verbose
> -------------------------------------------
>
>                 Key: ISPN-867
>                 URL: https://issues.jboss.org/browse/ISPN-867
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Marshalling
>    Affects Versions: 5.0.0.ALPHA1
>            Reporter: Manik Surtani
>            Assignee: Galder Zamarreño
>            Priority: Minor
>              Labels: logging
>             Fix For: 5.0.0.ALPHA2
>
>
> Seen when a remote node throws an exception and the exception is propagated across the network.  See http://pastie.org/1437482

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the infinispan-issues mailing list