Open topic with navigation

# Default Durable

You can use the default durable to add delivery assurance to any application, even applications that do not explicitly supply a durable name or a subscriber name in their create subscriber calls.

To use the default durable, administrators may map the default subscriber name (`_default`) to a durable in one or more application instance definitions.

## Restrictions

- Each application instance definition supports at most one default durable per endpoint. That is, for each application endpoint, each application instance definition can map the default subscriber name to at most one durable name. (However, separate application instance definitions can map their respective default subscribers to different durable names.)
- At any moment, at most one running process can claim a specific standard durable.

  This restriction applies to all standard durables, but pay special attention to prevent inadvertent violations by processes that use default durables.

  (This restriction does not apply to shared durables nor last-value durables.)

See Also: Configuring a Default Durable

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.