Following up on the work performed here:
https://issues.jboss.org/browse/EAP7-450

Discuss with the various stakeholders (GSS/Dev/QE) and implement (if it makes sense) the disabling by default of enlistment tracing in IronJacamar, in order to get better performance out-of-the-box, however, with the corresponding loss of traceability.

Since it will be a common usecase for a customer to enable this again in case of a problem in the course of diagnosing an issue, it make sense to make the attribute change take place immediately, without the need for a server/subystem restart.

The original Change Request that kicked of the discussion:
https://mojo.redhat.com/docs/DOC-1045012#comment-1013451