I'm using activemessaging to connect to a stomp interface on an ActiveMQ broker, and having trouble processing all of the messages that are coming over my subscription to a topic.
The messages take a fair amount of cpu as they must be unzipped, processed, and stored to the db. So much that I'd like to add another processor (subscriber) to help keep up with the message flow, but I'm not sure how to make two clients feed off of the same topic (not a queue, currently). I tried adding a subcriptionName attribute to my subscription, and started two processors, but that turned it into a durable subscription, and messages started backing up, and activemq hung! I'd rather keep it a non-durable subscription, as I have a MaximumPendingMessageLimit set and would like to discard messages when the subscribers can't keep up. I'd also like to keep sending the messages to a topic rather than a queue, as there are other systems that subscribe to this same topic. Is there a way to do what I'd like to, and not have messages pile up in the broker when the subscriber is slow for any reason? I have a feeling that this is possible, but I just don't know the right approach/configuration. Thanks, -Pete -- View this message in context: http://www.nabble.com/Parallel-processors-on-a-single-topic-queue-tf3608561s2354.html#a10082719 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
