ning.com/snyder/
Blog - http://www.nighttale.net
On Tue, Oct 27, 2009 at 1:07 AM, Mitch Granger
wrote:
Update: We've [nearly] proven that this only happens with AMQ running on
openVZ. What exactly is causing it, we're still not sure. After
memoryUsage is met, the number of threads s
ed investigating this more and
hopefully I'll have some more findings in the near future.
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 Tue, Oct
What sort of instability are you seeing? If there were some specific
areas than people could comment on how they've addressed them.
Also setting that gave stability for one person may not work for
everyone. Some good things to know would be:
- what hardware are you using? or virtualization
of
messages on their queues should be well served by changing the cursor.
Mitch Granger wrote:
Config is attached. We have also tried the activemq-scalability.xml
with the only change being adding a stomp connector.
Once we hit the memoryUsage limit we can [sometimes] connect new
consumers bu
Config is attached. We have also tried the activemq-scalability.xml
with the only change being adding a stomp connector.
Once we hit the memoryUsage limit we can [sometimes] connect new
consumers but nothing comes back after we send the SUBSCRIBE frame.
I expect sending to fail when we hit t
axdepth is reached?
Could you raise an enhancement request for this feature?
2009/10/22 Mitch Granger
To be clearer, I'm looking for something like Websphere MQ's maxdepth
property for queues.
themitchy wrote:
I'm looking for a way to keep queue sizes down to a specific
To be clearer, I'm looking for something like Websphere MQ's maxdepth
property for queues.
themitchy wrote:
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
Turns out AMQ is handling this properly. It sends an error when you
request receipt on a send and the broker is full. It's Net::Stomp which
does not attempt to read in the error or the receipt.
themitchy wrote:
Is there any way to get the fail notification when the store is full with the
sto
Bruce Snyder wrote:
On Thu, Oct 1, 2009 at 11:51 AM, Mitch Granger wrote:
The 5.3 Snapshot seems to fix all my trouble. Wahoo!
What behavior do you see with 5.3 when the StoreLimit is reached?
It's more about the StoreLimit recovering when messages are consumed
again. 5.3 rec
The 5.3 Snapshot seems to fix all my trouble. Wahoo!
themitchy wrote:
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
Bruce Snyder wrote:
On Wed, Sep 23, 2009 at 5:57 PM, themitchy wrote:
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 su
Thanks! I'm all sorted out now. The real issue turned out to be that
the OpenVZ images I was working off of couldn't multicast. Having
working configs for a static list of brokers did help me identify that
though.
Thanks again!
Bruce Snyder wrote:
On Fri, Sep 4, 2009 at 5:43 PM, themitchy
I've got an out of the box ActiveMQ(5.2.0) setup that's doing about
500,000 messages per queue on 3 queues via the stomp framework.
After a while(hours/days) I get a flood of "Memory usage change. from:
99, to: 100" messages in the log and then it just loops on restarting
the transport follow
Cutting to the chase, I need to be able to discover brokers by non-java
means. Here are the details:
I have activeMQ set up to use rendezvous using the following configuration:
discoveryUri="rendezvous://test"/>
The DiscoveryAgent starts up fine and can be discovered using the
14 matches
Mail list logo
