Return-Path: X-Original-To: apmail-cxf-users-archive@www.apache.org Delivered-To: apmail-cxf-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03A0D10D1E for ; Tue, 16 Dec 2014 21:33:56 +0000 (UTC) Received: (qmail 17034 invoked by uid 500); 16 Dec 2014 21:33:55 -0000 Delivered-To: apmail-cxf-users-archive@cxf.apache.org Received: (qmail 16970 invoked by uid 500); 16 Dec 2014 21:33:55 -0000 Mailing-List: contact users-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cxf.apache.org Delivered-To: mailing list users@cxf.apache.org Received: (qmail 16959 invoked by uid 99); 16 Dec 2014 21:33:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 21:33:55 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE X-Spam-Check-By: apache.org Received-SPF: error (athena.apache.org: local policy) Received: from [216.40.44.33] (HELO smtprelay.hostedemail.com) (216.40.44.33) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Dec 2014 21:33:49 +0000 Received: from filter.hostedemail.com (unknown [216.40.38.60]) by smtprelay08.hostedemail.com (Postfix) with ESMTP id 0538B29DDFE for ; Tue, 16 Dec 2014 21:32:56 +0000 (UTC) X-Session-Marker: 64616E406B756C702E636F6D X-Spam-Summary: 50,0,0,,d41d8cd98f00b204,dkulp@apache.org,::mektoub@gmail.com,RULES_HIT:41:152:355:379:541:564:599:800:960:967:968:973:988:989:1260:1277:1311:1313:1314:1345:1359:1381:1437:1513:1515:1516:1518:1521:1534:1542:1593:1594:1711:1730:1747:1777:1792:2393:2525:2553:2561:2564:2682:2685:2693:2859:2900:2933:2937:2939:2942:2945:2947:2951:2954:3022:3138:3139:3140:3141:3142:3354:3865:3866:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4184:4659:5007:6119:6261:7514:7875:7903:8660:8957:9015:9025:9036:9388:10004:10400:10848:11232:11257:11651:11658:11914:12043:12517:12519:12663:12740:13019:13095:13148:13230:13891:13972:21060:21080,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fu,MSBL:0,DNSBL:none,Custom_rules:0:0:0 X-HE-Tag: cry61_537a1eccdad1b X-Filterd-Recvd-Size: 3762 Received: from server.dankulp.com (cn1.dankulp.com [64.85.173.253]) (Authenticated sender: dan@kulp.com) by omf08.hostedemail.com (Postfix) with ESMTPA for ; Tue, 16 Dec 2014 21:32:53 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: WS-Addressing : [MAPCodec] Failed to correlate message From: Daniel Kulp In-Reply-To: Date: Tue, 16 Dec 2014 16:32:48 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <19A50448-0E9C-419F-A8B9-271CAB861458@apache.org> References: To: users@cxf.apache.org, Manu X-Mailer: Apple Mail (2.1993) X-Virus-Checked: Checked by ClamAV on apache.org > On Dec 16, 2014, at 8:18 AM, Manu wrote: >=20 > 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 >=20 >=20 > Le Tue Dec 16 2014 at 13:29:56, Manu a =C3=A9crit = : >=20 >> 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 .. >>=20 >> Precision : I'm not usng jetty but the ServletDestination for = handling the >> response ... >>=20 >>=20 >>=20 >> Le Tue Dec 16 2014 at 12:41:07, Manu a =C3=A9crit = : >>=20 >> 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 ... >>>=20 >>> Le Mon Dec 15 2014 at 16:59:14, Manu a =C3=A9crit = : >>>=20 >>> 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 ? >>>>=20 >>>>=20 >>>> Le Mon Dec 15 2014 at 14:26:42, Manu a =C3=A9crit= : >>>>=20 >>>> Does anyone have a clue on what's going on ? >>>>>=20 >>>>>=20 >>>>> Le Fri Dec 12 2014 at 11:58:30, Manu a =C3=A9cri= t : >>>>>=20 >>>>> Hi, >>>>>>=20 >>>>>> Our application uses asynchronous invocation through = ws-addressing a >>>>>> lot and randomly we have this error : >>>>>> [MAPCodec] Failed to correlate message, aborting dispatch. >>>>>>=20 >>>>>> 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. >>>>>>=20 >>>>>> Thanks >>>>>> Manuel >>>>>>=20 >>>>>=20 --=20 Daniel Kulp dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com