DEV Community

Query Filter
Query Filter

Posted on

docker99

Subject: Regarding Persistent Test Messages in the CTI_QA Environment

Dear Customers,

Please accept my sincere apologies for the "LEONID CITI DEMO" messages that have been appearing within the system. I understand that these persistent messages have caused frustration and confusion, and I want to provide a clear explanation of why this occurred and how we are resolving it.

What Happened

During testing, I utilized two Persistent Queuesmy_persistent_queue and my_persistent_queue123—which I bound to several topics, including US/COMET/INC/ORDER/CASH/COES/SLSI. In the Solace ecosystem, a Persistent Queue acts as a physical "mailbox" on the broker's disk. Unlike a standard topic, which is ephemeral, a message delivered to a persistent queue will remain there indefinitely until it is manually purged or successfully acknowledged by a consuming application.

Because these queues were linked to multiple topics, they captured and stored every "LEONID" test injection across several routing paths. These messages have remained "surfacing" because they were never consumed and removed from the broker’s storage.

The Resolution Plan

To permanently stop these messages from appearing, the "mailboxes" must be cleared and their links to the production-style topics must be severed. I have provided a guide below for the necessary actions within the Solace PubSub+ Manager.

Step Action Purpose
1. Locate Queues Find my_persistent_queue and my_persistent_queue123. Identifies the specific test containers.
2. Remove Bindings Open the Subscriptions tab and delete all topic bindings. Stops the queues from "attracting" any future messages.
3. Purge Messages Select Action > Purge. Wipes the existing demo messages from the disk.
4. Delete Queues Select Action > Delete. Permanently removes the test infrastructure to prevent recurrence.

I am currently auditing our source code and deployment scripts to ensure these test queues are not recreated in future builds. Thank you for your patience as we clean up these artifacts.

Best regards,

Leonid
Software & DevOps Engineer

Top comments (0)