anchor.diff:          ...
       }
   }
  -....
  +--
   
   === Web console improvements
   
  
positive.code: 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}" />
  
negative.code: 
  Once statistics are enabled, the `pooled-connection-factory` resource will have a `statistics=pool` child resource that will returns metrics on the pool used by the `pooled-connection-factory`:
  
  [source, ruby]
  --
  [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra/statistics=pool:read-resource(include-runtime)
  {
      "outcome" => "success",
  