[CONJ-796] Com_stmt_close is not increasing Created: 2020-06-08 Updated: 2020-11-18 Resolved: 2020-11-18 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | question |
| Affects Version/s: | 2.5.4 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Allen Lee (Inactive) | Assignee: | Diego Dupin |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | need_feedback | ||
| Environment: |
MariaDB Server - 10.3.22 |
||
| Description |
|
customer reported that they hit this error initially with mariadb-java-client-1.4.6.jar
With some investigation and trial and recommendation from engineering, they have upgraded to mariadb-java-client-2.5.4.jar, but still hitting the same error. Looking at Com_stmt_close, it's value is not even close to Com_stmt_prepare. -initial report
This is EJB configuration:
|
| Comments |
| Comment by Diego Dupin [ 2020-06-08 ] |
|
By default, client use client prepare, so no Com_stmt_execute would be executed. This is not the case here. Default value of `prepStmtCacheSize` is 250. With a pool size of 100 to 400, that means having up to 100 000 cached prepared statement, that is > of the 32768 maximum. First thing would be to know the exact configuration about those options. Another problem is that cache is enable wildfly side too (with `prepared-statement-cache-size` and `share-prepared-statements`). either use one or the another, but not the 2 at the same time. |
| Comment by Diego Dupin [ 2020-11-18 ] |
|
I can only indicate to use a more recent version (mariadb-java-client-1.4.6.jar) is quite old. |