WS-Addressing : [MAPCodec] Failed to correlate message

[Manu]

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

[Manu]

Does anyone have a clue on what's going on ?

Post by Manu
Hi,
Our application uses asynchronous invocation through ws-addressing a lot
[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

[Manu]

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 ?

Post by Manu
Does anyone have a clue on what's going on ?
Hi,

Post by Manu
Our application uses asynchronous invocation through ws-addressing a lot
[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

[Manu]

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 <***@gmail.com> a écrit :

It seems that when there is multiple asynchronous web service using the

Post by Manu
same decoupled endpoint that there some kind of correlating-message problem.
Should I use a unique decoupledEndpoint for each asynchronous web service ?
Does anyone have a clue on what's going on ?

Hi,

Post by Manu
Our application uses asynchronous invocation through ws-addressing a lot
[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

[Manu]

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 ...

Post by Manu
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 ...
It seems that when there is multiple asynchronous web service using the

Post by Manu
same decoupled endpoint that there some kind of correlating-message problem.
Should I use a unique decoupledEndpoint for each asynchronous web service ?
Does anyone have a clue on what's going on ?

Hi,

Post by Manu
Our application uses asynchronous invocation through ws-addressing a
[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

[Manu]

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 ?

Post by Manu
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 ...
It seems worse than I first thought ...

Post by Manu
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 ...
It seems that when there is multiple asynchronous web service using the

Post by Manu
same decoupled endpoint that there some kind of correlating-message problem.
Should I use a unique decoupledEndpoint for each asynchronous web service ?
Does anyone have a clue on what's going on ?

Hi,

Post by Manu
Our application uses asynchronous invocation through ws-addressing a
[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]

Post by Manu
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.

Post by Manu
Could this lead to an OutOfMemoryError ?

Hopefully no if the clients are cleaned up.

Dan

Post by Manu

Post by Manu
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 ...
It seems worse than I first thought ...

Post by Manu
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 ...
It seems that when there is multiple asynchronous web service using the

Post by Manu
same decoupled endpoint that there some kind of correlating-message problem.
Should I use a unique decoupledEndpoint for each asynchronous web service ?
Does anyone have a clue on what's going on ?

Hi,

Post by Manu
Our application uses asynchronous invocation through ws-addressing a
[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