Install

Configure

Use

FAQ

	About Index Installing JIRA Requirements Install Guide Setup Wizard JIRA Standalone Using external databases JIRA Webapp Configuring database storage Server-specific Guides Server Comparison Orion JBoss 2.4 JBoss 3.0 Tomcat 4.0.x Tomcat 4.1.x Caucho Resin Jetty Weblogic Other servers Concepts Issues Projects Versions Components Configuration Configuring JIRA Look and Feel Email Notifications Permissions Issue Management Defining New Resolutions Defining New Priorities Configuring File Attachments Adding Custom Fields Issue Linking Configure Time Tracking Issue Level Security What is Issue Level Security Issue Security Schemes Issue Security Levels Setting the Security on an Issue Project Management Version Management Configuring project admins Email Notifications Creating a Notification Scheme Customising email content Extensibility & Integration Setting up CVS Emails Setting up Comment Emails Issue Creation from Email Operational Tasks Indexing & Search Backup Data to XML Restoring Data from XML Upgrading JIRA safely Splitting a JIRA instance Automating JIRA backups Reference Guides Configuring the Dashboard Time Tracking Linking two issues Navigator Views Searching & Filtering Search & Issue Filters Search Query Syntax Developer Help Debugging Errors Database Indexing Performance Tips JIRA Source Building JIRA from source Extending JIRA Extension Overview Listeners Services Configurable Objects API Documentation Miscellaneous FAQ Printable docs JIRA PDF manual (1.2Mb)

Debugging Errors

PDF

If you encounter any errors using or setting up JIRA, please report them to the mailing list or file a bug. We'll fix them as soon as possible.

To help us fix the error, we often need more information than just "this feature doesn't work". Often an error message is reported on the console or via log4j. If you could include the error message in your email or bug report, it would be most appreciated!

From 1.2, JIRA ships with a log4j.properties file that has the default logging levels specified. You can find this file in WEB-INF/classes/log4j.properties.

To get detailed error message or stack traces, you may need to setup log4j to display detailed error messages. Edit the log4j.properties file and follow the instructions to increase the verbosity of logging.

Alteratively, if you application server itself configures logging (JBoss), you may need to remove the log4j.properties file. On some servers (JBoss 3.0), you may also need to remove the entire log4j.jar file to get logging to work.