Github user gemmellr commented on the issue:
https://github.com/apache/qpid-jms/pull/3
As you note this is a bit hacky. We'll see if we can add something to
similar effect at some point.
The client is using 'never' since that is whats actually needed to truly
satisfy the JMS semantics for a durable subscription. The server could arguably
accept that and still delete the subscription regardless after a suitably large
'administratively enforced' idle/detached period. It shouldnt accept it then
delete it immediately upon detach just because the timeout (which obviously
doesnt apply to the 'never' case) is 0, and obviously crashing if you set it
above 0 not being ideal either. I'd suggest you raise an issue with those folks
too.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
