Re: file descriptor leak
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 any idea of when 1.4.4 will be released ? Maarten On Thu, Dec 3, 2009 at 9:46 AM, Johan Compagner wrote: 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. oups ! A special thank you to Johan to :) Thank you Maarten, I have set antiJarLocking to true. My application used to fail after 30 minutes (in deployment mode) before that. After setting that context parameter, I have not encountered any problem. The number of open file descriptors remains to a reasonable value. So I consider my problem solved. Thank you all for your help. Pascal. johan On Thu, Dec 3, 2009 at 09:41, Pascal Grange < pascal1.gra...@orange-ftgroup.com> wrote: 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 I am new to wicket and I need help to fix this. Searching for file descriptor leaks in wicket on google I found some old mailing-list post but that doesn't help me a lot so I post here :) I red about issues with jar url but the post are so old that I understand those are fixed bug ? No need to precise what versions of wicket stuffs I use, your can see that above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. Thanks for your help, Pascal. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. Multimedia Business Services shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. Multimedia Business Services shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely fo
Re: file descriptor leak
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 ? Maarten On Thu, Dec 3, 2009 at 9:46 AM, Johan Compagner wrote: 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. Thank you Maarten, I have set antiJarLocking to true. My application used to fail after 30 minutes (in deployment mode) before that. After setting that context parameter, I have not encountered any problem. The number of open file descriptors remains to a reasonable value. So I consider my problem solved. Thank you all for your help. Pascal. johan On Thu, Dec 3, 2009 at 09:41, Pascal Grange < pascal1.gra...@orange-ftgroup.com> wrote: 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 I am new to wicket and I need help to fix this. Searching for file descriptor leaks in wicket on google I found some old mailing-list post but that doesn't help me a lot so I post here :) I red about issues with jar url but the post are so old that I understand those are fixed bug ? No need to precise what versions of wicket stuffs I use, your can see that above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. Thanks for your help, Pascal. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. Multimedia Business Services shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. Multimedia Business Services shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
Re: file descriptor leak
its already fixed that way On Thu, Dec 3, 2009 at 12:15, Ilja Pavkovic 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 *always* recalculates lastModified. > > And lastModified() calls urlConnection.getInputstream().close(); > > > Best Regards, >Ilja Pavkovic > > Am Donnerstag, 3. Dezember 2009 11:40:04 schrieb Johan Compagner: > > 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 > wrote: > > > 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 > > > > > >wrote: > > > > > > > > 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 < > > > > > > > > pascal1.gra...@orange-ftgroup.com> wrote: > > > > > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > > > > > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > > > > > > > > > I am new to wicket and I need help to fix this. Searching for file > > > > > descriptor leaks in wicket on google I found some old mailing-list > > > > > post > > > > > > > > but > > > > > > > > > that doesn't help me a lot so I post here :) I red about issues > with > > > > > > jar > > > > > > > url > > > > > > > > > but the post are so old that I understand those are fixed bug ? > > > > > > > > > > No need to precise what versions of wicket stuffs I use, your can > see > > > > > > > > that > > > > > > > > > above. For java, it's version 1.5.0_14 and Tomcat version is > 5.5.25. > > > > > > > > > > Thanks for your help, > > > > > Pascal. > > > > > > > > > > > > > > > > > > > > Ce message et toutes les pieces jointes (ci-apres le "message") > sont > > > > > confidentiels et etablis a l'intention exclusive de ses > > > > > destinataires. Toute utilisation ou diffusion non autorisee est > > > > > interdite. > > > > > Tout message electronique est susceptible d'alteration. Multimedia > > > > > > > > Business > > > > > > > > > Services decline toute responsabilite au titre de ce message s'il a > > > > > ete altere, deforme ou falsifie. > > > > > Si vous n'etes pas destinataire de ce message, merci de le detruire > > > > > immediatement et d'avertir l'expediteur. > > > > > * > > > > > This message and any attachments (the "message") are confidential > and > > > > > intended solely for the addressees. Any unauthorised use or > > > > > > dissemination > > > > > > > is > > > > > > > > > prohibited. > > > > > Messages are susceptible to alteration. Multimedia Business > Services > > > > > > > > shall > > > > > > > > > not be liable for the message if altered, changed or > > > > > falsified. > > > > > If you are not the intended addressee of this message, please > cancel > > > > > it immediately and inform the sender. > > > > > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > -- > binaere bauten gmbh · tempelhofer ufer 1a · 10961 berlin > > +49 · 171 · 9342 465 > > Handelsregister: HRB 115854 - Amtsgericht Charlottenburg > Geschäftsführer: Dipl.-Inform. Ilja Pavkovic, Dipl.-Inform. Jost Becker > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
Re: file descriptor leak
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 Regards, Ilja Pavkovic Am Donnerstag, 3. Dezember 2009 11:40:04 schrieb Johan Compagner: > 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 wrote: > > 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 > > > >wrote: > > > > > > 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 < > > > > > > pascal1.gra...@orange-ftgroup.com> wrote: > > > > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > > > > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > > > > > > > I am new to wicket and I need help to fix this. Searching for file > > > > descriptor leaks in wicket on google I found some old mailing-list > > > > post > > > > > > but > > > > > > > that doesn't help me a lot so I post here :) I red about issues with > > > > jar > > > > > url > > > > > > > but the post are so old that I understand those are fixed bug ? > > > > > > > > No need to precise what versions of wicket stuffs I use, your can see > > > > > > that > > > > > > > above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. > > > > > > > > Thanks for your help, > > > > Pascal. > > > > > > > > > > > > > > > > Ce message et toutes les pieces jointes (ci-apres le "message") sont > > > > confidentiels et etablis a l'intention exclusive de ses > > > > destinataires. Toute utilisation ou diffusion non autorisee est > > > > interdite. > > > > Tout message electronique est susceptible d'alteration. Multimedia > > > > > > Business > > > > > > > Services decline toute responsabilite au titre de ce message s'il a > > > > ete altere, deforme ou falsifie. > > > > Si vous n'etes pas destinataire de ce message, merci de le detruire > > > > immediatement et d'avertir l'expediteur. > > > > * > > > > This message and any attachments (the "message") are confidential and > > > > intended solely for the addressees. Any unauthorised use or > > > > dissemination > > > > > is > > > > > > > prohibited. > > > > Messages are susceptible to alteration. Multimedia Business Services > > > > > > shall > > > > > > > not be liable for the message if altered, changed or > > > > falsified. > > > > If you are not the intended addressee of this message, please cancel > > > > it immediately and inform the sender. > > > > > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > > For additional commands, e-mail: users-h...@wicket.apache.org > -- binaere bauten gmbh · tempelhofer ufer 1a · 10961 berlin +49 · 171 · 9342 465 Handelsregister: HRB 115854 - Amtsgericht Charlottenburg Geschäftsführer: Dipl.-Inform. Ilja Pavkovic, Dipl.-Inform. Jost Becker - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: file descriptor leak
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 wrote: > 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 >wrote: > > > 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 < > > pascal1.gra...@orange-ftgroup.com> wrote: > > > > > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > > > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > > > > > I am new to wicket and I need help to fix this. Searching for file > > > descriptor leaks in wicket on google I found some old mailing-list post > > but > > > that doesn't help me a lot so I post here :) I red about issues with > jar > > url > > > but the post are so old that I understand those are fixed bug ? > > > > > > No need to precise what versions of wicket stuffs I use, your can see > > that > > > above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. > > > > > > Thanks for your help, > > > Pascal. > > > > > > > > > > > > Ce message et toutes les pieces jointes (ci-apres le "message") sont > > > confidentiels et etablis a l'intention exclusive de ses destinataires. > > > Toute utilisation ou diffusion non autorisee est interdite. > > > Tout message electronique est susceptible d'alteration. Multimedia > > Business > > > Services decline toute responsabilite au titre de ce message s'il a ete > > > altere, deforme ou falsifie. > > > Si vous n'etes pas destinataire de ce message, merci de le detruire > > > immediatement et d'avertir l'expediteur. > > > * > > > This message and any attachments (the "message") are confidential and > > > intended solely for the addressees. Any unauthorised use or > dissemination > > is > > > prohibited. > > > Messages are susceptible to alteration. Multimedia Business Services > > shall > > > not be liable for the message if altered, changed or > > > falsified. > > > If you are not the intended addressee of this message, please cancel it > > > immediately and inform the sender. > > > > > > > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > >
Re: file descriptor leak
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 : > 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 wrote: > > > 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 < > > pascal1.gra...@orange-ftgroup.com> wrote: > > > > > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > > > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > > > > > I am new to wicket and I need help to fix this. Searching for file > > > descriptor leaks in wicket on google I found some old mailing-list post > > but > > > that doesn't help me a lot so I post here :) I red about issues with jar > > url > > > but the post are so old that I understand those are fixed bug ? > > > > > > No need to precise what versions of wicket stuffs I use, your can see > > that > > > above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. > > > > > > Thanks for your help, > > > Pascal. > > > > > > > > > > > > Ce message et toutes les pieces jointes (ci-apres le "message") sont > > > confidentiels et etablis a l'intention exclusive de ses destinataires. > > > Toute utilisation ou diffusion non autorisee est interdite. > > > Tout message electronique est susceptible d'alteration. Multimedia > > Business > > > Services decline toute responsabilite au titre de ce message s'il a ete > > > altere, deforme ou falsifie. > > > Si vous n'etes pas destinataire de ce message, merci de le detruire > > > immediatement et d'avertir l'expediteur. > > > * > > > This message and any attachments (the "message") are confidential and > > > intended solely for the addressees. Any unauthorised use or dissemination > > is > > > prohibited. > > > Messages are susceptible to alteration. Multimedia Business Services > > shall > > > not be liable for the message if altered, changed or > > > falsified. > > > If you are not the intended addressee of this message, please cancel it > > > immediately and inform the sender. > > > > > > > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > > > - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: file descriptor leak
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 wrote: > 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 < > pascal1.gra...@orange-ftgroup.com> wrote: > > > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > > > I am new to wicket and I need help to fix this. Searching for file > > descriptor leaks in wicket on google I found some old mailing-list post > but > > that doesn't help me a lot so I post here :) I red about issues with jar > url > > but the post are so old that I understand those are fixed bug ? > > > > No need to precise what versions of wicket stuffs I use, your can see > that > > above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. > > > > Thanks for your help, > > Pascal. > > > > > > > > Ce message et toutes les pieces jointes (ci-apres le "message") sont > > confidentiels et etablis a l'intention exclusive de ses destinataires. > > Toute utilisation ou diffusion non autorisee est interdite. > > Tout message electronique est susceptible d'alteration. Multimedia > Business > > Services decline toute responsabilite au titre de ce message s'il a ete > > altere, deforme ou falsifie. > > Si vous n'etes pas destinataire de ce message, merci de le detruire > > immediatement et d'avertir l'expediteur. > > * > > This message and any attachments (the "message") are confidential and > > intended solely for the addressees. Any unauthorised use or dissemination > is > > prohibited. > > Messages are susceptible to alteration. Multimedia Business Services > shall > > not be liable for the message if altered, changed or > > falsified. > > If you are not the intended addressee of this message, please cancel it > > immediately and inform the sender. > > > > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > >
Re: file descriptor leak
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 < pascal1.gra...@orange-ftgroup.com> wrote: > 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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 > lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 > > I am new to wicket and I need help to fix this. Searching for file > descriptor leaks in wicket on google I found some old mailing-list post but > that doesn't help me a lot so I post here :) I red about issues with jar url > but the post are so old that I understand those are fixed bug ? > > No need to precise what versions of wicket stuffs I use, your can see that > above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. > > Thanks for your help, > Pascal. > > > > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'intention exclusive de ses destinataires. > Toute utilisation ou diffusion non autorisee est interdite. > Tout message electronique est susceptible d'alteration. Multimedia Business > Services decline toute responsabilite au titre de ce message s'il a ete > altere, deforme ou falsifie. > Si vous n'etes pas destinataire de ce message, merci de le detruire > immediatement et d'avertir l'expediteur. > * > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised use or dissemination is > prohibited. > Messages are susceptible to alteration. Multimedia Business Services shall > not be liable for the message if altered, changed or > falsified. > If you are not the intended addressee of this message, please cancel it > immediately and inform the sender. > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
file descriptor leak
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 -p 24689 | grep wicket-datetime-1.3.4.jar | wc -l -> 401 lsof -p 24689 | grep wicket-extensions-1.3.4.jar | wc -l -> 6 I am new to wicket and I need help to fix this. Searching for file descriptor leaks in wicket on google I found some old mailing-list post but that doesn't help me a lot so I post here :) I red about issues with jar url but the post are so old that I understand those are fixed bug ? No need to precise what versions of wicket stuffs I use, your can see that above. For java, it's version 1.5.0_14 and Tomcat version is 5.5.25. Thanks for your help, Pascal. Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message electronique est susceptible d'alteration. Multimedia Business Services decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur. * This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. Multimedia Business Services shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
