Salut,
Vrignaud Etienne wrote:
> Hello,
>
> Here are some additional details about the troubles that I have with the
> test case that I submited.
> When my server takes time (0 to 4 secondes) between each 30 responses, the
> memory usage grows abnormally. And the memory is never returned back. In
> that case the complete execution of the 500 requests done by the ArpClient
> class put the server part to 99 Mo of memory usage (while the memory usage
> when the server answers without taking time is about 31 Mo).
>
> I considered and tried your idea of calling AsyncExecutor.postExecute() that
> release back the ARP resource. In my code I use already
> asyncHandler.handle(asyncTask); that at the end calls postExecute(). So
> adding a call to the postExecute() method only issued a
> NullPointerException.
> So nothing goes better.
>
> I think perhaps it will be good to check whether or not its a grizzly issue
> before publishing the 1.9.0 version of grizzly.
I don't see such issues with Comet, witch build on top of ARP. But I
will try to look at your code ASAP to see if I can find something.
Thanks for the feedback!
-- Jeanfrancois
>
> Thanks for your help,
> Regards,
> Etienne VRIGNAUD
>