On 15/05/2010 12:25, André Warnier wrote:
> Pid wrote:
>> On 14/05/2010 19:43, André Warnier wrote:
>>> Mark Thomas wrote:
>>> ...
>>>
TRACE & PUT could be tested safely but it is hard to test DELETE
without
causing some damage if it is permitted.
>>> Well, you could DELETE http
Pid wrote:
On 14/05/2010 19:43, André Warnier wrote:
Mark Thomas wrote:
...
TRACE & PUT could be tested safely but it is hard to test DELETE without
causing some damage if it is permitted.
Well, you could DELETE http://localhost/some-highly-unlikely-url
and check if you get a 404, couldn't y
On 14/05/2010 22:44, Licht Jiang wrote:
> I run a servlet on tomcat 5.5.27, jvm 1.6.0_10-b33, and fedora
> 2.6.21.7-2.fc8xen. The service has a problem: after running for a
> certain time, the servlet becomes unavailable because of "too many
> open files" exception:
>
> 2010-05-13 23:58:14,575 DEB
On 14/05/2010 19:21, Mark Shifman wrote:
> After playing around I don't think the leak is from JAXBContext. My web app
> is running under struts 1.3.10. I tested
> the blank web apps that comes with struts 1.3.10 and it showed a memory leak
> on undeploying and redeploying. (so did the
> blank w
On 14/05/2010 19:43, André Warnier wrote:
> Mark Thomas wrote:
> ...
>
>>
>> TRACE & PUT could be tested safely but it is hard to test DELETE without
>> causing some damage if it is permitted.
>>
> Well, you could DELETE http://localhost/some-highly-unlikely-url
> and check if you get a 404, could
