Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

JIRA cannot start due to a java.lang.NoClassDefFoundError: com/atlassian/jira/index/ha/ReplicatedIndexManager

Francesco R
Francesco R
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
November 21, 2013

Hello, I, experiencing this error that prevent JIRA to start. I really don't remember what I did to have it.

Maybe I just swithed from a database to another to test different projects with the same version of jira.

I'm running JIRA version = 6.1.3, Java Version = 1.7.0_25

I get:
2013-11-22 17:31:02,203 localhost-startStop-1 FATAL [atlassian.jira.startup.ComponentContainerLauncher] An Error occurred during ComponentContainerLauncher servlet context initialisation - com/atlassian/jira/index/ha/ReplicatedIndexManager.
java.lang.NoClassDefFoundError: com/atlassian/jira/index/ha/ReplicatedIndexManager
at com.atlassian.jira.ContainerRegistrar.registerComponents(ContainerRegistrar.java:1946)
at com.atlassian.jira.ComponentManager.registerComponents(ComponentManager.java:407)
at com.atlassian.jira.ComponentManager.initialise(ComponentManager.java:185)
at com.atlassian.jira.startup.ComponentContainerLauncher.populateFullPicoContainer(ComponentContainerLauncher.java:57)
at com.atlassian.jira.startup.ComponentContainerLauncher.start(ComponentContainerLauncher.java:29)
at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:122)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:315)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:209)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:114)
at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:30)
at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:77)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:34)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:72)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54) <+5> (StandardContext.java:4791) (StandardContext.java:5285) (LifecycleBase.java:150) (ContainerBase.java:1559) (ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: com.atlassian.jira.index.ha.ReplicatedIndexManager
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1711)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1556)
... 24 more
2013-11-22 17:31:02,206 localhost-startStop-1 ERROR [atlassian.jira.startup.LauncherContextListener] Unable to start JIRA due to Java Error.
java.lang.NoClassDefFoundError: com/atlassian/jira/index/ha/ReplicatedIndexManager
at com.atlassian.jira.ContainerRegistrar.registerComponents(ContainerRegistrar.java:1946)
at com.atlassian.jira.ComponentManager.registerComponents(ComponentManager.java:407)
at com.atlassian.jira.ComponentManager.initialise(ComponentManager.java:185)
at com.atlassian.jira.startup.ComponentContainerLauncher.populateFullPicoContainer(ComponentContainerLauncher.java:57)
at com.atlassian.jira.startup.ComponentContainerLauncher.start(ComponentContainerLauncher.java:29)
at com.atlassian.jira.startup.DefaultJiraLauncher$3.run(DefaultJiraLauncher.java:122)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:315)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:209)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:114)
at com.atlassian.jira.startup.DefaultJiraLauncher.access$100(DefaultJiraLauncher.java:30)
at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:77)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:34)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:72)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54) <+5> (StandardContext.java:4791) (StandardContext.java:5285) (LifecycleBase.java:150) (ContainerBase.java:1559) (ContainerBase.java:1549)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: com.atlassian.jira.index.ha.ReplicatedIndexManager
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1711)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1556)
... 24 more
2013-11-22 17:31:02,218 localhost-startStop-1 INFO [atlassian.jira.startup.DefaultJiraLauncher] Stopping launchers
Any suggestion ? Thank you in advance
Answer
Watch
Like Be the first to like this
604 views

1 answer

0 votes
Giuliano C_
Giuliano C_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 5, 2014

Hey Francesco,

While I was researching for the resolution for cases like this one, we are still not able to find it. Given that, would you mind to share what have you performed in order to have it fixed, so we can help other users to avoid this?

Was it caused by the database connection parameters after the change of the instance?

Any feedback would be awesome!

View More Comments
Francesco R
Francesco R
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
August 20, 2014

Hello Giuliano,
sincerely I don't remember which was our workaround. Probably we used the Jira builtin restore feature (the one that uses the zip files) starting from an empty database or we deleted the indexes' directory. I'm sorry I can't help you furtherly

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira Software
TAGS
AUG Leaders

Atlassian Community Events

    See all events