nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Unknown system variable 'storage_engine'" JIRA 7.0 and MySQL 5.7.9

Semen Pleshivts

Hi!

I'm trying to install JIRA 7.0 on MySQL 5.7.9 and connector "mysql-connector-java-5.1.37-bin.jar".

When I'm trying to connect to MySQL DB, error message appears:

---

"Unknown system variable 'storage_engine'"

---

This variable is NOT present in my.ini. Insead, I'm using default-storage-engine = InnoDB.

Well, system variable storage_engine is deprecated "as of MySQL 5.5.3".

Should I use version of MySQL below 5.5.3 ?

Best regards, Semyon.

jiraCapture.JPG

Accepted answers

All comments

Fabian Wallentowitz

same here....

the mysql connector url should be defineable as in the confluence setup...

Matt White

Yah, same issue here. rolled back to mysql 5.6.27 and it is happy now.

MattS

There's a feature request at jac for this.

Andrew Claridge

https://jira.atlassian.com/issues?jql=text ~ "storage_engine 5.7.9"

Vin

Here are the steps to get around:

If you are doing this the first time, copy the sample dbconfig.xml from https://confluence.atlassian.com/adminjiraserver070/connecting-jira-applications-to-mysql-749382640.html, else edit the existing dbconfig.xml as an administrator. It is in the JIRA HOME folder.
Search for <url> tag in the file.
Remove the text: "sessionVariables=storage_engine=InnoDB" (sans double-quotes).
Ensure that the server and database name match the ones specified during installation.
Restart JIRA.

yurii-bitbucket

i got it working

in short see my fork : https://github.com/yurii-github/mysql-connector-j

------------------------

changing JIRA was too hard for me, too many places with hardcoded storage_engine parameter, so i did a change into mysql connector itself - i'm replacing deprecated variable in connection constructor. like this

https://github.com/yurii-github/mysql-connector-j/commit/47199bf3ef4a9c3db6eb3a1858fc53c980d8a439

built snapshot is in repo too: https://github.com/yurii-github/mysql-connector-j/blob/release/5.1/mysql-connector-java-5.1.38-SNAPSHOT-bin.jar

or you can build it yourself etc.

just note, it was built without jdk1.6. Also no warranties etc, you know smile

hope it helps and doesn't crash for you, it works for me though.

regards,

Yurii

MattS

https://jira.atlassian.com/browse/JRA-40198

MattS

That's a cool piece of work but where else was storage_engine hard coded? https://answers.atlassian.com/questions/32023132/answers/32522729 looked like you could just tweak dbconfig.xml no?

yurii-bitbucket

unfortunately i didnt save search progress. as i remember, just changing dbconfig didn't help me. i found hardcoded "storage_engine" about 4 times. some in text files INF or something, some in plugins in jar files. but even after i repackaged jar files it was still failing with this error. i think some hardcoded link(s) still exist in obfuscated compiled code, haven't look too much into this as connector license allows me to modify its code and in one place. anyway, if changing config file works for you - great. i wonder why it didnt work for me then regards

Frank Adcock

sudo vi /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/database-defaults/mysql.properties

Remove the text as stated above including the preceding & character.

vellotis

Thank you @Vin.

To the others: It is not needed to modify connector. Just modify the dbconfig.xml.

Daniel Duerr

@Frank Adcock nailed the solution for a new JIRA install, since it won't look at the dbconfig.xml file when the setup wizard is wanting to be run.

Emil Georgiev

Thank you!!! After 2 days of searching and trying to get around this, I finally was able to get a successful connection with your jar!

Paul Stewart

Just got burned by this myself.. 5.7 has been out for quite some time and was surprised to see this issue come up.

Maxim Lebedev

Meet with a same problem. And it has been fixed by rollback to to mysql 5.6.27

Gyana Ranjan

Thanks a lot.. It works!

Samrat Basra

yes. it will work with mysql 5.6.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration