Hello,
I observe file descriptor leaks when running my wicket application. By
leak I mean that the java process tries to open more than 1024 file
descriptors. When I lsof the process, here is what I see :
lsof -p 24689 | wc -l - 1095
lsof -p 24689 | grep wicket-1.3.4.jar | wc -l - 522
lsof
We try to do our best, but the problem is that this is a leak internal to
java itself (classloader and urlconnection)
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html
play with antiJarLocking and antiResouceLocking attributes.
johan
On Thu, Dec 3, 2009 at 09:41, Pascal Grange
Have you seen this thread:
http://www.mail-archive.com/users@wicket.apache.org/msg43879.html
Maarten
On Thu, Dec 3, 2009 at 9:46 AM, Johan Compagner jcompag...@gmail.comwrote:
We try to do our best, but the problem is that this is a leak internal to
java itself (classloader and urlconnection)
http://issues.apache.org/jira/browse/WICKET-2534
I think this will be fixed in 1.4.4
Witold
Am Thu, 3 Dec 2009 10:56:38 +0100
schrieb Maarten Bosteels mbosteels@gmail.com:
Have you seen this thread:
http://www.mail-archive.com/users@wicket.apache.org/msg43879.html
Maarten
On Thu,
ahh
i did knew that there was already code for that in place
but thats only in the lastMofified() method... of that UrlResourceStream
not in the constructor..
On Thu, Dec 3, 2009 at 10:56, Maarten Bosteels mbosteels@gmail.comwrote:
Have you seen this thread:
Hi,
I wonder if the complete lastModified evaluation in the constructor is
necessary at all. The only place were lastModified is used is in the function
lastModified() . This one *always* recalculates lastModified.
And lastModified() calls urlConnection.getInputstream().close();
Best
its already fixed that way
On Thu, Dec 3, 2009 at 12:15, Ilja Pavkovic ilja.pavko...@binaere-bauten.de
wrote:
Hi,
I wonder if the complete lastModified evaluation in the constructor is
necessary at all. The only place were lastModified is used is in the
function
lastModified() . This one
Maarten Bosteels a écrit :
Have you seen this thread:
http://www.mail-archive.com/users@wicket.apache.org/msg43879.html
I had not seen this thread, thank you. It seems this issue will be fixed
in wicket-1.4.4 (saw it in the thread). Do we have any idea of when
1.4.4 will be released ?
pascal1.gra...@orange-ftgroup.com a écrit :
Maarten Bosteels a écrit :
Have you seen this thread:
http://www.mail-archive.com/users@wicket.apache.org/msg43879.html
I had not seen this thread, thank you. It seems this issue will be
fixed in wicket-1.4.4 (saw it in the thread). Do we have
