The image is not attached in my previous mail, I retry ...
http://www.nabble.com/file/5562/xslt.jpg
Anne Noseda wrote:
>
> Hy,
>
> I have a similar problem but I think that the pipeline eip service
> engine looses the correlation ID when it calls an extern WS.
>
> Here the schema of my work :
> (see attachment)
>
> The exchanges 1 and 2 raise an error "Could not retrieve correlation
> id for incoming exchange" in the aggregator eip service engine but the
> exchange number 3 is correctly processed by the aggregator. I think
> the saxon service engine is not implicated.
>
> Here my error stack trace :
>
> Exchange 3 ok :
>
> DEBUG - DeliveryChannelImpl - Received: InOnly[
> id: ID:POC07-1718-1168419261170-2:29
> status: Active
> role: provider
> service: {http://saxon.test.etnic.be}seAggregator
> endpoint: endpoint
> in: <?xml version="1.0" encoding="UTF-8"?> ***
> ]
> DEBUG - DeliveryChannelImpl - Processing inbound exchange:
> InOnly[
> id: ID:POC07-1718-1168419261170-2:29
> status: Done
> role: consumer
> service: {http://saxon.test.etnic.be}seAggregator
> endpoint: endpoint
> in: <?xml version="1.0" encoding="UTF-8"?> ***
> ]
>
> Exchanges 1 et 2 : KO :
>
> ERROR - EIPComponent - Error processing exchange InOnly[
> id: ID:POC07-1718-1168419261170-2:33
> status: Active
> role: provider
> service: {http://saxon.test.etnic.be}seAggregator
> endpoint: endpoint
> in: <?xml version="1.0" encoding="UTF-8"?> ***
> ]
> java.lang.IllegalArgumentException: Could not retrieve correlation id
> for incoming exchange
> at
> org.apache.servicemix.eip.support.AbstractAggregator.process(AbstractAggregator.java:138)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665
>
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
> ERROR - EIPComponent - Error processing exchange InOnly[
> id: ID:POC07-1718-1168419261170-2:34
> status: Active
> role: provider
> service: {http://saxon.test.etnic.be}seAggregator
> endpoint: endpoint
> in: <?xml version="1.0" encoding="UTF-8"?> ***
> ]
> java.lang.IllegalArgumentException: Could not retrieve correlation id
> for incoming exchange
> at
> org.apache.servicemix.eip.support.AbstractAggregator.process(AbstractAggregator.java:138)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
>
>
> 2007/1/10, sebastien <[EMAIL PROTECTED]>:
>>
>> Hi,
>>
>> I tried with servicemix-saxon SE.
>> Now, I can see in the log file that the correlation ID is sent to the
>> aggregator component.
>> But I got still the same error :
>> http://www.nabble.com/file/5559/servicemix.log servicemix.log > incoming
>> exchange"
>>
>> -> I put the servicemix log file in attachement
>>
>> Thanks for your help
>>
>> Sebastien
>>
>>
>>
>>
>>
>> gnodet wrote:
>> >
>> > Have you tried with servicemix-saxon SE instead of the
>> > lightweight component ?
>> >
>> > On 1/9/07, sebastien <[EMAIL PROTECTED]> wrote:
>> >>
>> >> hi all,
>> >>
>> >> I use the followings components :
>> >>
>> >> -> XSLT (x) -> HTTP
>> >> (pipeline)
>> >> HTTP -> Splitter -> Recipient List
>> >> -> Aggregator -> JMS
>> >> -> XSLT (x) -> HTTP
>> >> (pipeline)
>> >>
>> >> I can see in the log file that XSLT component does not send the
>> >> correlation
>> >> ID property.
>> >> It causes the following error in the Aggregator component :
>> >> "java.lang.IllegalArgumentException: Could not retrieve correlation id
>> >> for
>> >> incoming exchange"
>> >>
>> >> Have you got an idea ?
>> >>
>> >> Tanks for your help.
>> >>
>> >> Sebastien
>> >>
>> >> I tried with ServiceMix 3.0 and ServiceMix 3.1 version without any
>> >> success.
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Correlation-ID-lost-after-XSLT-component-tf2945039s12049.html#a8235443
>> >> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Correlation-ID-lost-after-XSLT-component-tf2945039s12049.html#a8253993
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Correlation-ID-lost-after-XSLT-component-tf2945039s12049.html#a8255163
Sent from the ServiceMix - User mailing list archive at Nabble.com.
