Open topic with navigation

# Store Detail Panel

The Store details panel presents the details of a persistence store definition. In edit mode, you can modify the definition.

From the left menu, select Stores. Select the three dots above a store, then select View Details.

GUI Parameter | JSON Attribute | Description
--- | --- | ---
Dynamic Durables Limit | `dynamic_durable_limit` | Optional. This parameter limits persistence service memory growth by restricting the number of dynamic durables that the store can create. When a program attempts to create a dynamic durable in excess of this maximum, the create subscriber call throws an exception. Zero is a special value, indicating no limit. When absent, the default value is zero. For further details, see Persistence Limits.
Maximum Message Limit | `message_limit` | This parameter limits the number of messages that can be held by the store. When this limit is reached, the client receives an exception on `tibPublisher_Send` or `tibPublisher_SendMesages` (when `store_confirm_send` mode is set on the store). However, the client library retries the sends. To have the exception presented to the user, the client application must specify a finite persistence retry duration. Note that even when messages are stored on disk, message metadata is still stored in memory. Hence, use this setting to constrain memory use. Zero is a special value indicating no limit. The store may grow until it exhausts available memory or disk of any one of its persistence services.
Maximum Message Size | `max_message_size` | Optional. Set the maximum allowed message size. If the application's message exceeds the configured limit, `tibPublisher_Send/tibPublisher_SendMessages` calls get an exception (if the store publisher mode is `confirm_send`). See Maximum Message Size.
Swap Byte Limit | `swap_bytelimit` | Optional. If message swapping is enabled, set a byte quantity threshold for the store above which messages are swapped to disk to keep store memory use limited. Valid values are -1 (unlimited), 0, or any positive byte count. Positive byte counts can be expressed with a suffix. For example, `100`, `100m`, `100mb` are all valid. Default is 0. If `disk_swap` is set to `false`, this parameter is ignored.

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.