Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 57412 invoked from network); 5 Dec 2010 14:26:43 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 5 Dec 2010 14:26:43 -0000 Received: (qmail 64512 invoked by uid 500); 5 Dec 2010 14:26:43 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 64185 invoked by uid 500); 5 Dec 2010 14:26:41 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 64168 invoked by uid 99); 5 Dec 2010 14:26:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Dec 2010 14:26:40 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sberyozkin@gmail.com designates 209.85.214.41 as permitted sender) Received: from [209.85.214.41] (HELO mail-bw0-f41.google.com) (209.85.214.41) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Dec 2010 14:26:32 +0000 Received: by bwz16 with SMTP id 16so17331508bwz.0 for ; Sun, 05 Dec 2010 06:26:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=mh6ntj6j3vdqwQi3Hg/+BZVgzLw2o4kH17R/Pt/IfQs=; b=dLJpX7qKbK34Dd+nRFbIqa25srVFusDgKR01C8pRzRNRI9zBCUueT4zG+2dV1xBjAD nG5jTKE20Yy84jiZL2RAeIZFwUnPBHL/2Ox9He4KI1Gg0f1Scnfx7xtkUiDTOKMU+ync hA9etvisAyPcGXdep5xWDA5lQGBlxzoaWFXc4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=j1c4fcG3c1RBIK4wDdEkbXNN/eI8X7rcRywdrWMlqDXyxMVfvt6Vct4FQZudBTW170 Lzz4PrtIeXls+ObydIKOX4LmZ46beEM7QsaMHZsDWKynWY+ipc5T6DrcMoo0hZB9H+D+ LpkgCandkxO07hUlJrGY0SRW3GW6bgayH/BxM= MIME-Version: 1.0 Received: by 10.204.100.139 with SMTP id y11mr4627573bkn.93.1291559171823; Sun, 05 Dec 2010 06:26:11 -0800 (PST) Received: by 10.204.80.69 with HTTP; Sun, 5 Dec 2010 06:26:11 -0800 (PST) Date: Sun, 5 Dec 2010 14:26:11 +0000 Message-ID: Subject: Two way requests can get ahead of oneway requests ? From: Sergey Beryozkin To: dev@cxf.apache.org Content-Type: multipart/alternative; boundary=001485f796e2a499e80496aa8d14 X-Virus-Checked: Checked by ClamAV on apache.org --001485f796e2a499e80496aa8d14 Content-Type: text/plain; charset=ISO-8859-1 Hi I've noticed, while working on my demo, that if a proxy executes two operations, with the 1st one being a oneway operation, then sometimes the server sees the 2nd operation being invoked first. I can see why it is happening and obviously the server code should not make any assumptions in this case, but can CXF at least make the best effort, perhaps by increasing the priority of the server threads dealing with the actual execution of oneway requests ? Thoughts ? Sergey --001485f796e2a499e80496aa8d14--