> 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.41/toa-1.16.34.md).

# Hornet 1.16.34

<mark style="color:green;">Release Date: Monday, August 24, 2026</mark>

## Compatibility Notes

The following issues have compatibility implications:

* [TOA-132 - receiveOnly not enforced at runtime for sendMessage(channelName, ...) overloads](#toa-132)

## Change Summary

* [Bug](#bug)
  * [TOA-132 - receiveOnly not enforced at runtime for sendMessage(channelName, ...) overloads](#toa-132)
  * [TOA-134 - Hornet service loader leaves model-XML temp files (xmd\*) accumulating in /tmp](#toa-134)

## Bugs <a href="#bug" id="bug"></a>

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

<mark style="color:orange;">receiveOnly not enforced at runtime for sendMessage(channelName, ...) overloads</mark>

Prior to this release, the `receiveOnly` attribute introduced in TOA-131 was only enforced at service-model parse time — a runtime call to one of the `sendMessage(String channelName, IRogMessage, ...)` overloads naming a receive-only channel was accepted by the framework and forwarded to the AEP engine, defeating the intent of the attribute. This release extends `receiveOnly` enforcement to the runtime channel-name send path: the `sendMessage(String channelName, ...)` overloads now reject attempts to send on a receive-only channel with a descriptive exception.

{% hint style="warning" %}
**Compatibility Notes**

**Areas of Impact**: None

The `receiveOnly` channel attribute is now enforced at runtime as well as at service-model parse time. A call to a `sendMessage(String channelName, ...)` overload naming a receive-only channel was previously accepted and forwarded to the AEP engine; it is now rejected with a descriptive exception. Code that relied on the previous behaviour, whether deliberately or not, will see an exception where the send formerly succeeded.
{% endhint %}

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

<mark style="color:orange;">Hornet service loader leaves model-XML temp files (xmd\*) accumulating in /tmp</mark>

Prior to this release, Hornet extracted each ADM message-model XML to a temporary file in java.io.tmpdir during service loading and relied on JVM-exit cleanup to remove it; on non-graceful shutdowns these temp files accumulated in /tmp. They are now removed immediately after the model is parsed.