users@jersey.java.net

Re: [Jersey] Refactoring the container SPI

From: Paul Sandoz <Paul.Sandoz_at_Sun.COM>
Date: Thu, 12 Jun 2008 15:53:08 +0200

Jeanfrancois Arcand wrote:
> Hum...the GrizzlyAdapter has the following code:
>
>> GrizzlyRequest request = (GrizzlyRequest)
>> req.getNote(ADAPTER_NOTES);
>> GrizzlyResponse response = (GrizzlyResponse)
>> res.getNote(ADAPTER_NOTES);
>>
>> if (request == null || response == null) {
>> return;
>> }
>> try {
>> response.finishResponse();
>> req.action(ActionCode.ACTION_POST_REQUEST, null);
>> res.finish();
>> } catch (Throwable t) {
>> getLogger().log(Level.SEVERE,"afterService exception",t);
>> } finally {
>> // Recycle the wrapper request and response
>> request.recycle();
>> response.recycle();
>> req.recycle();
>> res.recycle();
>> }
>> try{
>> afterService(request,response);
>> } catch (Exception ex){
>> logger.log(Level.SEVERE,"afterService", ex);
>> throw ex;
>> }
>
> Which close the connection. Which test case should I look at to
> reproduce and debug the issue?
>

There is no issue. All the Jersey-Grizzly unit tests pass. I think i am
mistaken: i thought that it was the responsibility of the
GrizzlyContainer to close the output stream of the response.

Paul.

-- 
| ? + ? = To question
----------------\
    Paul Sandoz
         x38109
+33-4-76188109