Open files

Can you explain why the multip platform edition running on a red hat enterprise edition server woul have 600+ files open. When we kill the agent.sh they all go away and when we start it back up the same number of files are open. On top of that it seems to open the same files multiple times. Below is a list of the files that it opens several times. I checked and it does this on multiple servers we have the multi-platform edition running on.

java 30632 root mem REG 8,3 8945 686069 /usr/local/java/j2re1.4.2_15/lib/ext/dnsns.jar
java 30632 root mem REG 8,3 24068652 572029 /usr/local/java/j2re1.4.2_15/lib/rt.jar
java 30632 root mem REG 8,3 89796 571978 /usr/local/java/j2re1.4.2_15/lib/sunrsasign.jar
java 30632 root mem REG 8,3 889364 571987 /usr/local/java/j2re1.4.2_15/lib/jsse.jar
java 30632 root mem REG 8,3 70480 571979 /usr/local/java/j2re1.4.2_15/lib/jce.jar
java 30632 root mem REG 8,3 111651 686068 /usr/local/java/j2re1.4.2_15/lib/ext/sunjce_provider.jar
java 30632 root mem REG 8,3 53248 686071 /usr/local/java/j2re1.4.2_15/lib/ext/ldapsec.jar
java 30632 root mem REG 8,3 54665 767343 /usr/local/24x7_Scheduler/activation.jar
java 30632 root mem REG 8,3 110681 766915 /usr/local/24x7_Scheduler/commons-beanutils-1.5.jar
java 30632 root mem REG 8,3 6041857 572027 /usr/local/java/j2re1.4.2_15/lib/charsets.jar
java 30632 root mem REG 8,3 46725 767318 /usr/local/24x7_Scheduler/commons-codec-1.3.jar
java 30632 root mem REG 8,3 3227888 766923 /usr/local/24x7_Scheduler/jscheduler.jar
java 30632 root mem REG 8,3 764405 686083 /usr/local/java/j2re1.4.2_15/lib/ext/localedata.jar
java 30632 root mem REG 8,3 274149 767330 /usr/local/24x7_Scheduler/SNMP4J.jar
java 30632 root mem REG 8,3 165119 766906 /usr/local/24x7_Scheduler/commons-collections-2.1.jar
java 30632 root mem REG 8,3 18404 766908 /usr/local/24x7_Scheduler/commons-logging-api-1.0.2.jar
java 30632 root mem REG 8,3 174619 767327 /usr/local/24x7_Scheduler/commons-net-1.4.0.jar
java 30632 root mem REG 8,3 189924 767332 /usr/local/24x7_Scheduler/concurrent.jar
java 30632 root mem REG 8,3 9423 766903 /usr/local/24x7_Scheduler/console.jar
java 30632 root mem REG 8,3 64596 767322 /usr/local/24x7_Scheduler/jdpb24x7.jar
java 30632 root mem REG 8,3 963513 766912 /usr/local/24x7_Scheduler/jgl3.1.0.jar
java 30632 root mem REG 8,3 10384 767319 /usr/local/24x7_Scheduler/jalt.jar
java 30632 root mem REG 8,3 550903 766907 /usr/local/24x7_Scheduler/jasperreports-0.5.3.jar
java 30632 root mem REG 8,3 74784 766920 /usr/local/24x7_Scheduler/jawin.jar
java 30632 root mem REG 8,3 354611 766922 /usr/local/24x7_Scheduler/jcommon-0.9.6.jar
java 30632 root mem REG 8,3 955401 766910 /usr/local/24x7_Scheduler/jfreechart-0.9.21.jar
java 30632 root mem REG 8,3 138822 766909 /usr/local/24x7_Scheduler/jgraph.jar
java 30632 root mem REG 8,3 138110 767315 /usr/local/24x7_Scheduler/jgraphaddons.jar
java 30632 root mem REG 8,3 588596 766905 /usr/local/24x7_Scheduler/jhall.jar
java 30632 root mem REG 8,3 699081 767340 /usr/local/24x7_Scheduler/js.jar
java 30632 root mem REG 8,3 352668 767317 /usr/local/24x7_Scheduler/log4j-1.2.8.jar
java 30632 root mem REG 8,3 338486 766911 /usr/local/24x7_Scheduler/looks-1.3.1.jar
java 30632 root mem REG 8,3 327603 767351 /usr/local/24x7_Scheduler/mail.jar
java 30632 root mem REG 8,3 71537 767321 /usr/local/24x7_Scheduler/vb24x7.jar
java 30632 root mem REG 8,3 517761 767320 /usr/local/24x7_Scheduler/velocity-dep-1.4.jar

You are likely hitting known bug in Sun's version of Java. Here is the link describing the problem http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4189011. It refers to Windows as the affected system while in fact this bug affects all platforms across the board including Red Hat. We have reports from other users hitting this on different platforms. The bug seems to be specific to earlier releases of JDK 1.4.

As far as I know this bug has been fixed in 1.4.2_15 and later maintenance releases. I also think the bug is not present in BEA and IBM versions of JDK, but these systems have their own share of problems.