> For the complete documentation index, see [llms.txt](https://docs.xplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplatform.com/release-notes/3.16/3.16.32/toa-1.16.27.md).

# Hornet 1.16.27

<mark style="color:green;">Release Date: Wednesday, July 24, 2024</mark>

## Compatibility Notes

No issues have compatibility implications

## Change Summary

* [Improvement](#improvement)
  * [TOA-126 - nv.trace.useslf4j ignored by Hornet service tracer (nv.toa)](#toa-126)
  * [TOA-127 - Excessive trace by nv.toa tracer](#toa-127)

## Improvements <a href="#improvement" id="improvement"></a>

### TOA-126 <a href="#toa-126" id="toa-126"></a>

<mark style="color:orange;">nv.trace.useslf4j ignored by Hornet service tracer (nv.toa)</mark>

This release fixes an issue in which the nv.trace.useslf4j configuration setting is ignored by Hornet service tracer (nv.toa). This causes the trace output by this tracer to use X trace format and output to stdout instead as configured by the appropriate SLF4J config

### TOA-127 <a href="#toa-127" id="toa-127"></a>

<mark style="color:orange;">Excessive trace by nv.toa tracer</mark>

Prior to this release, the Hornet tracer, i.e, the nv.toa logger, outputs the AEP engine configuration if the trace level if at or higher than CONFIG. The AEP engine itself also outputs its configuration when its trace level is set at or above CONFIG. Since the change to make CONFIG the default trace level, both the nv.toa and nv.aep loggers output the engine configuration. This can result in a significant amount of trace when a very large number of message types are employed by an application. To reduce this, this ticket changes the nv.toa logger to output the engine configuration if the trace level if set to VERBOSE or higher.