Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,819
Community Members
 
Community Events
168
Community Groups

Jira doesn´t start

Hi all,

if i start Jira and open the host in the web browser, i can the the plugin initialization. AFter that is finished, i get the follwoing issue.

 

java.lang.RuntimeException: javax.servlet.ServletException: com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: com/atlassian/jira/plugin/webfragment/model/JiraWebLabel

I tried to clean up cache but that didn´t help.

 

Is there someone who can help me out with this problem?

4 answers

1 accepted

0 votes
Answer accepted
Craig Nodwell Community Leader Aug 27, 2022

Hi @Andre Meier as Nic mentioned the error in the logs will go a long way here into someone helping you.

Hi @Craig Nodwell  , @Nic Brough _Adaptavist_ 

The logfile is showing this lines

2022-08-27 11:55:48,787+0200 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 40040 ms.
2022-08-27 11:55:56,335+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-08-27 11:55:56,451+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-08-27 11:55:56,937+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 813000
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.13.0
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 517 milliseconds to process.
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

Hi,

the logfile is showing this:

 


2022-08-27 11:55:48,787+0200 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 40040 ms.
2022-08-27 11:55:56,335+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-08-27 11:55:56,451+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-08-27 11:55:56,937+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 813000
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.13.0
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 517 milliseconds to process.
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests


Hey,

this is what i can see in the log file:

2022-08-27 11:55:48,787+0200 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 40040 ms.
2022-08-27 11:55:56,335+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-08-27 11:55:56,451+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-08-27 11:55:56,937+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 813000
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.13.0
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 517 milliseconds to process.
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

Hi,

sure. This is what i can see in the file:

[c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully

[c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully

[c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

 

 

And this is the error what is written on the web browser.

General error: "java.lang.IllegalStateException: Reading from cache:nio:D:/Programme/Atlassian/Application Data/JIRA/database/h2db.mv.db failed;

 

I didn´t change anything. I had a working instance yesterday and today it doesn´t work.

 

kind regards,

Andre

There's still not enough of the log to be sure, but the mention of h2db is usually a red flag.

h2 is the database behind a demo/test/dev Jira that has been fired up and told to use the internal database for its storage instead of a supported database.

H2 is fine for temporary small systems, but it often fails as you scale, and if there is any fault of any type (including ones as simple as just stopping the system without a proper shutdown) and can randomly fail with no reason at all.

I suspect this has happened to you.

Mhh doesn´t sounds like what i want to hear :-D

 

Is there a way to setup a new system with the old Data? Then transfer to a suppoerted database?

Yes, you can export the system to XML, create a new one hooked up to a supported database, and then import the XML.

The export does need you to have a working system, which you don't, so the next question is do you have a backup?

If you've got an older copy of the database files (it's the content of <jira home>/database) then you can just restore those into place and start Jira, but the best bet is the automatic backup.

In the home directory there should be a directory called backups, an off-the-sheld jira install will have been creating two files a day in there - the latest one of these can be fed to a new install (with a supported database configured) via the "restore from backup" option in the admin section.

Thanks for the detailed answer. So if I have a new instance with supported database, I can restore the H2 data as into the new Database. Is that statement correct or after restore do I have the same H2 database again?

No.  You import XML into your Jira.  It reads it in and puts the data into the database.

Hi all,

the Log-File is showing this:

 

2022-08-27 11:55:48,787+0200 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 40040 ms.
2022-08-27 11:55:56,335+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-08-27 11:55:56,451+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-08-27 11:55:56,937+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 813000
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.13.0
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 517 milliseconds to process.
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

Hi all,

the Logfile is showing this:

2022-08-27 11:55:48,787+0200 Caesium-1-1 INFO [c.a.jira.startup.CacheWarmerLauncher] Warmed cache(s) in 40040 ms.
2022-08-27 11:55:56,335+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Running scheduled upgrades
2022-08-27 11:55:56,451+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2022-08-27 11:55:56,937+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current build number to 813000
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] There are no reindex requests of type [IMMEDIATE, DELAYED] so none will be run
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting current version to 8.13.0
2022-08-27 11:55:56,953+0200 Caesium-1-4 INFO [c.a.j.upgrade.util.BuildNumberDao] Setting downgrade version to 7.1.2
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has finished successfully, and took 517 milliseconds to process.
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] JIRA upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeScheduler] Plugins upgrades completed successfully
2022-08-27 11:55:56,968+0200 Caesium-1-4 INFO [c.a.jira.upgrade.UpgradeIndexManager] Reindexing is not allowed after this upgrade and there is no immediate reindex requests

0 votes

Welcome to the Atlassian Community!

What are the other errors in the logs?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,084 views 18 32
Read article

Atlassian Community Events