Re: AMQ halts and crashes after few thousand reqs

anything lesser than 48g 1/2U's because now I need to play games with the collectors running out of steam at 16-18g heaps. On Feb 26, 2013, at 19:09, Darren Govoni dar...@ontrenet.com wrote: Unfortunately, getting AMQ to show production-grade scalability and reliability is a real challenge. We

Re: AMQ halts and crashes after few thousand reqs

with quadcore + 8GB RAM, is that a server grade machine that you use or your laptop? I have trouble getting anything lesser than 48g 1/2U's because now I need to play games with the collectors running out of steam at 16-18g heaps. On Feb 26, 2013, at 19:09, Darren Govoni dar...@ontrenet.com wrote

Re: AMQ halts and crashes after few thousand reqs

Unfortunately, getting AMQ to show production-grade scalability and reliability is a real challenge. We tried and failed to get it to scale or perform acceptably and were forced to write our own distributed queue on top of mongodb. The addition of AMQP is nice however. On 02/15/2013 05:44 AM,

Re: python library?

think the scaling issues still linger from the message traffic I see on the list. Your mileage may vary though. On Sat, 2012-04-07 at 16:45 +0200, Luis Cañas Díaz wrote: On 07/04/12 16:18, Darren Govoni wrote: Can you be more specific? What is not working well, and so on Yeah, sorry

Re: New to Apollo

Hi, It seems at times the shutdown button on the web console doesn't cause a shutdown. My suggestion is to add it as a command to 'apollo-broker' similar to run so it can be scripted. Also, I notice in my app, that after 17k messages or so, my consumers stop receiving messages. The

Transport failed exceptions

Hi, After some period of time, AMQ (5.5) starts rejecting connections with the below exception: 2011-08-10 11:40:56,434 | INFO | Transport failed: java.io.EOFException | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///127.0.0.1:50762 Then I can no

consumer queue acknowledge?

Hi, I want to allow consumers of a persistent queue to programmatically acknowledge messages. And after some time, if it is not acknowledge, I want the message re-delivered elsewhere. Are there examples of how to do this? Any tips appreciated. Thanks! Darren

Re: consumer queue acknowledge?

this behavior works correctly in 5.5? On 06/28/2011 02:15 PM, Johan Edstrom wrote: Yes, it depends on how you acknowledge. AUTO, Client or Individual (This is an AMQ specific) Client == On the Session. On Jun 28, 2011, at 11:43 AM, Darren Govoni wrote: Hi, I want to allow consumers of a persistent

Re: Channel was inactive for too long. sigh

Yeah, I can't detect why its happening and the maxInactivityDuration=0 doesn't work. Maybe I can set a trace to dig deeper? I'm using pyactivemq over activemq-cpp so maybe there are some version issues. Not sure. Maybe the client is busy doing work in its main thread and can't respond to the

Re: Channel was inactive for too long. sigh

Ok, I moved my connection creation into my objects runnable thread and outside its constructor and the connections stay up now. Probably something was falling out of scope or getting gc'd. silly me. On 06/22/2011 11:57 AM, Darren Govoni wrote: Yeah, I can't detect why its happening

Channel was inactive for too long. sigh

Hi, I am using 5.5.0. When running on 64bit ubuntu on EC2, I have 30 connections via pyactivemq on same host. They connect fine. get messages. Shortly later (like couple minutes) all the connections disappear with this exception in the activemq log (many of them). 2011-06-22 00:36:10,394