You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Bill Nagy (JIRA)" <ji...@apache.org> on 2007/02/01 20:59:05 UTC

[jira] Resolved: (AXIS2-2076) Improve trace correlation for message context serialization

     [ https://issues.apache.org/jira/browse/AXIS2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Nagy resolved AXIS2-2076.
------------------------------

    Resolution: Fixed
      Assignee: Bill Nagy

> Improve trace correlation for message context serialization
> -----------------------------------------------------------
>
>                 Key: AXIS2-2076
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2076
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: kernel
>            Reporter: Ann Robinson
>         Assigned To: Bill Nagy
>            Priority: Minor
>         Attachments: patch.txt
>
>
> In debugging some of the more complicated application scenarios, it has become clear that having better correlation in the trace messages among some of the objects in the message context object graph is very helpful in determining failure points.
> The following needs to be done:
> - Make use of the logCorrelationIDString in the MessageContext
> - Add a logCorrelationIDString to the OperationContext
> - Add a logCorrelationIDString to the Options
> - Add some try..catch blocks around the use of ObjectStateUtils.writeObject(...) for some objects
> In addition, clean up the following
> - remove commented out System.out.println lines 
> - move the check of the NeedsToBeReconciled flag to a method 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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