Re: Backlog data causes producers to slow down.

2011-09-12 Thread kaustubh khasnis
Hi Gary, We also have observed this problem, when the backlog piles up (e.g. for some reason consumers are disconnected, like network outage) producers as well slows down, even when producer flow control is disabled, send is asynchronous. Thanks and regards Kaustubh On Tue, Sep 13, 2011 at 3:18 A

Re: slow speed sending message

2011-09-12 Thread wglass
Thanks for the tip. I didn't have JMX on when it slowed down. I've turned it on now and am waiting to see if it happened again. Question - am I right in understanding that flow control will turn on automtically when the rate goes over a certain level? Will it then shut off? Second question. I

Re: NMS Consumer Not Receiving Messages

2011-09-12 Thread Timothy Bish
On Mon, 2011-09-12 at 15:10 -0700, Todd wrote: > I've poked around a bit and haven't found anything in the forum or docs. > > I created what is supposed to be an asynchronous consumer. I found some code > in the NMS docs that I adapted. See below. (You can ignore the XML > deserialization stuff.)

NMS Consumer Not Receiving Messages

2011-09-12 Thread Todd
I've poked around a bit and haven't found anything in the forum or docs. I created what is supposed to be an asynchronous consumer. I found some code in the NMS docs that I adapted. See below. (You can ignore the XML deserialization stuff.) This worked once or twice, but I cannot get it to work a

Re: Backlog data causes producers to slow down.

2011-09-12 Thread bbansal
Hey Gary, I will try to write a testcase but based on my Jprofile it looks to me contention is for write lock due to removeMessages() calls after they receive the ack from the client side and the incoming producer messages. I am going to play with producer-flow-control settings and other configur

Unexplained producer throttling when using a network of brokers

2011-09-12 Thread bob.cot...@gmail.com
ActiveMQ 5.5.0 Name : IBM Performance Harness for Java Message Service. Version : 1.2 Build : 488 Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425) OSX 10.6.8 Producer perfharness commandline: java -Dactivemq.base=$ACTIVEMQ_HOME JMSPerfHarness -pc JNDI -ii org.apache.activemq.jndi.

Re: Help building ActiveMQ CPP 3.4.0 on Solaris

2011-09-12 Thread Timothy Bish
On Mon, 2011-09-12 at 09:29 +0100, nospam.1.friedbad...@spamgourmet.com wrote: > Hi, > > I can't get the Active MQ library 3.4.0 to build on Solaris. I have > the Sun Studio 11 compiler. I think I have read all the READMEs. If > I try to build without running autogen.sh > (http://activemq.apach

Log4j SMTPAppender not working within ActiveMQ-Camel

2011-09-12 Thread billy
I want to email WARNINGs and above in my log file to myself, but I'm having trouble getting the Log4j SMTPAppender to work in ActiveMQ. I created a small java test program and verified that my Log4j SMTPAppender properties are correct and that I can send myself an email, but when I copy these prop

Re: Backlog data causes producers to slow down.

2011-09-12 Thread darren
I also noticed this problem. When there is high throughput and consumers get bogged down working in between messages, they eventually get dropped and must re-open a connection or they will stop receiving messages. The problem with that is that consumers will have to actively monitor their connect

Re: Backlog data causes producers to slow down.

2011-09-12 Thread Gary Tully
on the results of your jprobe profiling, it would be good to identify if there is a real contention problem there. If you can generate a simple junit test case that demonstrates the behavior you are seeing, please open a jira issue and we can investigate some more. A test case will help focus the a

Re: Backlog data causes producers to slow down.

2011-09-12 Thread Gary Tully
for the queue case, with backlogs (when the consumers don't keep up) you may want to experiment with On 12 September 2011 01:08, bbansal wrote: > Hello folks, > > I am evaluating ActiveMQ for some simple scenarios. The web-server will push > notifications to the queue/topic to be consumed by on

Re: setProducerWindowSize inhibits propagation of ResAllocEx + producer stays forever blocked once it blocks

2011-09-12 Thread AndreiD
Any suggestions/hints? Let me know what additional details I can provide. -- View this message in context: http://activemq.2283324.n4.nabble.com/setProducerWindowSize-inhibits-propagation-of-ResAllocEx-producer-stays-forever-blocked-once-it-blocs-tp3782348p3807775.html Sent from the ActiveMQ - Us

Re: Camel - PooledConnectionFactory or not

2011-09-12 Thread oseymen
Thanks for your reply Jason! That link you provided recommends the use of PooledConnectionFactory if I am publishing messages - which is OK for B2 endpoint in my above example and recommends using MessageListenerContainer for consuming messages which is for B1 endpoint. This also correlates to an

Re: Camel - PooledConnectionFactory or not

2011-09-12 Thread Jason Whaley
> > > My questions are: > 1. Where can I control the number of producers pooled in > PooledConnectionFactory? Does it create and pool one producer per session > (maximumActive setting above)? You can't really enforce the maximum number producers you actually have created, since a session can p

Camel - PooledConnectionFactory or not

2011-09-12 Thread oseymen
Hi all, I am trying to understand the most optimised way to send messages concurrently between two activemq endpoints using Camel. There has been some discussions on this in the mail groups but some of them confuses me even more. So I am looking the draw the line under this topic and get your recom

Help building ActiveMQ CPP 3.4.0 on Solaris

2011-09-12 Thread nospam . 1 . friedbadger
Hi, I can't get the Active MQ library 3.4.0 to build on Solaris. I have the Sun Studio 11 compiler. I think I have read all the READMEs. If I try to build without running autogen.sh (http://activemq.apache.org/cms/using-the-solaris-cc-compiler.html) I get many compilation errors, only some of w

Re: slow speed sending message

2011-09-12 Thread Torsten Mielke
Perhaps try connecting to the broker using jconsole and check the brokers JMX statistics. Do any of these at broker level or at destination level stick out and may explain the slow performance that you encounter (queue size, memory percent usage of broker and of destination, store percent usage,