[infinispan-issues] [JBoss JIRA] Commented: (ISPN-155) Marshalling code to provide more helpful stacktraces

Galder Zamarreno (JIRA) jira-events at lists.jboss.org
Thu Sep 10 13:38:23 EDT 2009


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

Galder Zamarreno commented on ISPN-155:
---------------------------------------

<dmlloyd> yeah, but now whenever I think of toString, I think of the monstrosity in e.g. BaseClassLoader that returns a string that's like 150k
<dmlloyd> well you could do that
<dmlloyd> try { nested write operation; } catch (IOException e) { if (log.isTraceEnabled()) { MarshallingException.addUserInformation(myObject.toString()); }}
<dmlloyd> (and rethrow)
<galderz> true
<galderz> at least for the reading part yeah
<galderz> i mean writingt
<dmlloyd> that'd still work for writing as well, but you'd have to do it everywhere you use writeObject()
<dmlloyd> which means in your custom marshallers as well as in your main entry point

> Marshalling code to provide more helpful stacktraces
> ----------------------------------------------------
>
>                 Key: ISPN-155
>                 URL: https://jira.jboss.org/jira/browse/ISPN-155
>             Project: Infinispan
>          Issue Type: Task
>          Components: RPC
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: 4.0.0.CR1
>
>
> Try to make marshaller code more friendly so that more helpful stacktraces are presented. Example: http://pastie.org/580184
> IRC chat with Manik:
> <manik> galderz ping
> <galderz> hi manik 
> <manik> hi there
> <manik> any chance of wrapping up the marshaller code to provide more helpful stack traces?   :-)
> <galderz> yeah, why not?
> <galderz> any suggestion in particular?
> <manik> e.g.
> <manik> http://pastie.org/580184
> <manik> doesn't tell me what it is trying to marshall when it fails
> <manik> So it's kinda hard for me to locate where the problem is
> <galderz> right, ic ur point
> <galderz> let me create a jira for this
> <manik> well, its clearly trying to read a stream and something should be logged on the sender (or any generator of that stream) so we can trace what it is
> <galderz> we have to be careful about what we log since this code is used v heavily
> <galderz> i'll investigate this further
> * clebert1 (n=clebert at cpe-70-112-88-39.austin.res.rr.com) has joined #infinispan
> <galderz> wrt the exception, there's something in the SuccessfulResponse sent back that the requester doesn't know what it is

-- 
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 infinispan-issues mailing list