You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by Jason Chaffee <ja...@tvworks.com> on 2008/04/11 11:28:30 UTC

too many open files with 1.0.2

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?  


Re: too many open files with 1.0.2

Posted by Marc Gassmann <ma...@netcetera.ch>.
hi henri

will try, thanks :-)



Henri Gomez wrote:
>> I use derby-10.1.3.1.jar and still have the same issue.
>>
>> does anybody knows an other solution?
>>
>> and where can I extend the open files?
>>
>> cheers marc
> 
> On linux, you should use ulimit :
> 
> example on the archiva startup script :
> 
> ulimit -n 2048
> 
> java ${JAVA_OPTS} -Djava.endorsed.dirs=${HOME_LOC}/tomcat6/endorsed
> -Dcatalina.base=${HOME_LOC}/tomcat6
> -Dcatalina.home=${HOME_LOC}/tomcat6
> -Djava.io.tmpdir=${HOME_LOC}/tomcat6/temp -classpath ${CLASSPATH}
> org.apache.catalina.startup.Bootstrap $@ >> ${TOMCAT_LOG} 2>&1 &
> 
> ...
> 
> Hope it will help


-- 
Projekt «Robot Team Challenge»: Wir fördern den Nachwuchs
www.informatica08.ch/robot

Marc Gassmann | marc.gassmann@netcetera.ch
phone +41-44-247 79 84 | fax +41-44-247 70 75
Netcetera AG | 8040 Zürich | Switzerland | http://netcetera.ch

Re: too many open files with 1.0.2

Posted by Henri Gomez <he...@gmail.com>.
> I use derby-10.1.3.1.jar and still have the same issue.
>
> does anybody knows an other solution?
>
> and where can I extend the open files?
>
> cheers marc

On linux, you should use ulimit :

example on the archiva startup script :

ulimit -n 2048

java ${JAVA_OPTS} -Djava.endorsed.dirs=${HOME_LOC}/tomcat6/endorsed
-Dcatalina.base=${HOME_LOC}/tomcat6
-Dcatalina.home=${HOME_LOC}/tomcat6
-Djava.io.tmpdir=${HOME_LOC}/tomcat6/temp -classpath ${CLASSPATH}
org.apache.catalina.startup.Bootstrap $@ >> ${TOMCAT_LOG} 2>&1 &

...

Hope it will help

Re: too many open files with 1.0.2

Posted by marc gassmann <mg...@netcetera.ch>.
hi

I use derby-10.1.3.1.jar and still have the same issue.

does anybody knows an other solution?

and where can I extend the open files?

cheers marc




Jason Chaffee wrote:
> 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:henri.gomez@gmail.com] 
> 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 <ja...@tvworks.com>:
>> 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?
>>
>>


Fwd: too many open files with 1.0.2

Posted by Arnaud HERITIER <ah...@gmail.com>.
Perhaps the ML doesn't allow to attach binaries :-(

---------- Forwarded message ----------
From: Arnaud HERITIER <ah...@gmail.com>
Date: Thu, Jun 5, 2008 at 5:51 PM
Subject: Re: too many open files with 1.0.2
To: users@archiva.apache.org


We have the same issue but we are using mysql
archiva creates a lot of file descriptors to proxify ressources, cleanup
repositories, deliver artifacts, ....
We changed the number of maximum open files from 1024 to 2048 and it works
fine now.
As you can see in the attached image we were over 2048 only one time this
week.

arnaud


On Thu, Jun 5, 2008 at 4:47 PM, Henri Gomez <he...@gmail.com> wrote:

> Did you tried with 10.4.1.3 or 10.3.3.0 ?
>
> I switched to 10.4 (10.4.1000003.648739) but still got these errors.
>
> I take a look at the opened inodes on my Linux box (with lsof).
>
> About 100 open connections to database/seg0/cxxx.dat files
>
> I have to restart my tomcat about 2 times in the last week, and I'm
> not very confortable with the current settings
>

Re: too many open files with 1.0.2

Posted by Henri Gomez <he...@gmail.com>.
No image here ;(

2008/6/5 Arnaud HERITIER <ah...@gmail.com>:
> We have the same issue but we are using mysql
> archiva creates a lot of file descriptors to proxify ressources, cleanup
> repositories, deliver artifacts, ....
> We changed the number of maximum open files from 1024 to 2048 and it works
> fine now.
> As you can see in the attached image we were over 2048 only one time this
> week.
>
> arnaud
>
> On Thu, Jun 5, 2008 at 4:47 PM, Henri Gomez <he...@gmail.com> wrote:
>>
>> Did you tried with 10.4.1.3 or 10.3.3.0 ?
>>
>> I switched to 10.4 (10.4.1000003.648739) but still got these errors.
>>
>> I take a look at the opened inodes on my Linux box (with lsof).
>>
>> About 100 open connections to database/seg0/cxxx.dat files
>>
>> I have to restart my tomcat about 2 times in the last week, and I'm
>> not very confortable with the current settings
>
>

Re: too many open files with 1.0.2

Posted by Arnaud HERITIER <ah...@gmail.com>.
We have the same issue but we are using mysql
archiva creates a lot of file descriptors to proxify ressources, cleanup
repositories, deliver artifacts, ....
We changed the number of maximum open files from 1024 to 2048 and it works
fine now.
As you can see in the attached image we were over 2048 only one time this
week.

arnaud

On Thu, Jun 5, 2008 at 4:47 PM, Henri Gomez <he...@gmail.com> wrote:

> Did you tried with 10.4.1.3 or 10.3.3.0 ?
>
> I switched to 10.4 (10.4.1000003.648739) but still got these errors.
>
> I take a look at the opened inodes on my Linux box (with lsof).
>
> About 100 open connections to database/seg0/cxxx.dat files
>
> I have to restart my tomcat about 2 times in the last week, and I'm
> not very confortable with the current settings
>

Re: too many open files with 1.0.2

Posted by Henri Gomez <he...@gmail.com>.
Did you tried with 10.4.1.3 or 10.3.3.0 ?

I switched to 10.4 (10.4.1000003.648739) but still got these errors.

I take a look at the opened inodes on my Linux box (with lsof).

About 100 open connections to database/seg0/cxxx.dat files

I have to restart my tomcat about 2 times in the last week, and I'm
not very confortable with the current settings

RE: too many open files with 1.0.2

Posted by Jason Chaffee <ja...@tvworks.com>.
Yes, I switched from 10.3.2.1 back to 10.1.3.1 and the problem went
away.  This suggests a resource leak with the latest derby.

-----Original Message-----
From: Henri Gomez [mailto:henri.gomez@gmail.com] 
Sent: Sunday, April 13, 2008 10:55 AM
To: archiva-users@maven.apache.org
Subject: Re: too many open files with 1.0.2

You goes back from 10.3.2.1 (latest) to 10.1.3.1 (Jul 2006) ?

2008/4/13, Jason Chaffee <ja...@tvworks.com>:
> 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:henri.gomez@gmail.com]
>  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 <ja...@tvworks.com>:
>  > 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?
>  >
>  >
>

Re: too many open files with 1.0.2

Posted by Henri Gomez <he...@gmail.com>.
You goes back from 10.3.2.1 (latest) to 10.1.3.1 (Jul 2006) ?

2008/4/13, Jason Chaffee <ja...@tvworks.com>:
> 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:henri.gomez@gmail.com]
>  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 <ja...@tvworks.com>:
>  > 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?
>  >
>  >
>

RE: too many open files with 1.0.2

Posted by Jason Chaffee <ja...@tvworks.com>.
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:henri.gomez@gmail.com] 
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 <ja...@tvworks.com>:
> 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?
>
>

Re: too many open files with 1.0.2

Posted by Henri Gomez <he...@gmail.com>.
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 <ja...@tvworks.com>:
> 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?
>
>