Too many open files with jxta 2.4.1 on nfs. Any solution?
I am developing a distributed computing network using jxta.
The directory that the application and jxta is located in is mounted via nfs.
The problem is that in the .jxta/cm/uuid-SOMETHING/srdi/.nfsXXXX files keep building up, and are never removed, leading to a "too many open files" exception after the ulimit of open files (1024 in my case) is reached.
According to an nfs faq (http://nfs.sourceforge.net/ ;see 'D2. What is a "silly rename"? Why do these .nfsXXXXX files keep showing up?'):
"Unix applications often open a scratch file and then unlink it. They do this so that the file is not visible in the file system name space to any other applications, and so that the system will automatically clean up (delete) the file when the application exits. This is known as "delete on last close", and is a tradition among Unix applications.
Because of the design of the NFS protocol, there is no way for a file to be deleted from the name space but still remain in use by an application. Thus NFS clients have to emulate this using what already exists in the protocol. If an open file is unlinked, an NFS client renames it to a special name that looks like ".nfsXXXXX". This "hides" the file while it remains in use. This is known as a "silly rename." Note that NFS servers have nothing to do with this behavior."
My question is now:
does anyone know of where in the jxta src such file operations would take place, or if it's know that jxta does maybe not close filestreams properly?
Where would changes of that behaviour have to be made
Or might there be another solution to that problem (because increasing ulimit would just lead to a later "death")?
Thanx very much in advance.
Message was edited by: lutey