Open ahaq0 opened 1 year ago
Just to add more information, found out that this issue occurs when inserting a record with id greater than 2^16
Also, to make matters more interesting, the issue can be mitigated by making sure that the insert queries fit the correct decimal format.
Can provide more information as necessary
Not sure if this will work for others; we were also getting this error when we upgraded our application to Spring Boot 2.5.x
Nothing seemed to work to fix the ArrayIndexOutOfBoundsException We were also getting this on random tables in different applications.
We came across this 1 thread here - https://bugs.mysql.com/bug.php?id=105706
After adding the mariadb-java-client
dependency and switching to the org.mariadb.jdbc.Driver
driver class name according to the steps here - https://springframework.guru/configuring-spring-boot-for-mariadb/
Errors seem to have stopped in last 1 day. (We're still monitoring these)
FYI: Our DBs are MariaDBs, maybe that's why this worked for us.
Hi All,
I'm dealing with this intermittent ArrayIndexOutOfBoundsException ocurring when attempting to run certain
INSERT
queries that work fine sometimes and fail otherwise.Setup Hikari 5.0.1 my-sql-connector-java 8.0.31
my-sql 8.0.30
Here is the stack trace:
the issue appears reminisicent of the previous bug here https://github.com/brettwooldridge/HikariCP/issues/1712 however, we are now
8.0.31
of my-sql-connector java and the issue seems to occur on 1 of 4 environments with consistent config randomly.For instance, previously, the query would fail 9 / 10 times across all pods and started occuring out of nowhere i.e. there was no update or config changes that spurred it.
Later, we were able to stop the error by truncating the associated the table. This has appeared to work so far.
Upon digging we found that potentially there is an issue of inserting a
double
in a Decimal 10,0 column. Was about to fix that but if it was the culprit why would it stop occuring after truncating the table? Further, why would this error occur in only one environment ( an environment that gets more traffic)One thing to note the environment where this issue is occuring has ongoing activity ( load tests) could load ( and the associated records in the table) be a factor?
Any insights would be sincerely appreciated!
Thanks