Upgrading Jira removed .jks

[Nate Christensen]

Hey everyone, 

So I posted last week about upgrading JIRA and the proper steps to do so. I followed them only to realize that the https portion didn't work anymore. 8080 worked just fine.

After a bit of searching I came across some documentation about the keystore and the .jks file as well as the config.bat file.

So I went and opened up the config file and went to the Web server tab, and it was reset. And doing some more looking on the server, the jks file was gone as well. 

For the heck of it, I tried using the old .jks file from a backup which didn't work so well. With that file set up in the config.bat tomcat wouldn't run at all.

So after doing the upgrade, am I going to have to redo the server certificates in order to get the https link to work correctly?

[Nate Christensen · Accepted solution]

So I did those suggestions, and that wasn't really the problem I was running into. What my problem was that after I updated and ran the config.bat file it put all the right info in, but the connector was wrong. 

I had to change it from:

protocol="org.apache.coyote.http11.http11protocol"

TO

protocol="org.apache.coyote.http11.http11Nioprotocol"

The config.bat didn't update that. This fixed what I was having problems with

[Andy Heinzer]

That was a known problem in regards to upgrades of Jira 7.3 and later.  This is mentioned in the upgrade and release notes:

https://confluence.atlassian.com/jirasoftware/jira-software-7-3-x-upgrade-notes-861251109.html

That specific error is because the version of Tomcat that Jira ships with no longer supports the old http11 connector.

[Andy Heinzer]

I agree with Nic here.  You can technically install Jira without having to install Java separately because the exe and bin installers are including an Oracle JRE package to run Jira.

But I'd still recommend installing your own Oracle Java jdk/jre outside the Jira directories and having Jira use that Java instead.  Provided you setup the $JAVA_HOME variable on your system, then this way Jira isn't using the bundled java, but rather your own defined Java install path.   This way you can avoid this kind of configuration loss when upgrading Jira on this system.

If you don't do this, then every upgrade to Jira that bundles a different Java JRE could potentially cause this kind of configuration loss. 

[Nic Brough -Adaptavist-]

Yes, I'm afraid you will need to re-do the key installation into a jks store.  I tend to keep the key stores outside the Jira installation, in the jira user's home directory, so that you only lose the pointers in the setenv file on upgrade.