Solace Community is getting a facelift!

On March 3rd we will be starting the process of migrating Solace Community to a new platform. As a result, Solace Community will go in to a temporary read-only state. You will still be able to come onto Solace Community and search through posts to find answers, but you won't be able to ask questions, post comments, or react in any way.

We hope to have the migration complete by Wednesday March 5th (or sooner), so please keep an eye out!

Non-Durable Queue Lifecycle

triptesh
triptesh Member Posts: 27 ✭
in PubSub+ Event Broker #1

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 example Non-Durable queue will get deleted only when it is disconnected from Client for more than 120 seconds ?


Thanks,

Triptesh

Answers

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #2

    Hi @triptesh,

    No, unfortunately not. The non-durable endpoint lifetime isn't configurable.

    You could, perhaps, use the SEMP API to periodically clean up durable endpoints that have not had a client connected for more than 60 seconds. However, I think it would be worth understanding more about your use case - does your application take more than 60 seconds to start up?

  • triptesh
    triptesh Member Posts: 27 ✭
    #3

    Hi @TomF , For our use case, we need it to handle cases where the client may be disconnected for more than 60 seconds.

  • TomF
    TomF Member, Employee Posts: 412 Solace Employee
    #4

    Hi @triptesh if that's the case then it sounds like you need a durable endpoint.

Categories

This Month's Leaders

This Week's Leaders