title: Parallel message consumption on ActiveMQ topic
body: <p>It appears that durable topics in ActiveMQ (and this seems to be an impediment in JMS itself) that only one consumer can be active on a subscriber.</p>
  
  <p>That is, in the ActiveMQ docs:</p>
  
  <blockquote>
    <p>A JMS durable subscriber MessageConsumer is created with a unique JMS
    clientID and durable subscriber name. To be JMS compliant only one JMS
    connection can be active at any point in time for one JMS clientID,
    and only one consumer can be active for a clientID and subscriber
    name. i.e., only one thread can be actively consuming from a given
    logical topic subscriber.</p>
  </blockquote>
  
  <p>Other queueing systems, however (looks like Azure Service Bus does this, based on the documentation), seem to easily allow multiple threaded "subscribers" on a single "subscription". In this day and age, one would think that would be a given.</p>
  
  <p>Why is this the case? Is this going to be resolved in future versions of JMS and/or ActiveMQ?</p>
  
  <p>P.S. It seems like "Virtual Topics" (the doc that's quoted above) is a not so ideal and not-so-performant workaround for this scenario, as it appears to create a completely separate queue in the background for each subscriber.</p>