Java program always hang.. message "Too many open files" appears sometime.

[NiCK_76]

Hi ,

perform command lsof will appear following error message.
java 21929 mms31 53u sock 0,0 15544497 can't
identify protocol
java 21929 mms31 54u sock 0,0 15544498 can't
identify protocol
java 21929 mms31 55u sock 0,0 15544522 can't
identify protocol
java 21929 mms31 56u sock 0,0 15544523 can't
identify protocol
java 21929 mms31 57u sock 0,0 15544562 can't
identify protocol
........

my platform:
Redhat enterprice AS3 update 4 x86_64
j2sdk1.4.2_03
CPU Intel(R) Xeon(TM) CPU 2.80GHz *2
MEMORY 2G

Thanks.

NiCK

[Steven E. Protter]

Seems like you may want to increase the number of open files permitted with the kernel.

If I'm right, adding memory will do no good.

Java could stand some patching though.

SEP

[T G Manikandan]

check the value of /proc/sys/fs/file-max.

cat /proc/sys/fs/file-max

if the value is low increase the number.

echo 10000 > /proc/sys/fs/file-max

This will change the kernel limit.No need to reboot.

[NiCK_76]

cat /proc/sys/fs/file-max
209689

[Dave Falloon]

More likely its a problem with the ulimit set for the user you are running the program as.

If you use bash you can check the number of open files allowed by the shell with the following command:

ulimit -f

or all limits with this:

ulimit -a

ulimit is built into bash. All its documentation is in the bash man page.

man bash then search for ulimit.

--Dave

[Dave Falloon]

Woops, ulimit -f is the file size switch, you'll want the -n

snipped from the man page:

-n The maximum number of open file descriptors

--Dave

[NiCK_76]

I use ulimit to change number of open file to 2048, but problem still happen.

Anything else?

Now,I upgrade jdk from 1.4.2-03 to 1.4.2-08 to have a try.

[Dave Falloon]

You could try ulimit -n unlimited

I remember having trouble with a Analog CAD tool that used this really clunky java GUI and it would spawn a hundred garbage file descriptors anytime you clicked on a icon so eventually it would tank with too many open files.

If it still doesn't work then it could be your /proc/sys/fs files like other people have said:

file-max
inode-max ( if your system has an inode-max file )

--Dave