You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Manu <me...@gmail.com> on 2014/12/12 11:58:30 UTC
WS-Addressing : [MAPCodec] Failed to correlate message
Hi,
Our application uses asynchronous invocation through ws-addressing a lot
and randomly we have this error :
[MAPCodec] Failed to correlate message, aborting dispatch.
I've joined the full log trace for the error with cxf ws-addressing in
DEBUG mode.
I can't figure out what's going on so any help would be appriecated.
Thanks
Manuel
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Daniel Kulp <dk...@apache.org>.
> On Dec 16, 2014, at 8:18 AM, Manu <me...@gmail.com> wrote:
>
> If I create a unique and dynamic replyTo URL, will the destination registry
> be storing each URL ?
Yes. But only as long as there is a client that is using it. When the client is finalized or you call close on it, the endpoint would get cleaned up and the registry entry removed.
> Could this lead to an OutOfMemoryError ?
Hopefully no if the clients are cleaned up.
Dan
>
>
> Le Tue Dec 16 2014 at 13:29:56, Manu <me...@gmail.com> a écrit :
>
>> In org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.getDestination(Bus,
>> String, Message), the interceptor register a MessageObserver on the
>> destination.
>> So the second web service call will replace the first MessageObserver.
>> This way the interceptor chain registered (and the MAPCodec) will not be
>> aware of the
>> message so the error message occured ..
>>
>> Precision : I'm not usng jetty but the ServletDestination for handling the
>> response ...
>>
>>
>>
>> Le Tue Dec 16 2014 at 12:41:07, Manu <me...@gmail.com> a écrit :
>>
>> It seems worse than I first thought ...
>>> If 2 requests for the same asynchronous web service run in parallel, the
>>> same problem occurs.
>>> Can someone help me please ?
>>> I'm totally lost ...
>>>
>>> Le Mon Dec 15 2014 at 16:59:14, Manu <me...@gmail.com> a écrit :
>>>
>>> It seems that when there is multiple asynchronous web service using the
>>>> same decoupled endpoint that there some kind of correlating-message problem.
>>>> Should I use a unique decoupledEndpoint for each asynchronous web
>>>> service ?
>>>>
>>>>
>>>> Le Mon Dec 15 2014 at 14:26:42, Manu <me...@gmail.com> a écrit :
>>>>
>>>> Does anyone have a clue on what's going on ?
>>>>>
>>>>>
>>>>> Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
>>>>>
>>>>> Hi,
>>>>>>
>>>>>> Our application uses asynchronous invocation through ws-addressing a
>>>>>> lot and randomly we have this error :
>>>>>> [MAPCodec] Failed to correlate message, aborting dispatch.
>>>>>>
>>>>>> I've joined the full log trace for the error with cxf ws-addressing in
>>>>>> DEBUG mode.
>>>>>> I can't figure out what's going on so any help would be appriecated.
>>>>>>
>>>>>> Thanks
>>>>>> Manuel
>>>>>>
>>>>>
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Manu <me...@gmail.com>.
Hi again,
If I create a unique and dynamic replyTo URL, will the destination registry
be storing each URL ?
Could this lead to an OutOfMemoryError ?
Le Tue Dec 16 2014 at 13:29:56, Manu <me...@gmail.com> a écrit :
> In org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.getDestination(Bus,
> String, Message), the interceptor register a MessageObserver on the
> destination.
> So the second web service call will replace the first MessageObserver.
> This way the interceptor chain registered (and the MAPCodec) will not be
> aware of the
> message so the error message occured ..
>
> Precision : I'm not usng jetty but the ServletDestination for handling the
> response ...
>
>
>
> Le Tue Dec 16 2014 at 12:41:07, Manu <me...@gmail.com> a écrit :
>
> It seems worse than I first thought ...
>> If 2 requests for the same asynchronous web service run in parallel, the
>> same problem occurs.
>> Can someone help me please ?
>> I'm totally lost ...
>>
>> Le Mon Dec 15 2014 at 16:59:14, Manu <me...@gmail.com> a écrit :
>>
>> It seems that when there is multiple asynchronous web service using the
>>> same decoupled endpoint that there some kind of correlating-message problem.
>>> Should I use a unique decoupledEndpoint for each asynchronous web
>>> service ?
>>>
>>>
>>> Le Mon Dec 15 2014 at 14:26:42, Manu <me...@gmail.com> a écrit :
>>>
>>> Does anyone have a clue on what's going on ?
>>>>
>>>>
>>>> Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
>>>>
>>>> Hi,
>>>>>
>>>>> Our application uses asynchronous invocation through ws-addressing a
>>>>> lot and randomly we have this error :
>>>>> [MAPCodec] Failed to correlate message, aborting dispatch.
>>>>>
>>>>> I've joined the full log trace for the error with cxf ws-addressing in
>>>>> DEBUG mode.
>>>>> I can't figure out what's going on so any help would be appriecated.
>>>>>
>>>>> Thanks
>>>>> Manuel
>>>>>
>>>>
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Manu <me...@gmail.com>.
In org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.getDestination(Bus,
String, Message), the interceptor register a MessageObserver on the
destination.
So the second web service call will replace the first MessageObserver. This
way the interceptor chain registered (and the MAPCodec) will not be aware
of the
message so the error message occured ..
Precision : I'm not usng jetty but the ServletDestination for handling the
response ...
Le Tue Dec 16 2014 at 12:41:07, Manu <me...@gmail.com> a écrit :
> It seems worse than I first thought ...
> If 2 requests for the same asynchronous web service run in parallel, the
> same problem occurs.
> Can someone help me please ?
> I'm totally lost ...
>
> Le Mon Dec 15 2014 at 16:59:14, Manu <me...@gmail.com> a écrit :
>
> It seems that when there is multiple asynchronous web service using the
>> same decoupled endpoint that there some kind of correlating-message problem.
>> Should I use a unique decoupledEndpoint for each asynchronous web service
>> ?
>>
>>
>> Le Mon Dec 15 2014 at 14:26:42, Manu <me...@gmail.com> a écrit :
>>
>> Does anyone have a clue on what's going on ?
>>>
>>>
>>> Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
>>>
>>> Hi,
>>>>
>>>> Our application uses asynchronous invocation through ws-addressing a
>>>> lot and randomly we have this error :
>>>> [MAPCodec] Failed to correlate message, aborting dispatch.
>>>>
>>>> I've joined the full log trace for the error with cxf ws-addressing in
>>>> DEBUG mode.
>>>> I can't figure out what's going on so any help would be appriecated.
>>>>
>>>> Thanks
>>>> Manuel
>>>>
>>>
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Manu <me...@gmail.com>.
It seems worse than I first thought ...
If 2 requests for the same asynchronous web service run in parallel, the
same problem occurs.
Can someone help me please ?
I'm totally lost ...
Le Mon Dec 15 2014 at 16:59:14, Manu <me...@gmail.com> a écrit :
It seems that when there is multiple asynchronous web service using the
> same decoupled endpoint that there some kind of correlating-message problem.
> Should I use a unique decoupledEndpoint for each asynchronous web service ?
>
>
> Le Mon Dec 15 2014 at 14:26:42, Manu <me...@gmail.com> a écrit :
>
> Does anyone have a clue on what's going on ?
>>
>>
>> Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
>>
>> Hi,
>>>
>>> Our application uses asynchronous invocation through ws-addressing a lot
>>> and randomly we have this error :
>>> [MAPCodec] Failed to correlate message, aborting dispatch.
>>>
>>> I've joined the full log trace for the error with cxf ws-addressing in
>>> DEBUG mode.
>>> I can't figure out what's going on so any help would be appriecated.
>>>
>>> Thanks
>>> Manuel
>>>
>>
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Manu <me...@gmail.com>.
It seems that when there is multiple asynchronous web service using the
same decoupled endpoint that there some kind of correlating-message problem.
Should I use a unique decoupledEndpoint for each asynchronous web service ?
Le Mon Dec 15 2014 at 14:26:42, Manu <me...@gmail.com> a écrit :
> Does anyone have a clue on what's going on ?
>
>
> Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
>
> Hi,
>>
>> Our application uses asynchronous invocation through ws-addressing a lot
>> and randomly we have this error :
>> [MAPCodec] Failed to correlate message, aborting dispatch.
>>
>> I've joined the full log trace for the error with cxf ws-addressing in
>> DEBUG mode.
>> I can't figure out what's going on so any help would be appriecated.
>>
>> Thanks
>> Manuel
>>
>
Re: WS-Addressing : [MAPCodec] Failed to correlate message
Posted by Manu <me...@gmail.com>.
Does anyone have a clue on what's going on ?
Le Fri Dec 12 2014 at 11:58:30, Manu <me...@gmail.com> a écrit :
> Hi,
>
> Our application uses asynchronous invocation through ws-addressing a lot
> and randomly we have this error :
> [MAPCodec] Failed to correlate message, aborting dispatch.
>
> I've joined the full log trace for the error with cxf ws-addressing in
> DEBUG mode.
> I can't figure out what's going on so any help would be appriecated.
>
> Thanks
> Manuel
>