About jdbcQueryManager.cacheMetaDataTask.enable property

[MARUBUN SUPPORT]

Hi API Gateway Support team,

I need your help.

Here is jdbcQueryManager.cacheMetaDataTask.enable property.

"https://techdocs.broadcom.com/jp/ja/ca-enterprise-software/layer7-api-management/api-gateway/congw-10-1/reference/gateway-cluster-properties/jdbc-cluster-properties.html"

The default of the property is "true".
If we set "false" into the property, what should we pay attention?

Best regrads,
Marubun

[MARUBUN SUPPORT]

HI,

I'm waiting for your reply.

Best regards,

Marubun

[Raju Gurram]

jdbcQueryManager.cacheMetaData.enable - to cache the metadata of JDBC procedures / functions to be executed

jdbcQueryManager.cacheMetaDataTask.enable - to make sure the cached metadata up-to-date with the actual DBMS changes. This will be done asynchronously.

When it (second property) is set to false, cached items are not refreshed periodically, hence they are subjected to the removal. Next time, when needed, metadata will be fetched and cached as part of the JDBC statement preparation. Having said that, Perform JDBC Query assertion is not impacted functionally. 

[MARUBUN SUPPORT]

HI Raju,

Thank you for your update.

However, just to be sure please let me ask you a question.

Even if we set "False" into the property, meta data will cache but it is not cached periodically.

My understanding is correct?

Best regards,

Marubun,

[Raju Gurram]

Yes, metadata will still be cached if jdbcQueryManager.cacheMetaDataTask.enable property was set to false. But, it will not be refreshed periodically.

Please note that, the caching metadata will be disabled when the jdbcQueryManager.cacheMetaData.enable property is set to false.

[MARUBUN SUPPORT]

Sorry Raju,

Please let me ask you a question again.

According to your answer,

>Please note that, the caching metadata will be disabled when the jdbcQueryManager.cacheMetaData.enable property is set to false.

What does it mean(the caching metadata will be disabled)?

The metadata will be cached but the metadata is not used?

Best regards,

Marubun

[Raju Gurram]

:), I'm sorry if my statements are ambiguous. 

Metadata will be fetched but not cached when we set the jdbcQueryManager.cacheMetaData.enable property to false.

May I know the reason for revisiting these values for your gateways?

Thanks.

[MARUBUN SUPPORT]

HI Raju

Thank you for your help.
First of all, I would like to know about the property's behavior.
if we set "False" into the property, meta data will NOT cache.
It is correct, isn't it?

According to your answer,
>Metadata will be fetched

What does it mean(fetch)?
metadata is fetched by procedures or functions but it is not cached.
Correct or not?

>May I know the reason for revisiting these values for your gateways?

According to my customer, 
When a database access occurs at the same time as a metadata acquisition process and 
a business request, there were cases where the business request was delayed, so they are considering turning off the metadata acquisition process.

Best regrads,
Marubun

[Raju Gurram]

Sometimes, it needs a more information to execute certain JDBC statements (functions or procedures). Because of which, metadata will be fetched (or retrieved from the Database) and cached for subsequent statement executions. 

Fetching the metadata is inevitable whether the caching is enabled or not.

This metadata about the statement will be cached for future use when jdbcQueryManager.cacheMetaData.enable = true

Above cached metadata will be refreshed periodically by a background thread when jdbcQueryManager.cacheMetaDataTask.enable = true. If this is set to false, metadata will still be cached but not refreshed periodically.

As per your requirement, it seemed OK to disable the periodic refresh task ( via jdbcQueryManager.cacheMetaDataTask.enable = false).

Thanks.

[MARUBUN SUPPORT]

Hi Raju,

Thank you very much indeed!

I understand what you say.

Marubun,