Re: Broker refusing to send messages to only certain queues?

2015-04-16 Thread Tim Bain
If that was happening you'd see the DestinationViewMBean's ExpiredCount increasing in the JMX counters, but only if the expiration was happening on the broker; as far as I could tell, there's no stat that captures when messages expire while they're in the client's prefetch buffer. (But that's just

Re: selectors don't browse?

2015-04-16 Thread Tim Bain
I think the behavior you're seeing has to do with message cursors ( http://activemq.apache.org/message-cursors.html) than with missing acks. Basically once the cursor is full of messages that don't match your selectors, no new messages will come out of the message store into the cursor until one of

JMX variables for queue creation timestamp, last enqueue time, etc.

2015-04-16 Thread Kevin Burton
It would be handy to have timestamps for various things on queues. Right now if a queue is created, it’s unclear how long it’s been in existence for.. Would also be nice to see stats for the last time the a message was produced, consumed, etc. -- Founder/CEO Spinn3r.com Location: *San Francisc

Monitoring producer flow control.

2015-04-16 Thread Kevin Burton
I’m looking at implementing producer flow control so that I don’t fill up the queues on my broker. It doesn’t look like there’s any way I can see that a client is blocking, waiting for resources to be released. Maybe one strategy could be to put a stopwatch around each send() and then I can see t

selectors don't browse?

2015-04-16 Thread Jon Gorrono
I am trying to do some testing an limit the output from a queue that has about 4500 messages in it. Each message contains between 300 and 500 documents attached that i process individually. But I am trying to test only specific message types and not see the others so I restart the client each cycle

Re: Broker refusing to send messages to only certain queues?

2015-04-16 Thread Kevin Burton
actually, I not’ think this could be the issue. The if I was getting redeliveries, and NO work was being done, I’d see messages in the dead letter queue - which I don’t see. On Thu, Apr 16, 2015 at 9:55 AM, Kevin Burton wrote: > Ah.. That’s an interesting hypothesis. So in this situation th

Makefile for performance testing

2015-04-16 Thread Arun Babu Neelicattu
Hey; thought this might be useful for some to get started with http://activemq.apache.org/activemq-performance-module-users-manual.html I have written a Makefile that does what is required to setup and run the default test. https://gist.github.com/abn/9cbffdfd1f5cb7f7c3e4 To execute a test one j

Too many open files with thousands connections in Solaris

2015-04-16 Thread hicyo
Hi, I am facing a big problem in our application. It uses a cluster of 3 brokers configured with a network connector. We have a huge number of clients around 1 connected to theses brokers. Each client opens 2 connections to send and receive messages. We use a powerful machines running on Solari

Re: Broker refusing to send messages to only certain queues?

2015-04-16 Thread Kevin Burton
Ah.. That’s an interesting hypothesis. So in this situation the client would just never even see the message and would just keep being rejected. Is there any way to test this hypothesis.? Any stats? I’ll look at JMX but I didn’t see any that might stand out. On Thu, Apr 16, 2015 at 5:51 AM, Tim

Re: AMQ console - Enque/Deque/Dispactched - Mystified!

2015-04-16 Thread mattmadhavan
Hi artnassef, It does not matter how many large volumes of messages I have, I have tried anywhere from 10 thousand, 15 thousand to 32 thousand. It stops dispensing right towards the end. I have to restart both the brokers and and the consumers to make the job complete. Please find attached my scr

http://localhost:8161/admin/ gives Exception occurred while processing

2015-04-16 Thread Mehran Khizar
ActiveMQ 5.7.0 OS : Oracle Solaris 10 JDK 1.7.0 J2EE ActiveMQ process was killed. When Tried to start ActiveMQ using following . activemq start & Queues started to Work. However, "http://localhost:8161/admin/"; started to give Error! Exception occurred while processing this request, check

Re: Broker refusing to send messages to only certain queues?

2015-04-16 Thread Tim Bain
Is there any chance the messages are old enough that they're expired by the time the client gets to them? Maybe the broker is running slowly enough that it doesn't try to dispatch each message until after it's expired, resulting in no messages getting *consumed* rather than no messages getting dis