Actually, I think it had to do with the version of derby I was using. The docs said use derby-10.1.3.1.jar or later. I was using derby-10.3.2.1.jar. I changed it do use derby-10.1.3.1.jar and the problem disappeared.
It might be a good idea to add a warning or have someone else confirm and then add a warning to the tomcat documentation It caused us a lot of issues and in fact cause our entire primary server to crash. If other people do not have some type of high availability configuration they could really end up in a bind and be quite upset. -----Original Message----- From: Henri Gomez [mailto:[EMAIL PROTECTED] Sent: Saturday, April 12, 2008 9:50 AM To: archiva-users@maven.apache.org Subject: Re: too many open files with 1.0.2 I see that also but it was releated to a problem with Tomcat 6.x and libtcnative. Is it your setting ? >2008/4/11, Jason Chaffee <[EMAIL PROTECTED]>: > With Archvia-1.0.2 running in tomcat, I am getting "too many open files" > errors at least twice a day, forcing a reboot of archiva to fix the > issue. When I run "lsof", I see that the database files are open more > than once so I suspect a resource leak. Is anyone else seeing this? > >
