Out of Memory on 5.3

We're using only persistent messages and heap size is set to 2GB yet we hit the memoryUsage limit quite quickly (system usage config below). This is followed by "java.lang.OutOfMemoryError: unable to create new native thread" as the process quickly reaches the 2GB of heap we gave it. How are we g

How to limit queue by number of messages

I'm looking for a way to keep queue sizes down to a specific number. For example if a queue gets to 10 messages I would like older message to start disappearing. I'm aware there are some "Pending Message Limit Strategy" options but these only apply to pending messages on a topic per consumer

sendFailIfNoSpace and stomp

Is there any way to get the fail notification when the store is full with the stomp client? Right now, with sendFailIfNoSpace set to true, when I send to a broker that is full it just looks like a successful send from stomp's point of view - which is obviously the opposite of what I would like to

ajax subscriber won't consume messages

I'm having trouble getting an ajax subscriber working. I'm able to send message just fine via the ajax servlet but when I subscribe all I get back is even when there are messages queued. I subscribe doing the following(testqueue has messages in it): var callback = function(message) { alert

Failed to register subscription

I'm not really sure what's causing this. The server that gets into this state is networked with one other. The other server is consuming messages that are produced on the first server(the one that breaks down). It's not hitting any max store or memory limits but it is blocking on send now. Her

Strange behaviour when StoreLimit is reached

I'm trying to prove the stability of AMQ when queues are being written too but not consumed (or rather that we can recover after such a scenario). So far it's not doing so well. I'm using stomp. Issue: Send messages until the StoreLimit is reached... send now blocks. Consume all the messages we

multicast 'timeToLive' doesn't seem to work

This is how I'm setting timeToLive: When I check on the packets with Wireshark the TTL is still 1. That setting does seem to be doing _something_ since if I set it too high it won't even start. Anyone ever used this successfully? Maybe it just doesn't do what I think it should (Like so many

Re: Embedded Brokers discovery

Were you ever able to get this to work? I really need to get discovery working but since AMQ leaves off the protocol and domain I can't use real Bonjour or mdns libraries. Using java isn't an option since it has to be perl. kitplummer wrote: > > > James (and everyone else), > > Ok, I feel s

can't get simple Network of Brokers to work

I've followed the example in http://activemq.apache.org/networks-of-brokers.html for multicast discovery. I have two brokers set up that way (let's call them A and B). I'm sending messages to /queue/foo on broker A. I have something subscribing to /queue/foo on broker B but it doesn't get the m

Rendezvous Discovery broadcasting on non-standard name

So I realise that AMQ broadcasts on _default.ActiveMQ-4. and the java libraries discover it just fine. However, to any other Bonjour client this will be invisible since it's missing the protocol and domain (ie. _default.ActiveMQ-4._tcp.local). Is there any way to adjust it so it's a 'real' Bonj