Broker stops accepting messages when policy queue memoryLimit is reached

Broker stops accepting messages once the queue memoryLimit is hit. Version: 5.2.0 How to reproduce: 1. Start ActiveMQ with default configuration. 2. Queue messages until it stops accepting messages. (~5000 depending on message size.) The broker will continue accepting messages past the lim

RE: Using Perl to check ActiveMQ with Net::Stomp.

can_read() is actually part of IO::Select, and not at all related to the broker. Net::Stomp's can_read function just passes through to the internal IO::Select->can_read() function on the socket to the client, so if you want to explore what its actually doing, look to that module instead of Net::

activemq-admin failing on snapshot

This is bizarre. I have 3 servers running 5.2.0-SNAPSHOT from today. Their configuration is identical other than the broker name and broker URLs in the activemq.xml file. On two on them activemq-admin works flawlessly, on the 3rd, it sits there for 5+ minutes before returning a connection timed

RE: kr-store/index-queue-data grows indefinitely?

gt; On 5 Aug 2008, at 01:06, Dylan Vanderhoof wrote: > > > Running 5.1.0. > > > > We have a single queue running around 1M messages per day (and some > > other much smaller ones). We're using persistance simply so if a > > consumer fails, we can restart Acti

kr-store/index-queue-data grows indefinitely?

Running 5.1.0. We have a single queue running around 1M messages per day (and some other much smaller ones). We're using persistance simply so if a consumer fails, we can restart ActiveMQ without losing the queued messages. However, nothing is durable. Once the message is processed, its gone

Net::Stomp and failover/network of brokers transport?

I know several people over time have said they're working on HA extensions to Net::Stomp. Has anybody actually made any progress on this with code they're willing to share? Thanks, Dylan

Number of consumers high on 5.1 RC

I have a couple ad-hoc queues, each with 2 consumers running. For whatever reason, the number of consumers on one queue is 17, the other 5. These are all Stomp clients. There have been a few unclean kills of the consumers, but my understanding is that the consumers would be flushed on the nex

RE: Heap error w/ kaha (I think?)

Are the RCs considered production stable(ish?) > -Original Message- > From: Rob Davies [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 23, 2008 12:24 PM > To: users@activemq.apache.org > Subject: Re: Heap error w/ kaha (I think?) > > > > On 23 Apr 2008, at 20

Heap error w/ kaha (I think?)

I'm getting the following error periodically with my broker (5.0.0) Using Kaha, although I'm not sure that's the issue. 2008-04-23 18:46:27,415 [ce Adaptor Task] WARN AMQMessageStore - Message could not be added to long term store: Java heap space java.lang.OutOfMemoryError: Java

RE: STOMP and Failover transport

I believe Ramit Arora and Simon Wistow from this list are also working separatly on failover transport for Net::Stomp and have access to PAUSE for uploading to CPAN. It might be worth pinging them to avoid duplication of effort and get a One True Module(tm) out for the perl community. (Speakin

RE: Implementing failover for Net::Stomp

If you get this worked out, would you be willing to release your Net::Stomp hacks? I'm desperatly needing HA for my perl publishers (and subscribers for that matter), but I don't have the hours to do it in house at the moment. -D > -Original Message- > From: Ramit Arora [mailto:[EMAIL

RE: Perl/Net::Stomp and multiple brokers

Nobody's done this? I could've sworn I saw at least one person mention that'd added failover support to Net::Stomp, but I can't find that email right now. -D > -Original Message- > From: Dylan Vanderhoof [mailto:[EMAIL PROTECTED] > Sent: Monday, March 0

Perl/Net::Stomp and multiple brokers

Does anybody have a hacked Net::Stomp they'd be willing to share for contacting multiple brokers? Either a network, or failover, I'm not terribly picky about which at the moment. -Dylan