-
Estimation of expected background traffic for a subscriber that is not receiving data?
Suppose I have a c# application which receives guaranteed messages from a solace pubsub+ broker. The application runs as a windows service or daemon. In other words it is always running, but essentially just sitting idle (asynchronously waiting on an IAsyncEnumerable) when there is no data to process. Under this scenario I…
-
Solace Software standard version Upgrade for AWS
Currently we are using Solace Software Stand version 9.8 and we are planning to upgrade to 9.12. As per the documentaion available to upgrade solace version for AWS, We ahve to download entire AWS Instance. Is there a way we can upgrade only the solace service version instead of downloading the entire AWS Instance ?
-
Non-Durable Queue Lifecycle
Hi Community, I am going through Understanding Solace Endpoints: Durable vs. Non-Durable - Solace and tried to create Queues using Solace Java API (jcsmp). We could see that Non-Durable queue gets deleted if it is disconnected from Client for more than 60 seconds. Can it be possible to increase more than 60 seconds , for…
-
How can you find topics that have no subscriptions?
A publisher can be producing events on a topic that have no interested consumers. Is there a way to list those topics for the purposes of clean-up or decommission of unused flows? This condition would also be causing the client counter Ingress Discard - No Subscription Match to increment.
-
How do I publish a bytearray on the Solace Direct Publisher?
Hello everyone! Trying to publish a bytearray instead of an outbound message object on the direct publisher but it seems nothing is being published / subscriber is mishandling the received message. Can't seem to figure out which. Here is my publisher script: def publish_one(self, msg, _topic): try: topic =…
-
Topic Naming Validation via Regex
Hi Solace Community, I wonder if anyone else before had the need to validate topic names (including wildcards), for example in CI/CD pipelines. Because I couldn't find anything, I've tried myself to assemble a regex that validates the general structure of topic names. By no means I feel like it's perfect, however at least…
-
Solace spring cloud stream - pubsub
I was going through this post and got to know how can i work with topic, i can have many queues subscribing to one topic and each get message right ? i can have one queue subscribing to many topic as well right ? Topic subscription on Queues makes it persist, but.. if the application is scaling up and down with many…
-
Issues with running Solace Helm chart with Redundancy and TLS enabled.
Trying to figure out what reason this would not work. I am able to use the solace helm chart (https://github.com/SolaceProducts/pubsubplus-kubernetes-quickstart) to run solace in my GKE kubernetes cluster with tls enabled using my cert secret, however when I enable redundancy, 2 of the pods will not become ready. I was…
-
Assert Durable Queues Into Existence Via AMQP?
Hello, I'm used to RabbitMQ / AMQP 0-9-1. Clients with the right credentials can assert queues into existence and bind them to multiple topic bindings. Clients can specify if queues are durable etc. It's quite convenient. I'm trying to get the same thing working in Solace via AMQP 1.0. Sorry but I'm not super familiar with…
-
Pub-sub with multiple consumers having offline capabilities
Hi, We have an application running with multiple instances and consuming from a solace queue. We want all the instances to receive messages. Currently, only one of them receives messages. The instances can be scaled up and down dynamically and if one of them is offline, they should be able to receive messages after coming…
-
Persistent receiver with subscription-specific listeners
Hi, Is it possible to have multiple topic-specific receivers and handlers to consume messages from a queue? Like: var receiver1 = messagingService.createPersistentMessageReceiverBuilder() .withMessageAutoAcknowledgement() .withSubscriptions(topicSet1) .build(queue) .start(); receiver1.receiveAsync((message) -> { //...…
