On 12/5/06, Roger Menday <[EMAIL PROTECTED]> wrote:
Guillaume Nodet (JIRA) wrote:
> [
https://issues.apache.org/activemq/browse/SM-751?page=comments#action_37501 ]
>
> Guillaume Nodet commented on SM-751:
> ------------------------------------
>
> Btw, looking at the patch, I was wondering if it would be interesting to have
a multi-level
> correlationId, so that we could trace the exchange to its "parent" exchange
and from
> the parent to the grand-parent and so forth...
>
Hi,
Sorry to drag out an old email, but I was wondering if the proposition
above made it into the code ?
It would be quite useful to have ...
(as I see it when a new correlationid is added into the properties of an
exchange which already has one, another property records the
parentcorrelationid ... )
Not yet. Would you mind raising another issue for that ?
If you have any time to write a patch ... ;)
?
thanks,
Roger
>
>> Flow tracing with correlation id
>> --------------------------------
>>
>> Key: SM-751
>> URL: https://issues.apache.org/activemq/browse/SM-751
>> Project: ServiceMix
>> Issue Type: Improvement
>> Reporter: Gianfranco Boccalon
>> Attachments: servicemix-components.zip
>>
>>
>> Add the possibility to trace the flow of the messages inside a Service
Assembly.
>> For example, if we have a Service Assembly composed of three components, two
binding components (call them BC1 and BC2) and a service engine (SE) organized in this
sequence BC1->SE->BC2, we need to recognize that the output messages produced by the
SE component are related to some messages provided by BC1.
>> To do this, we need to add a "process correlation id" to the message
exchanges and to modify the used components, to propagate this correlation id in all Message
Exchanges sent.
>> Enclosed there is the modified code for the following components:
>> - HTTP binding component: here I added the code to generate the correlation
Id and set it in the Message Exchange
>> - Splitter
>> - Router (the lightweight component)
>>
>
>
--
Cheers,
Guillaume Nodet
