This Exception is as follows:
MySQL session isolation level 'REPEATABLE-READ' is no longer supported. Session isolation level must be 'READ-COMMITTED'.
I know the resolution is as follows, but I don't know why the db config was changed. Could anyone to figure it out? Thanks.
-- 解决办法:
-- 查看InnoDB会话级别的事务隔离级别:
-- SELECT @@tx_isolation;
-- 修改事务隔离级别:
set global transaction isolation level read committed;
set session transaction isolation level read committed;
Hi @YY哥 ,
Welcome to Atlassian community.
Yes, as rightly pointed out by @Nic Brough -Adaptavist- you should change it to read-committed. Actually we have a detailed KB regarding the same. You can go through the below page.
I hope above info helps. Have a good weekend.!
Thanks,
Srinath T
I've run into this too, I managed to get away with swapping the database to read-committed.
If I were you, I would test that change to read-committed works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.