You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by DavidLevy <dv...@gmail.com> on 2009/10/14 12:46:42 UTC
"too many open files" error with 5.3 and Stomp
Hi
I had the issue with 5.2 and now that I installed 5.3 last night, it still
the same, or even worse.
It basically looks like this issue :
http://issues.apache.org/activemq/browse/AMQ-1873
After a short time (1 hour or so) the broker is filled with errors like 'too
many open files' and I have to restart activemq.
I don't believe it's a performance issue because
- the host server is strong
- there are less than 10 queues
- there are less than 10000 messages
I assume it has to do also with Stomp connections not being released.
I am using both PHP and Python clients. I believe the issue is related to
PHP clients that may be more error prone if the Apache threads die
improperly ...
I ll attach my current config file.
Any help is welcome !
Thanks :)
http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
--
View this message in context: http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: "too many open files" error with 5.3 and Stomp
Posted by "alex.hollerith" <al...@hollerith.net>.
Hi,
Dejan Bosanac wrote:
>
> ok, can you at least provide more data on:
>
> - how many producers/consumers are you using
> - are you opening a new connection for every message send/receive
>
I saw the same thing happening in our environment which consists of just one
producer at the moment.
We are using stomp via Perl and I think we are opening and closing the
connection every time we post, but am not sure.
Logfile attached.
A. http://www.nabble.com/file/p25995732/amq_log.txt amq_log.txt
--
View this message in context: http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25995732.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: "too many open files" error with 5.3 and Stomp
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi Alex,
see info in this post
http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-to25888831.html#a26129409
basically, try turning off the producer flow control and don't use stomp+nio
at the moment
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Fri, Oct 30, 2009 at 1:40 PM, alex.hollerith <al...@hollerith.net> wrote:
>
> config:
> <policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
>
> setup:
> 1 perl stomp producer producing into a queue,
> connecting and disconnecting on every post,
> rather low frequency of posts (0.5/minute)
> 0 consumers
>
> behaviour:
> works OK until around 68 messages are in the queue (surely depends on the
> size of the messages)
>
> after that you get this in the log:
> 2009-10-29 20:32:05,189 | INFO | Usage Manager memory limit reached on
> queue://test.soccerfeeds.queue. Producers will be throttled to the rate at
> which messages are removed <...>
>
> And while the activemq service is in that "throttling producers" state you
> will see CLOSE_WAIT sockets building up:
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:41519
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:36141
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:45840
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43793
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:40212
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44060
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43776
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44032
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43781
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:40200
> CLOSE_WAIT
> tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44045
> CLOSE_WAIT
>
> You can watch the numbers grow with:
> watch --interval=5 'netstat -an |grep tcp |grep 61613 | grep CLOSE_WAIT |wc
> -l'
>
> Every post increases the number of CLOSE_WAIT sockets by 1. And the sockets
> will not go away, the number seems to be steadily growing, we watched it
> for
> around 17 hours.
>
> Now just consume one single message (we did this via the admin
> webinterface)
> and the number of sockets in CLOSE_WAIT drops to 0 instantly.
>
> [root@bladedist01 activemq]# netstat -an |grep tcp |grep 61613
> tcp 0 0 :::61613 :::*
> LISTEN
>
> Our theory is that activemq does somehow manage to build up sockets in
> CLOSE_WAIT state while it is in "throttling producers" mode on a given
> queue until, eventually, the system runs out of resources (file descriptors
> in this case).
> --
> View this message in context:
> http://old.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p26129409.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: "too many open files" error with 5.3 and Stomp
Posted by "alex.hollerith" <al...@hollerith.net>.
config:
<policyEntry queue=">" producerFlowControl="true" memoryLimit="5mb">
setup:
1 perl stomp producer producing into a queue,
connecting and disconnecting on every post,
rather low frequency of posts (0.5/minute)
0 consumers
behaviour:
works OK until around 68 messages are in the queue (surely depends on the
size of the messages)
after that you get this in the log:
2009-10-29 20:32:05,189 | INFO | Usage Manager memory limit reached on
queue://test.soccerfeeds.queue. Producers will be throttled to the rate at
which messages are removed <...>
And while the activemq service is in that "throttling producers" state you
will see CLOSE_WAIT sockets building up:
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:41519
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:36141
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:45840
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43793
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:40212
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44060
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43776
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44032
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:43781
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:40200
CLOSE_WAIT
tcp 0 0 ::ffff:10.60.1.51:61613 ::ffff:10.60.1.206:44045
CLOSE_WAIT
You can watch the numbers grow with:
watch --interval=5 'netstat -an |grep tcp |grep 61613 | grep CLOSE_WAIT |wc
-l'
Every post increases the number of CLOSE_WAIT sockets by 1. And the sockets
will not go away, the number seems to be steadily growing, we watched it for
around 17 hours.
Now just consume one single message (we did this via the admin webinterface)
and the number of sockets in CLOSE_WAIT drops to 0 instantly.
[root@bladedist01 activemq]# netstat -an |grep tcp |grep 61613
tcp 0 0 :::61613 :::*
LISTEN
Our theory is that activemq does somehow manage to build up sockets in
CLOSE_WAIT state while it is in "throttling producers" mode on a given
queue until, eventually, the system runs out of resources (file descriptors
in this case).
--
View this message in context: http://old.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p26129409.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: "too many open files" error with 5.3 and Stomp
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi guys,
did some initial testing on this (will commit my test soon, so we can have
it for further testings).
I wasn't able to reproduce the exact error you notice, but was getting a
"unable to create new native thread" from a stomp broker under load. The
test simulates the behavior where producer/consumer open/close conenctions
on each operation.
What I noticed is a lot of sockets in TIME_WAIT (and some in CLOSE_WAIT)
state. After some digging I found that some configuration settings can
improve things
1. Use closeAsync transport option
<transportConnector name="stomp" uri="stomp://
0.0.0.0:61612?transport.closeAsync=false"/>
2. Remove small memoryLimit from destinationPolicy
<destinationPolicy>
<policyMap>
<policyEntries>
<policyEntry topic=">" producerFlowControl="true">
<pendingSubscriberPolicy>
<vmCursor />
</pendingSubscriberPolicy>
</policyEntry>
<policyEntry queue=">" producerFlowControl="true">
<pendingQueuePolicy>
<vmQueueCursor/>
</pendingQueuePolicy>
</policyEntry>
</policyEntries>
</policyMap>
</destinationPolicy>
Since all messages are sent through new connections they are all considered
to be new producers to the broker, and once the flow control is hit,
producers are grouping and probably taking all available connections. You
might try turning off producer flow control completely to see if it works
for you. Found this tip in http://issues.apache.org/activemq/browse/AMQ-1739
3. You can also try some of the scaling techniques, described here
http://activemq.apache.org/how-do-i-configure-10s-of-1000s-of-queues-in-a-single-broker-.html
I turned off dedicated task runner and gave the broker some more memory,
like this
ACTIVEMQ_OPTS="-Xmx1024M -Dorg.apache.activemq.UseDedicatedTaskRunner=false
-Djava.util.logging.config.file=logging.properties"
With all these options, the load test over the standard stomp connector ran
well for quite some time (I still observed some problems with stomp+nio
protocol).
Since there are a few issues regarding stomp and connections
http://issues.apache.org/activemq/browse/AMQ-1739
http://issues.apache.org/activemq/browse/AMQ-1873
https://issues.apache.org/activemq/browse/AMQ-2440
will take more look into it and perhaps when we have it sorted, we should
create activemq-stomp.xml tuned configuration for Stomp usage.
In the meantime, it would be great if you'd test this configuration in your
environment and report if there were any improvements (sample config is
attached)
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Oct 22, 2009 at 12:11 PM, DavidLevy <dv...@gmail.com> wrote:
>
> Hi
>
> - it's web, so I can't really tell ...
> I would say 50-100 STOMP PHP producers/consumers
> + 2 REST python producers/consumers
> In 5.3 i was using stomp at first, and then stomp+nio but I think both had
> the issue.
>
> - most of them yes, because it's new PHP scripts
>
> PS : the server is a 64bit server. It might be a problem ?
>
>
>
> Dejan Bosanac wrote:
> >
> > Hi David,
> >
> > ok, can you at least provide more data on:
> >
> > - how many producers/consumers are you using
> > - are you opening a new connection for every message send/receive
> >
> > Also, are you using regular stomp or stomp+nio transports?
> >
> > I'm working on creating a java test that can simulate stomp load
> > environment
> > with many producers/consumers opening connections.
> >
> > Cheers
> > --
> > Dejan Bosanac - http://twitter.com/dejanb
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
> >
> > On Wed, Oct 21, 2009 at 4:03 PM, DavidLevy <dv...@gmail.com> wrote:
> >
> >>
> >> Thanks Dejan,
> >>
> >> This happen in my production environment which is made of a dozen
> server.
> >> I don't believe it would be easy to reproduce by myself in a smaller
> >> environment.
> >>
> >> I noticed that it works better with v5.2. With 5.3, it's not stable for
> >> more
> >> than a few hours. 5.2 can last a few days before it crashes.
> >>
> >> I was also thinking about using REST calls instead of STOMP for some PHP
> >> scripts ... It should help if the STOMP leak is my issue for real ...
> >>
> >>
> >>
> >>
> >>
> >> Dejan Bosanac wrote:
> >> >
> >> > I plan to look at these connection closing issues with stomp in coming
> >> > days.
> >> > Any chance you can create a reproducible test case (in any language)?
> >> >
> >> > Cheers
> >> > --
> >> > Dejan Bosanac - http://twitter.com/dejanb
> >> >
> >> > Open Source Integration - http://fusesource.com/
> >> > ActiveMQ in Action - http://www.manning.com/snyder/
> >> > Blog - http://www.nighttale.net
> >> >
> >> >
> >> > On Wed, Oct 14, 2009 at 12:46 PM, DavidLevy <dv...@gmail.com>
> >> wrote:
> >> >
> >> >>
> >> >> Hi
> >> >>
> >> >> I had the issue with 5.2 and now that I installed 5.3 last night, it
> >> >> still
> >> >> the same, or even worse.
> >> >> It basically looks like this issue :
> >> >> http://issues.apache.org/activemq/browse/AMQ-1873
> >> >>
> >> >> After a short time (1 hour or so) the broker is filled with errors
> >> like
> >> >> 'too
> >> >> many open files' and I have to restart activemq.
> >> >>
> >> >>
> >> >> I don't believe it's a performance issue because
> >> >> - the host server is strong
> >> >> - there are less than 10 queues
> >> >> - there are less than 10000 messages
> >> >>
> >> >> I assume it has to do also with Stomp connections not being released.
> >> >> I am using both PHP and Python clients. I believe the issue is
> related
> >> to
> >> >> PHP clients that may be more error prone if the Apache threads die
> >> >> improperly ...
> >> >>
> >> >> I ll attach my current config file.
> >> >>
> >> >> Any help is welcome !
> >> >>
> >> >> Thanks :)
> >> >>
> >> >> http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
> >> >> --
> >> >> View this message in context:
> >> >>
> >>
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
> >> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >
> >> >
> >> > -----
> >> > Dejan Bosanac
> >> >
> >> > Open Source Integration - http://fusesource.com/
> >> > ActiveMQ in Action - http://www.manning.com/snyder/
> >> > Blog - http://www.nighttale.net
> >> >
> >>
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25993154.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > -----
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
>
> --
> View this message in context:
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p26007460.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: "too many open files" error with 5.3 and Stomp
Posted by DavidLevy <dv...@gmail.com>.
Hi
- it's web, so I can't really tell ...
I would say 50-100 STOMP PHP producers/consumers
+ 2 REST python producers/consumers
In 5.3 i was using stomp at first, and then stomp+nio but I think both had
the issue.
- most of them yes, because it's new PHP scripts
PS : the server is a 64bit server. It might be a problem ?
Dejan Bosanac wrote:
>
> Hi David,
>
> ok, can you at least provide more data on:
>
> - how many producers/consumers are you using
> - are you opening a new connection for every message send/receive
>
> Also, are you using regular stomp or stomp+nio transports?
>
> I'm working on creating a java test that can simulate stomp load
> environment
> with many producers/consumers opening connections.
>
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Wed, Oct 21, 2009 at 4:03 PM, DavidLevy <dv...@gmail.com> wrote:
>
>>
>> Thanks Dejan,
>>
>> This happen in my production environment which is made of a dozen server.
>> I don't believe it would be easy to reproduce by myself in a smaller
>> environment.
>>
>> I noticed that it works better with v5.2. With 5.3, it's not stable for
>> more
>> than a few hours. 5.2 can last a few days before it crashes.
>>
>> I was also thinking about using REST calls instead of STOMP for some PHP
>> scripts ... It should help if the STOMP leak is my issue for real ...
>>
>>
>>
>>
>>
>> Dejan Bosanac wrote:
>> >
>> > I plan to look at these connection closing issues with stomp in coming
>> > days.
>> > Any chance you can create a reproducible test case (in any language)?
>> >
>> > Cheers
>> > --
>> > Dejan Bosanac - http://twitter.com/dejanb
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>> >
>> > On Wed, Oct 14, 2009 at 12:46 PM, DavidLevy <dv...@gmail.com>
>> wrote:
>> >
>> >>
>> >> Hi
>> >>
>> >> I had the issue with 5.2 and now that I installed 5.3 last night, it
>> >> still
>> >> the same, or even worse.
>> >> It basically looks like this issue :
>> >> http://issues.apache.org/activemq/browse/AMQ-1873
>> >>
>> >> After a short time (1 hour or so) the broker is filled with errors
>> like
>> >> 'too
>> >> many open files' and I have to restart activemq.
>> >>
>> >>
>> >> I don't believe it's a performance issue because
>> >> - the host server is strong
>> >> - there are less than 10 queues
>> >> - there are less than 10000 messages
>> >>
>> >> I assume it has to do also with Stomp connections not being released.
>> >> I am using both PHP and Python clients. I believe the issue is related
>> to
>> >> PHP clients that may be more error prone if the Apache threads die
>> >> improperly ...
>> >>
>> >> I ll attach my current config file.
>> >>
>> >> Any help is welcome !
>> >>
>> >> Thanks :)
>> >>
>> >> http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
>> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > -----
>> > Dejan Bosanac
>> >
>> > Open Source Integration - http://fusesource.com/
>> > ActiveMQ in Action - http://www.manning.com/snyder/
>> > Blog - http://www.nighttale.net
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25993154.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> -----
> Dejan Bosanac
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
--
View this message in context: http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p26007460.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: "too many open files" error with 5.3 and Stomp
Posted by Dejan Bosanac <de...@nighttale.net>.
Hi David,
ok, can you at least provide more data on:
- how many producers/consumers are you using
- are you opening a new connection for every message send/receive
Also, are you using regular stomp or stomp+nio transports?
I'm working on creating a java test that can simulate stomp load environment
with many producers/consumers opening connections.
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Oct 21, 2009 at 4:03 PM, DavidLevy <dv...@gmail.com> wrote:
>
> Thanks Dejan,
>
> This happen in my production environment which is made of a dozen server.
> I don't believe it would be easy to reproduce by myself in a smaller
> environment.
>
> I noticed that it works better with v5.2. With 5.3, it's not stable for
> more
> than a few hours. 5.2 can last a few days before it crashes.
>
> I was also thinking about using REST calls instead of STOMP for some PHP
> scripts ... It should help if the STOMP leak is my issue for real ...
>
>
>
>
>
> Dejan Bosanac wrote:
> >
> > I plan to look at these connection closing issues with stomp in coming
> > days.
> > Any chance you can create a reproducible test case (in any language)?
> >
> > Cheers
> > --
> > Dejan Bosanac - http://twitter.com/dejanb
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
> >
> > On Wed, Oct 14, 2009 at 12:46 PM, DavidLevy <dv...@gmail.com> wrote:
> >
> >>
> >> Hi
> >>
> >> I had the issue with 5.2 and now that I installed 5.3 last night, it
> >> still
> >> the same, or even worse.
> >> It basically looks like this issue :
> >> http://issues.apache.org/activemq/browse/AMQ-1873
> >>
> >> After a short time (1 hour or so) the broker is filled with errors like
> >> 'too
> >> many open files' and I have to restart activemq.
> >>
> >>
> >> I don't believe it's a performance issue because
> >> - the host server is strong
> >> - there are less than 10 queues
> >> - there are less than 10000 messages
> >>
> >> I assume it has to do also with Stomp connections not being released.
> >> I am using both PHP and Python clients. I believe the issue is related
> to
> >> PHP clients that may be more error prone if the Apache threads die
> >> improperly ...
> >>
> >> I ll attach my current config file.
> >>
> >> Any help is welcome !
> >>
> >> Thanks :)
> >>
> >> http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
> >> --
> >> View this message in context:
> >>
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
> >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >>
> >>
> >
> >
> > -----
> > Dejan Bosanac
> >
> > Open Source Integration - http://fusesource.com/
> > ActiveMQ in Action - http://www.manning.com/snyder/
> > Blog - http://www.nighttale.net
> >
>
> --
> View this message in context:
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25993154.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
Re: "too many open files" error with 5.3 and Stomp
Posted by DavidLevy <dv...@gmail.com>.
Thanks Dejan,
This happen in my production environment which is made of a dozen server.
I don't believe it would be easy to reproduce by myself in a smaller
environment.
I noticed that it works better with v5.2. With 5.3, it's not stable for more
than a few hours. 5.2 can last a few days before it crashes.
I was also thinking about using REST calls instead of STOMP for some PHP
scripts ... It should help if the STOMP leak is my issue for real ...
Dejan Bosanac wrote:
>
> I plan to look at these connection closing issues with stomp in coming
> days.
> Any chance you can create a reproducible test case (in any language)?
>
> Cheers
> --
> Dejan Bosanac - http://twitter.com/dejanb
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
>
> On Wed, Oct 14, 2009 at 12:46 PM, DavidLevy <dv...@gmail.com> wrote:
>
>>
>> Hi
>>
>> I had the issue with 5.2 and now that I installed 5.3 last night, it
>> still
>> the same, or even worse.
>> It basically looks like this issue :
>> http://issues.apache.org/activemq/browse/AMQ-1873
>>
>> After a short time (1 hour or so) the broker is filled with errors like
>> 'too
>> many open files' and I have to restart activemq.
>>
>>
>> I don't believe it's a performance issue because
>> - the host server is strong
>> - there are less than 10 queues
>> - there are less than 10000 messages
>>
>> I assume it has to do also with Stomp connections not being released.
>> I am using both PHP and Python clients. I believe the issue is related to
>> PHP clients that may be more error prone if the Apache threads die
>> improperly ...
>>
>> I ll attach my current config file.
>>
>> Any help is welcome !
>>
>> Thanks :)
>>
>> http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
>> --
>> View this message in context:
>> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>
>
> -----
> Dejan Bosanac
>
> Open Source Integration - http://fusesource.com/
> ActiveMQ in Action - http://www.manning.com/snyder/
> Blog - http://www.nighttale.net
>
--
View this message in context: http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25993154.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: "too many open files" error with 5.3 and Stomp
Posted by Dejan Bosanac <de...@nighttale.net>.
I plan to look at these connection closing issues with stomp in coming days.
Any chance you can create a reproducible test case (in any language)?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Wed, Oct 14, 2009 at 12:46 PM, DavidLevy <dv...@gmail.com> wrote:
>
> Hi
>
> I had the issue with 5.2 and now that I installed 5.3 last night, it still
> the same, or even worse.
> It basically looks like this issue :
> http://issues.apache.org/activemq/browse/AMQ-1873
>
> After a short time (1 hour or so) the broker is filled with errors like
> 'too
> many open files' and I have to restart activemq.
>
>
> I don't believe it's a performance issue because
> - the host server is strong
> - there are less than 10 queues
> - there are less than 10000 messages
>
> I assume it has to do also with Stomp connections not being released.
> I am using both PHP and Python clients. I believe the issue is related to
> PHP clients that may be more error prone if the Apache threads die
> improperly ...
>
> I ll attach my current config file.
>
> Any help is welcome !
>
> Thanks :)
>
> http://www.nabble.com/file/p25888831/activemq.xml activemq.xml
> --
> View this message in context:
> http://www.nabble.com/%22too-many-open-files%22-error-with-5.3-and-Stomp-tp25888831p25888831.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>