anchor.diff:  Artemis uses thread pools for its clients that are running inside the application server. They can now be configured in the `messaging-activemq` subsystem to ensure that their sizes fit the application deployed in WildFly:
   
   [source, xml]
  +--
   <subsystem xmlns="urn:jboss:domain:messaging-activemq:1.1">
     <global-client thread-pool-max-size="${activemq.artemis.client.global.thread.pool.max.size}"
       scheduled-thread-pool-max-size="${activemq.artemis.client.global.scheduled.thread.pool.core.size}" />
  
positive.code:   </server>
    ...
  </subsystem>
  
  [source]
  
  NOTE: By default, the maximum size for client thread pool is not defined. In that case, Artemis will configure them to be 8 x the number of available processors.
  
  
negative.code:         ...
      }
  }
  --
  
  === Web console improvements
  
  