Yes, we have done that and there doesn't seem to be any sign of trouble. Threads are ~ 100 and memory is well below maximum.
The way the system works we have producers publishing to a single queue, the consuming application then processes those messages and publishes to a bunch of secondary queues. which it then consumes in separate threads. An earlier reply suggested that it could be producer flow control which I had originally discounted as the initial producer is not being throttled but I am wondering if it is possible for AMQ to throttle the publishes to the secondary queues? -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-tp4701242p4701246.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
