Hi Bill, I'm a little wary of adding anything that 'looks' like another messageid because of potential confusion. However, I share you trace-log woes. So, if you can think of a good, clear name, I'm all for it.
David On 08/01/07, Bill Nagy <[EMAIL PROTECTED]> wrote:
Hi folks, At least for me, trying to parse all but the most trivial trace file is a nightmare -- we have multiple threads, multiple concurrent messages being sent and received on a single thread, message processing being handed off between threads, etc. I figure that there has to be a way to make the logs easier to understand, so as a small first step I would like to propose adding a unique id to each message/MessageContext to be used as a correlation point for each of the log messages. (e.g. Message uid:2J39JAJQI11U2: AxisEngine receive: ...) We can't correlate on the object id's of the MessageContext's, because those change if the message is persisted/restored. We also can't correlate on the WS-A MessageID, as that is not guaranteed to be present, and even if it is, it won't be identified early enough in the flow to prevent having to perform a double correlation. The usefulness of this will, of course, depend upon log messages taking advantage of its presence, but I certainly view it as a worthwhile use of bytes. Comments? -Bill --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
