Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Daniel Kulp <dkulp@apache.org>
To: dev@cxf.apache.org
Subject: Re: Two way requests can get ahead of oneway requests ?
Date: Mon, 6 Dec 2010 14:02:52 -0500
User-Agent: KMail/1.13.5 (Linux/2.6.36; KDE/4.5.3; x86_64; ; )
Cc: Sergey Beryozkin <sberyozkin@gmail.com>
References: <AANLkTinGjzMy6qTspd5XEJiYExWKbbTLi2s=3oY2jZBk@mail.gmail.com>
In-Reply-To: <AANLkTinGjzMy6qTspd5XEJiYExWKbbTLi2s=3oY2jZBk@mail.gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201012061402.52832.dkulp@apache.org>

On Sunday 05 December 2010 9:26:11 am Sergey Beryozkin wrote:
> 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 ?

I was thinking about a possible sync on the runnable, stick it on the 
executor, then a wait(10) with the background thread doing a notifyAll once it 
starts.   If the executor is not busy/full, then that should allow it to 
continue without tieing up the Jetty/servlet thread for very long.  If the 
executors are busy, it will return FAIRLY quick.  Possibly make that 
configurable.

Dan


> 
> Thoughts ?
> 
> Sergey

-- 
Daniel Kulp
dkulp@apache.org
http://dankulp.com/blog