Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of donzymeth@gmail.com
 designates 209.85.210.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type;
        b=j5/msPa+0Q9K+EUd1GyRExwtqXtpHfWC9q4eZQfpJBR9mqocNYIJ2VtCHrqyIEwKaK
         L3rdvKuG5IU61xvyTrrllBVspvKAKfkXQDwKog2SyA2kJIQrtFHveCSR5zqNN6aVqJJ+
         00JZphe93l+98YNg2c0/F74yNwmpVmv9zOl4E=
Message-ID: <4D2479AA.2000400@gmail.com>
Date: Wed, 05 Jan 2011 22:01:14 +0800
From: Don Santillan <donzymeth@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: users@activemq.apache.org
Subject: Too many open files
References: <1294218478147-3175017.post@n4.nabble.com>
 <AANLkTinrmA=-w7Z-kO364Tupi6cw3GJ+CSHgHXyjMbTQ@mail.gmail.com>
 <7BB5B502F2DB6D4CAFEDAFDD8602A2BD1E4DA4D53C@P3ES.pcubed.jhb>
In-Reply-To: <7BB5B502F2DB6D4CAFEDAFDD8602A2BD1E4DA4D53C@P3ES.pcubed.jhb>
Content-Type: multipart/alternative;
 boundary="------------040101000502060502040107"

--------------040101000502060502040107
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

I have an embedded activemq in my webapp and it is deployed in a jetty 
server. I believe that our server OS's file descriptor limit has enough 
value.

After a few days, the application crashed with the following error:

2011-01-05 00:34:40.000:WARN::EXCEPTION 
java.io.IOException: Too many open files        
	at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
        at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:145)
        at org.eclipse.jetty.server.nio.SelectChannelConnector$1.acceptChannel(SelectChannelConnector.java:74)        
	at org.eclipse.jetty.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:650)
        at org.eclipse.jetty.io.nio.SelectorManager.doSelect(SelectorManager.java:195)
        at org.eclipse.jetty.server.nio.SelectChannelConnector.accept(SelectChannelConnector.java:134)
        at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:850)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436)
        at java.lang.Thread.run(Thread.java:6


Is there a possibility that I have configured my activemq or persistence 
wrongly which caused this? Here's my activemq.xml:
<beans xmlns="http://www.springframework.org/schema/beans"
    xmlns:amq="http://activemq.apache.org/schema/core" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.springframework.org/schema/beans 
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
  http://activemq.apache.org/schema/core 
http://activemq.apache.org/schema/core/activemq-core.xsd">

    <broker xmlns="http://activemq.apache.org/schema/core"
        brokerName="devbroker" persistent="true"
        destroyApplicationContextOnStop="true"
        dataDirectory="/tmp/dev">
       
        <transportConnectors>
            <transportConnector name="openwire"
                uri="vm://devBroker" />
        </transportConnectors>

        <plugins>
            <statisticsBrokerPlugin />
        </plugins>

    </broker>

</beans>


I googled this and saw some posts telling this maybe caused by an 
improper setting on memory limit. I also saw some threads that says use 
kaha db for better persistence. How am I able to address both of this? 
Can I configure both using the activemq.xml alone? What are the 
appropriate values for an application that processes large amount of 
messages.

Can anyone point me to a good activemq.xml configuration that is good 
for production environment?


Thanks!
-don

--------------040101000502060502040107--