[jira] Updated: (SANDESHA2-2) Enable trace for Sandesha2 Msg flows

["Andrew Gatford (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/SANDESHA2-2?page=all ]

Andrew Gatford updated SANDESHA2-2:
-----------------------------------

    Attachment: moretrace3.patch

Adding further trace to several classes to help problem diagnosis
Also, in the SandeshaUtil.executeAndStore method, removed the duplicate setting of the MESSAGE_STORE_KEY

> Enable trace for Sandesha2 Msg flows
> ------------------------------------
>
>                 Key: SANDESHA2-2
>                 URL: http://issues.apache.org/jira/browse/SANDESHA2-2
>             Project: Apache Sandesha2
>          Issue Type: Improvement
>            Reporter: Andrew Gatford
>            Priority: Trivial
>         Attachments: moretrace.patch, moretrace2.patch, moretrace2.patch, moretrace3.patch, patch.diff, patch2.patch, tracePatch1.txt
>
>
> To enable quicker debuging of problems encountered it would be good to trace the entry/exit of key methods so that people can quickly see the flow of messages through Sandesha2.
> For example when creating a new Bean Manager implementation and encountering problems it would be good to know what Sandesha was trying to do at the time the failure occured

-- 
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org