Search docs.molo17.com

    Solace PubSub+ logo Solace Pub Sub+ agent changelog

    Release notes

    2.3.0.3

    Released: October 21, 2026

    • Each agent connects to the broker with its own client name, Gluesync Solace agent <agent id>, instead of the same Gluesync Solace agent for every agent. A client name must be unique in its Message VPN, so with two Solace agents on the same broker and VPN (two pipelines, or two Core Hubs) every connection made the broker close the other session: the agents reconnected in a loop and messages the agent had reported as sent were lost. Client usernames are unchanged; if you look the agents up by client name on the broker, they now show as Gluesync Solace agent <agent id>;

    2.3.0.2

    Released: October 19, 2026

    • New optional topicPrefix agent property, joined with / in front of every target topic, for hierarchies such as acme/movex/<collection>/<action>. Wildcards (*, >) are refused, and left empty, topic names are unchanged (GSSD-1428);

    • A batch is confirmed to Core Hub only once the broker has it. In persistent mode the agent waits for the broker to acknowledge every message of the batch and fails the batch on any NACK, so it is retried (at-least-once) instead of being dropped; before, a NACK was lost. In direct mode the publisher buffers at most 10,000 messages and then waits, so a large snapshot no longer fills the heap: a 1-million-row snapshot failed with OutOfMemoryError on an 8 GB heap in both modes;

    2.3.0.1

    Released: October 15, 2026

    • The agent hands its pooled database back when its pipeline is deleted or detached and when its initialization fails. Before, the next pipeline writing to the same database could fail in a loop with NoClassDefFoundError;

    2.3.0

    Released: October 13, 2026

    • Agent compatibility upgrade to Gluesync 2.3;