# \#publish-subscribe

**URL:** https://community.solace.com/tag/publish-subscribe/159.md

[Latest](https://community.solace.com/latest.md) · [Categories](https://community.solace.com/categories.md) · [Tags](https://community.solace.com/tags.md)

---

## [SUBSCRIBER\_LOCAL\_PRIORITY is deprecated now - any substitution](https://community.solace.com/t/subscriber-local-priority-is-deprecated-now-any-substitution/4066)

<div class="topic-metadata">

**Author:** [@eaglefive](https://community.solace.com/u/eaglefive)\
**Replies:** 4\
**Last updated:** [March 31, 2025, 8:27am UTC](https://community.solace.com/t/subscriber-local-priority-is-deprecated-now-any-substitution/4066 "2025-03-31T08:27:06Z")

</div>

Hello team, I’ve just realized that deliver-to-one together with Subscriber priority is deprecated now. That was an extremely useful combination because we were able to make our high frequency subscribers highly availab…

---

## [Allowing a publisher to see the last message published while preventing subscription](https://community.solace.com/t/allowing-a-publisher-to-see-the-last-message-published-while-preventing-subscription/2086)

<div class="topic-metadata">

**Author:** [@allmhhuran](https://community.solace.com/u/allmhhuran)\
**Replies:** 4\
**Last updated:** [January 3, 2025, 6:21pm UTC](https://community.solace.com/t/allowing-a-publisher-to-see-the-last-message-published-while-preventing-subscription/2086 "2025-01-03T18:21:46Z")

</div>

I’m a bit stuck trying to figure out the best way to combine some features I’d like to provide in our in-house broker abstraction library. I have an IPublication\<T\> interface, which exposes a “simple” API to consumers…

---

## [Is OAuth service supported by Advance Event Mesh?](https://community.solace.com/t/is-oauth-service-supported-by-advance-event-mesh/2101)

<div class="topic-metadata">

**Author:** [@rajeshy1987113](https://community.solace.com/u/rajeshy1987113)\
**Replies:** 2\
**Last updated:** [December 16, 2024, 6:30am UTC](https://community.solace.com/t/is-oauth-service-supported-by-advance-event-mesh/2101 "2024-12-16T06:30:13Z")

</div>

My Scenario is : 3rd Party —\> Advance Event Mesh —\> S4H Is it possible for a third-party system to authenticate Advance Event Mesh Queue using OAuth credentials? , If Yes - how to create bearer token and pass to AEM ?

---

## [Trouble connecting to Solace and no descriptive error is being received? Certificate auth](https://community.solace.com/t/trouble-connecting-to-solace-and-no-descriptive-error-is-being-received-certificate-auth/2033)

<div class="topic-metadata">

**Author:** [@nomassama](https://community.solace.com/u/nomassama)\
**Replies:** 2\
**Last updated:** [October 2, 2024, 3:00am UTC](https://community.solace.com/t/trouble-connecting-to-solace-and-no-descriptive-error-is-being-received-certificate-auth/2033 "2024-10-02T03:00:45Z")

</div>

Hi, I am trying to connect to event-broker. but could not connect. also the exception I am receiving is not very descriptive about what could be wrong. I have double checked: trust store path. certificate path certifi…

---

## [Unable to Subscribe Topic in Solace Local from Streamset Pipeline (JMS Producer)](https://community.solace.com/t/unable-to-subscribe-topic-in-solace-local-from-streamset-pipeline-jms-producer/1968)

<div class="topic-metadata">

**Author:** [@malikhas14](https://community.solace.com/u/malikhas14)\
**Replies:** 2\
**Last updated:** [July 22, 2024, 9:46am UTC](https://community.solace.com/t/unable-to-subscribe-topic-in-solace-local-from-streamset-pipeline-jms-producer/1968 "2024-07-22T09:46:55Z")

</div>

I have set up Docker containers for SQL Server, StreamSets, and Solace, following the steps outlined in the blog https://solace.com/blog/change-data-capture-solace-streamsets-dr/. My goal is to enable Change Data Capture…

---

## [Why the messages remain in the QUEUE after the subscriber consume the message](https://community.solace.com/t/why-the-messages-remain-in-the-queue-after-the-subscriber-consume-the-message/1942)

<div class="topic-metadata">

**Author:** [@Sbelag](https://community.solace.com/u/Sbelag)\
**Replies:** 2\
**Last updated:** [July 1, 2024, 11:32am UTC](https://community.solace.com/t/why-the-messages-remain-in-the-queue-after-the-subscriber-consume-the-message/1942 "2024-07-01T11:32:16Z")

</div>

Hello, I have a Java Apache Camel consumer that consumes and acknowledge messages from a topic a/b/c/t1 . I have a Queue subscribed to the same topic (a/b/c/\>) . when I push a message (persistent or non-persistent) …

---

## [Solace Try-Me CLI (stm): A sleek command-line tool for messaging Solace PubSub+ Broker](https://community.solace.com/t/solace-try-me-cli-stm-a-sleek-command-line-tool-for-messaging-solace-pubsub-broker/1920)

<div class="topic-metadata">

**Author:** [@giri](https://community.solace.com/u/giri)\
**Replies:** 0\
**Last updated:** [May 2, 2024, 12:47pm UTC](https://community.solace.com/t/solace-try-me-cli-stm-a-sleek-command-line-tool-for-messaging-solace-pubsub-broker/1920 "2024-05-02T12:47:32Z")

</div>

Thrilled to introduce a new command-line tool \*Solace Try-Me CLI, \* simply called stm that brings the robust messaging capabilities of the Solace PubSub+ broker right to your fingertips! stm designed specifically fo…
