anchor.diff:      <metric-set-dmr name="Message Driven EJB Metrics" enabled="true">
           <metric-dmr name="Execution Time" interval="5" timeUnits="minutes" path="/" attribute="execution-time"
   />
  -        <metric-dmr name="Invocations" metricType="counter" interval="5" timeUnits="minutes" path="/" attribut
  -e="invocations"/>
  +        <metric-dmr name="Invocations" metricType="counter" interval="5" timeUnits="minutes" path="/"
  + attribute="invocations"/>
           <metric-dmr name="Peak Concurrent Invocations" interval="5" timeUnits="minutes" path="/" attribute="pe
   ak-concurrent-invocations"/>
           <metric-dmr name="Wait Time" interval="5" timeUnits="minutes" path="/" attribute="wait-time"/>
  
positive.code: ----
  <1> You need to provide username/password for one Hawkular user. The app server will only show for this user.
  <2> Change 'Local Server' to some *unique* value among your managed machines.
  <3> Optional A single WildFly instance can manage multiple remote WildFly server, in that case you need to enable the remote-dmr section and specify username and password of a management user of the remote server.
  
  
  * In the `standalone/configuration/standalone.xml` file of your Hawkular instance, add an outbound socket binding
  `<socket-binding-group>` that points to your running Hawkular server instance:
  
  [source,xml]
  
negative.code: === Error on starting Hawkular- OutOfMemoryError: unable to create new native thread
  This may happen if you use Cassandra embedded with Hawkular on *x systems
  
  Cassandra requires `ulimit` settings that are higher than usual on common *nix distributions. First check your present limits with `ulimit -a` and eventually increase open files to 65535 and max user processes to 4096 as appropriate on your system.
  
  On RHEL, CentOS and Fedora the settings can be made persistent in `/etc/security/limits.conf` like this:
  ----
  