how to fix the issue CacheSql - All buckets for {path_to_view} are in use.?

how to fix the issue CacheSql - All buckets for {path_to_view} are in use.?

book

Article ID: KB0079398

calendar_today

Updated On:

Products Versions
TIBCO Data Virtualization -

Description

I am always getting in the Cs_server.log,ERROR [jetty thread pool-670] 2018-10-11 13:18:48.253 -0600 CacheSql - All buckets for {path_to_view} are in use. Trying to clear them inline

What does this mean, and how do I fix it? Nearly all of my cached objects generate this error message.

Issue/Introduction

I am always getting in the Cs_server.log,ERROR [jetty thread pool-670] 2018-10-11 13:18:48.253 -0600 CacheSql - All buckets for {path_to_view} are in use. Trying to clear them inline What does this mean, and how do I fix it? Nearly all of my cached objects generate this error message.

Resolution


As a proactive measure to avoid the erroe, you will have to check in Studio if there are client connections accessing the view which is cached. After that you  have the following options.
wait for the client connections to finish before they trigger the cache refresh.
Increase the number of buckets to accommodate concurrency.
Please   following instructions to get rid of the Error. 


Occasionally when performing a cache refresh, you might encounter a situation where you receive a message stating:
All buckets for the cached resource are in use

Typically this message is displayed because there are several open client connections that are accessing the data in the cache buckets.
To manage the buckets
1. Open Studio, and open the Studio Manager.
2. Open Sessions.
3. Determine if any client connections are accessing the view which is cached.
4. Determine which of the following options is best for your situation:
— Wait for the client connections to finish before rerunning the cache refresh.
— Increase the number of buckets to accommodate concurrency.
5. To modify the Number of Caching Tables defined for your cache, see Enabling Caching to Multiple Tables.
6. Save any changes you have made.
7. Rerun the cache refresh.