After switching to production mode, the problem does not seem to appear any more at first sight.
As the problem cannot be simulated by carrying out a specific action, but only occurs after a while,
I cannot confirm that it does not re-occur in production mode any more.
Again I have monitored file usage in production mode, and it seems that indeed at this moment,
the wicket main jar file is not opened multiple times as in development mode.
Opposed to the main jar, the extension jar has a growing number of file handles.
Right now I cannot tell if this will make the problem re-occur.
I'll keep you posted on future experience.
Thank you for the advice!
Tom Desmet
| "Johan Compagner"
<[EMAIL PROTECTED]>
Verzonden door: [EMAIL PROTECTED] 11/04/2006 15:51
|
|
When you set it to deployment mode what happens then?
If you want markup polling to see changes do set the
public void setResourcePollFrequency(final Duration resourcePollFrequency)
to a higher number like 10 seconds..
johan
On 4/11/06, Tom Desmet <[EMAIL PROTECTED]> wrote:
Hi all,
On my company, we have an issue with wicket 2.0 beta 3 and Resin 3.0.18.
After resin is active for a while, a stack trace occurs in the logfile with the following exception ...
FileNotFoundException (Too many open files). The exception occurs multiple times.
We have tested with our own application, and afterwards also with a clean resin installation with only the wicket sample application.
In both cases the problem occurs.
We are using SuSE 9.3 ( Linux linux01 2.6.11.4-21.7-smp #1 SMP Thu Jun 2 14:23:14 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux )
on an intel xeon.
We are using Sun JRE:
java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_06-b05, mixed mode)
Problem also occurs on JRockit:
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
BEA JRockit(R) (build R26.0.0-188-52875-1.5.0_04-20051110-0920-linux-x86_64, )
When investigating open file handles with lsof, it seems that the wicket jar files have a very high amount of open file handles (+/- 1000).
(I think the problem occurs when more than 1024 files are opened simultaneously)
All these file handles are allocated to the wicket jar files.
We have other resin instances running without wicket, and there the phenomenon does not occur,
so it is probably related to the combination Resin / Wicket.
Contents of /proc/sys/fs/file-max
203357
Contents of /proc/sys/fs/file-nr
5835 0 203357
Alle entries in /etc/security/limits.conf are commented out.
Resin is running as user root for testing purposes.
When investigating open file handles on other files, no extremely high file usage on other processes is detected.
Does someone have a clue what could be going on here? Has someone experienced something similar?
After googling for the problem, I did not bump in any eventual solution. All help would be welcome.
Thanks in advance for any reaction.
Tom Desmet
| ____________________________________________________________________________________________________________________________________ ATTENTION !! This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this message you are hereby notified that any use, distribution or reproduction of this message and any files is prohibited. If you have received this email in error please notify the system manager by sending this email to [EMAIL PROTECTED] . Any views expressed in this email are those of the individual sender and may not necessarily reflect the views of TVH - Group Thermote & Vanhalst. This footnote also confirms that this email message has been swept by our virus-scanning software for the presence of computer viruses. ____________________________________________________________________________________________________________________________________ |
