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: Async http requests and workqueue....
Date: Wed, 05 Oct 2011 21:31:30 -0400
Message-ID: <23550744.lmGD4TzWaC@dilbert.dankulp.com>
User-Agent: KMail/4.7.1 (Linux/3.0.1; KDE/4.7.1; x86_64; ; )
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"


I have a question for folks to see what folks would think is the "best 
option".    Basically, if you use one of the JAX-WS async methods on a client 
when talking to an HTTP service, we have to put a runnable on the workqueue to 
handle the response.   The question is, what should we do if the workqueue is 
full?  Could options:

1) (current behavior) Throw the RejectedExecutionException so the user knows 
they are exceeding defaults and likely should reconfigure things.

2) Loop in a Thread.yield and retry putting it on the queue until successfull. 

3) Run the runnable synchronously on the calling thread. 

Likely 2 and 3 would both log a WARNING to let the user know to reconfigure.


Obviously, the best solution would be to finish the work I did to use the 
apache http-client instead of the HttpURLConnection, but lets not go there 
right now.  :-)

Anyway, thoughts?


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