Properties of a J2EE application

[Aaliya Seth]

Hello,
I need help solving a problem loading the properties of a J2EE application. I have a class that extends Configuration Properties and load the properties files from their url with this statement:

this.load(url.openStream());

The change of properties is taken hot so I periodically scans the config files, and after a while I get this error:

java.io.FileNotFoundException: "Filename" (Too many open files)

Obviously there is saturation of the file handle. Is it necessary to do something special to properly close files after reading them?

[GlassFish]

Hello,
Just follow the following lines of code and it is done.

inputStream input = null;
try {
   input = url.openStream();
   this.load(input);
} finputally {
   if (input! = null) {
     input.close();
   }
}

(Not to mention the management of IOException, which depends on the method signature).

[Windowed]

Hello,
There are very long, really long time before the C + + there, I remember having to recompile the Linux kernel to increase the number of file descriptor. It is a problem with your OS or application (server I imagine that too many files or sockets open, or you left unsealed streams into objects that are still in use). You have probably hundreds of file descriptor. You should try to get how many are allocated. And you program should have more details.

[NetWorkInG]

Hello,
If you're looking at the Linux command "ulimit-a" this gives you a lot of information about your configuration.

$ Ulimit-a
core file size          (blocks,-c) 0
data seg size           (kb,-d) unlimited
scheduling priority             (-e) 0
file size               (blocks,-f) unlimited
pending signals                 (-i) 49842
max locked memory       (kb,-l) 32
Max memory size         (kb,-m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes,-p) 8
POSIX message queues     (bytes,-q) 819212
real-time priority              (-r) 0
stack size              (kb,-s) 10440
cpu time               (seconds,-t) unlimited
max user processes              (-u) 42552
virtual memory          (kb,-v) unlimited
File Lock                      (-x) unlimited

Check this configuration this may help you.

[SoftWore]

Hi,
Unless you have very large need that forces you to open simultaneously in a large number of files, you should not change the system limit. As shown yann2Your problem is that you do not shut your flow, and therefore you increase gradually the number of file / open resources. In closing the problem neatly disappear You do not need to handle null, and you can use the following syntax:

InputStream input = url.openStream(); / / If nothinputg is done IOException
try {
   this.load(input);
} finally {
   input.close();
}

[Aaliya Seth]

Hello,
Indeed, the problem is solved with the finally clause that closes the flow. Thanks for your replies guys.

finally {
   input.close();
}

And also if this can be done in other way without using the finally block then I am interested. Thanks in advance.