JIRA not starting up and 404 shown on JIRA home page

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Symptoms

When trying to start JIRA, only a 404 page is visible in the Web browser.

The following appears in the atlassian-jira.log:

2013-05-20 09:16:57,795 main ERROR [NoModule] Error getting datasource via DBCP: JdbcDatasourceInfo{uri='jdbc:oracle:thin:@example.com:1521:BUGZILLA', driverClassName='oracle.jdbc.OracleDriver', username='jiradbuser', password='********', isolationLevel='null', connectionProperties=null, connectionPoolInfo=ConnectionPoolInfo{maxSize=75, minSize=2, maxWait=60000, sleepTime=300000, lifeTime=600000, deadLockMaxWait=600000, deadLockRetryWait=10000, validationQuery='null', minEvictableTimeMillis=null, timeBetweenEvictionRunsMillis=null}} org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-28001: the password has expired)

Diagnosis

This error is seen when using JIRA with Oracle as the database back-end

Cause

This is caused by an expired password being used by JIRA to connect to Oracle.

Solution

Resolution

  • Create a new password in Oracle for the JIRA user

    • ⚠️ As maintenance of your Oracle database is outside of the scope of Atlassian support, please engage a qualified Oracle DBA for this task

  • Change JIRA to use the new password when connecting to Oracle using one of these methods:

    • Edit the <jira-home>/dbconfig.xml file

    • Run the <jira-install>/bin/config.sh or <jira-install>\bin\config.bat script

Updated on May 22, 2025

Still need help?

The Atlassian Community is here for you.