Questions By Topic
Installation Troubleshooting
Post-Installation Troubleshooting
General Questions
LDAP
JIRA User Integration
Plugin Development
RSS Feeds
Site Backup & Restore
JIRA Issues Macro
Mail Archiving
Troubleshooting Crashes
Installation Troubleshooting
Solutions to common issues with
installing Confluence. Review your logs by opening the Confluence install directory and checking the
/logs/catalina.out and
/logs/catalina.out files for errors described below. Click on a problem to show the solution.
Confluence window closes immediately when started
An error is preventing Confluence from starting.
- Open a command prompt. On Windows, do this by clicking on your Start menu, then click Run. In the Run box, type
cmd and press OK
- From the command prompt, go to your Confluence install directory
- Go into the
bin subdirectory
- Run
startup.bat and read the error message
- Find the solution to that error below
Confluence won't start - java.lang.NoClassDefFoundError IntraHibernateAttachmentCopier
If you are seeing "java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/hibernate/AbstractHibernateAttachmentDao$IntraHibernateAttachmentCopier", you have unzipped Confluence using a program that cannot handle long filenames. You must delete your install directory and go back to the point in the instructions that covers unzipping Confluence using a third-party unzip program.
Confluence won't start - Exception in thread "main" java.lang.NoClassDefFoundError: ...
If http://localhost:8080 goes to an error page when you run Confluence, go to the install directory and find the /logs/catalina.out. If this file contains a single line error starting with "Exception in thread "main" java.lang.NoClassDefFoundError", your install path may contain spaces. The solution is to rename your install directory path so that there are no spaces, then restart Confluence.
Confluence won't start - Error creating Confluence Home directory
The confluence.home variable specified in confluence-init.properties cannot be created. To fix this, edit /confluence/WEB-INF/classes/confluence-init.properties and check the path specified exists. Make sure all the directory slashes use / and that the # has been removed. If you're stuck, try using confluence.home=c:/confluence/data
Confluence won't start - JAVA_HOME environment variable is not defined correctly
You have not installed the Java Development Kit, or not set the %JAVA_HOME% to the directory of the JDK. You should re-check your steps in Stage 2.
Confluence won't start - Port 8080 is in use
If you have another Tomcat running on the same machine, you must edit <INSTALL>/conf/server.xml and change both 8080 and 8005 to ports that do not conflict with your other Tomcat instance according to these instructions.
Confluence won't start - Error creating bean with name 'scheduler'
Confluence won't start - Error registering bean with name 'fileSystemAttachmentDataDao'
If you did not use one of the recommended unzipping tools, and happened to use for instance the default Windows XP extractor, one of the classes required for starting up Confluence may not be located due to the lengthy file-path. This is due to the reason that the default Windows tool silently fails to extract files with long names. We suggest you to use other tools such as WinZIP and 7zip and redo the deployment process.
Cause:
org.springframework.beans.factory.BeanDefinitionStoreException: Error registering bean with name 'fileSystemAttachmentDataDao' defined in class path resource applicationContext.xml: Class that bean class com.atlassian.confluence.pages.persistence.dao.FileSystemAttachmentDataDao depends on not found; nested exception is java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/FileSystemAttachmentDataDao$FileSystemAttachmentNamingStrategy
at org.springframework.beans.factory.xml.DefaultXmlBeanDefinitionParser.parseBeanDefinition(DefaultXmlBeanDefinitionParser.java:366)
caused by: java.lang.NoClassDefFoundError: com/atlassian/confluence/pages/persistence/dao/FileSystemAttachmentDataDao$FileSystemAttachmentNamingStrategy
at java.lang.Class.forName0(Native Method)
Confluence starts but localhost:8080 times out
Check the server logs for errors. If you are running Confluence Standalone on Windows, error messages will be printed to the console window that opened when you ran startup.bat. On Unix systems, Confluence will log messages to logs/catalina.out.
Confluence starts but localhost:8080 goes to Tomcat start homepage
The CATALINA_HOME environment variable is set to another instance of Tomcat. You should run shutdown.sh, remove the CATALINA_HOME reference to the other Tomcat version, and run startup.sh again.
Confluence starts but logins fail at login screen
If you try to login with the correct username and password but are always returned to the login screen without any error messages, and you are running Zone Alarm, please check that it is not blocking the Confluence server
BUILD FAILED message when trying to create an EAR file in Confluence 2.6 or 2.7
When trying to create a EAR file, you may encounter with the following error:
This is due to the build.xml file being incorrect for Confluence 2.6.x and 2.7.0. This problem will be fixed for future releases. However for these releases, please open the build.xml file and change the following two lines:
From:
To:
Re-trigger the setup wizard
To re-run the setup wizard, delete <confluence-home>/confluence.cfg.xml.
Post-Install Troubleshooting
General Questions
Is your question unanswered? Try searching using the Search box in the top right corner of the page. If you can't find your answer, visit Confluence Support and 'Create New Issue' for a support ticket. You may need to sign up for a free account first.
