# Non-Durable Queue Lifecycle

**URL:** <https://community.solace.com/t/non-durable-queue-lifecycle/1161>\
**Category:** Solace Event Broker\
**Created:** [February 22, 2022, 6:23am UTC](https://community.solace.com/t/non-durable-queue-lifecycle/1161 "2022-02-22T06:23:28Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![triptesh](https://avatars.discourse-cdn.com/v4/letter/t/3ab097/32.png) [@triptesh](https://community.solace.com/u/triptesh)\
**Post date:** [February 22, 2022, 6:23am UTC](https://community.solace.com/t/non-durable-queue-lifecycle/1161/1 "2022-02-22T06:23:28Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [February 22, 2022, 9:23am UTC](https://community.solace.com/t/non-durable-queue-lifecycle/1161/2 "2022-02-22T09:23:42Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![triptesh](https://avatars.discourse-cdn.com/v4/letter/t/3ab097/32.png) [@triptesh](https://community.solace.com/u/triptesh)\
**Post date:** [February 22, 2022, 10:19am UTC](https://community.solace.com/t/non-durable-queue-lifecycle/1161/3 "2022-02-22T10:19:29Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![TomF](https://yyz1.discourse-cdn.com/solace/user_avatar/community.solace.com/tomf/32/1749_2.png) [@TomF](https://community.solace.com/u/TomF)\
**Post date:** [March 14, 2022, 10:30am UTC](https://community.solace.com/t/non-durable-queue-lifecycle/1161/4 "2022-03-14T10:30:52Z")

</div>

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