Stomp connections doesn't seem to be released cleanly (Too many open files 
error)
---------------------------------------------------------------------------------

                 Key: AMQ-1873
                 URL: https://issues.apache.org/activemq/browse/AMQ-1873
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.1.0
         Environment: Linux RHEL 4
java version "1.5.0_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_15-b04)
Java HotSpot(TM) Server VM (build 1.5.0_15-b04, mixed mode)

            Reporter: Julien Devemy
         Attachments: activemq.xml

I'm actually testing ActiveMQ with a python stomp Client (stomp.py 
http://www.briggs.net.nz/log/projects/stomppy/).

I'm trying to load the broker with ~200 producers (on ~200 hosts) feeding one 
TOPIC for only one consumer.

Everything is working almost fine until the client connection fails.

The ActiveMQ log displays :
...
2008-07-30 09:28:43,665 [localhost:61613] ERROR TransportConnector             
- Could not accept connection : Too many open files
2008-07-30 09:28:43,665 [localhost:61613] DEBUG TransportConnector             
- Reason: Too many open files
java.net.SocketException: Too many open files
        at java.net.PlainSocketImpl.socketAccept(Native Method)
        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384)
        at java.net.ServerSocket.implAccept(ServerSocket.java:450)
        at java.net.ServerSocket.accept(ServerSocket.java:421)
        at 
org.apache.activemq.transport.tcp.TcpTransportServer.run(TcpTransportServer.java:221)
        at java.lang.Thread.run(Thread.java:595)

When I look at the open files (or connections) (with lsof) I see 65446 lines 
like :

java    26765 root *066u  sock        0,4          7534034 can't identify 
protocol

This seems to indicate that ActiveMQ doesn't totally released the UNIX socket

I'm attaching the activemq.xml conf file.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to