JIRA error 500

[Helpdesk Wildwest.in.ua]

Hi,

after setingup new JIRA service on own server I'm unable to restore DB. There we no backups from JIRA made, only MySQL DB.

1. Clean JIRA was installed
2. ./bin/config.sh
   1. changed DB configuration
3. starting JIRA
   1. first launch succesfull, everything is working (till next restart).
   2. putting JIRA license
   3. after JIRA restart getting 500 error (

      java.lang.RuntimeException: org.apache.jasper.JasperException: com.atlassian.extras.decoder.api.LicenseDecoderNotFoundException: Could not find any valid decoders in [com.atlassian.extras.decoder.v2.Version2LicenseDecoder@5a2a6697, com.atlassian.extras.decoder.v1.Version1LicenseDecoder@4d5979b4] for license string <>

4. checking MySQL DB accordingly to suggested solution - data missing
5. tried to make clean JIRA isntall, connect it to existing DB and making XML Backup from running instance and than restore it on clean installation - getting same error.

JIRA version is:

6.4.1

[Andy Heinzer · Accepted solution]

The error you are seeing here is in regards to an invalid license for Jira.  At least Jira can't seem to decode the license that you have here. 

Are you sure that the database backup you have is from a Jira 6.4.1 version?   If it was, then you technically don't need to apply a new license key if you had a commercial key applied to that instance when the backup was made.

Jira is storing the license in the database.   However if all you have is the database backup, you should only have to apply a new license key if both

1. Your old key is expired AND
2. You are installing a newer version of Jira that was released after the expiration date of your currently applied license.

Meaning, you don't need to apply a new license key as long as you are not doing an upgrade to Jira AND your database backup had a valid license key applied at the time the backup was created.  Even if your old key is expired in that database backup, you should still be able to complete the 6.4.1 provided your license was not an evaluation license, and Jira 6.4.1 was released before the expiration date of your license.

I would be interested to learn if you followed the database setup steps in Connecting Jira to MySQL.   I would still expect this to be followed for new installations, even if you are then still planning to do a database restore to that empty database shell.  Just because we have a pretty specific set of collation/encoding types that are supported for the Jira database, and if you happen to choose an unsupported one, weird/unexpected stuff can happen.

The other part I would be interested in is learning what license key you are using here to apply to the system and what license key is in the database backup.  You can find the latter following the steps in this KB: How to Get and Update JIRA License String from the Database.

If you want to post back the license keys to this thread feel free, I can obscure them after the fact.  If you are not comfortable with that, just let me know and we can find another way to obtain that info.

[Helpdesk Wildwest.in.ua]

After some investigation I've found out that problem is connected with displaying projects and issues from my previous DB. I've tried to access restored version using user which doesn't have administrative access and everything is working fine.

Also after investigation of the backup file, I've found that JIRA was installed as 6.2.1 and then upgrated to 6.4.1, maybe it is some how connected?

Another question if it is possible to find which resources aren't avaliable?

Right now I'm getting:

[Helpdesk Wildwest.in.ua]

Also maybe it is possible to downgrade backup file to previous version? maybe it would be possible to restore file on 6.2.1?

[Andy Heinzer]

I would try to restore this to a 6.2.1 version first instead.   If you can get this restored there and working, then from there you should be able to update the license key for Jira.    Doing it this way will then allow you to create a new XML backup, one with an updated license key.

This way you can more likely avoid this kind of error when upgrading later on.   Provided the XML backup has a license key that still has a future expiration date, then you should be able to update that version.

[Helpdesk Wildwest.in.ua]

yeah, after installing 6.2.1 and importing whole MySQL DB backup everything is running fine. Thx!!