Re: [Wicket-user] [Wicket-develop] [ wicket-Patches-1562130 ] File descriptor leak in URLResourceStream

2006-11-27 Thread Sebastiaan van Erk
[I sent this mail to wicket-develop as well, but I have not seen it there yet, is that list filtered?]. This is a workaround method for the wicket developers to solve the problem with Too many open files that a lot of people have been having. It's a bug in Sun's JarURLConnection (I reported

Re: [Wicket-user] [Wicket-develop] [ wicket-Patches-1562130 ] File descriptor leak in URLResourceStream

2006-11-27 Thread Johan Compagner
So instead of opening a connection inside the jar we just open a connection to the jar only. That would work for the app servers that uses the jar url connection but it won't help for example WebLogic and others. Because they use there own kind of thing.. johan On 11/27/06, Sebastiaan van Erk

Re: [Wicket-user] [Wicket-develop] [ wicket-Patches-1562130 ] File descriptor leak in URLResourceStream

2006-11-27 Thread Eelco Hillenius
On 11/27/06, Sebastiaan van Erk [EMAIL PROTECTED] wrote: [I sent this mail to wicket-develop as well, but I have not seen it there yet, is that list filtered?] The old dev list is shut down. You should have received a message stating this. Now that we're incubating Wicket, we moved the dev list

Re: [Wicket-user] [Wicket-develop] [ wicket-Patches-1562130 ] File descriptor leak in URLResourceStream

2006-11-27 Thread Eelco Hillenius
We could still apply this common case, and maybe test for the specific ones (web logic, which uses a zip variant, right?) if possible. WDYT Johan? Eelco On 11/27/06, Johan Compagner [EMAIL PROTECTED] wrote: So instead of opening a connection inside the jar we just open a connection to the jar