About JDBC Pool

[MARUBUN SUPPORT]

We have a question about the JDBC pool in Layer7 API Gateway.

We would appreciate any answers or advice you can give us.

 

[Questions]

 

Q1:

When multiple JDBC pools are defined, please tell me the criteria for selecting the JDBC pool used to obtain metadata.

Also, please let me know if there is a way to select it.

 

Q2:

Please tell me the log file where we can check the execution of metadata retrieval.

 

 

Best Regards,

Marubun Support

[Sampath Kumar]

Which APIGW version are you using and what exactly are you trying to do?

[MARUBUN SUPPORT]

Hi Kumar-san,

Thank you for your reply.

Our customer is currently using API Gateway Ver.10.0.
When they were considering upgrading from Ver.10.0 to Ver.11.0, they found it necessary to check about the JDBC pool, and so they asked me a question about it.
I would be grateful for any advice regarding the questions I asked.
If there are any differences in the usage method between Ver.10.0 and Ver.11.0, it would be helpful if you could also let me know about that.

Best Regards,
Marubun Support

[Sampath Kumar]

Hi Marubun,

The JDBC drivers got changed from 11.0 version as compared to the previous versions. So you need to update the driver class names.

As far as the JDBC connection pool is concerned its nothing related to the metadata. Connection pooling helps in reusing the existing connection rather than making connection for every request . Using pool helps in performance.

No criteria for selecting the JDBC Pool with respect to Metadata.

The pool size properties default values, can be edited from the cluster properties: 

jdbcConnection.pooling.minPoolSize.defaultValue

=3
jdbcConnection.pooling.maxPoolSize.defaultValue=15

Logs can be seen in gateway log file.