JBoss Deployment Failure due to 'Resource-ref jdbc JiraDS Found in jboss-web.xml but Not in web.xml'

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

The content on this page relates to platforms which are not supported. Consequently, Atlassian Support cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

Symptoms

Jira Application deployment fails, client requests return HTTP status code 404 Not Found. The following appears in the atlassian-jira.log:

1 2 16:00:10,226 ERROR [MainDeployer] Could not initialise deployment: file:/opt/jboss-4.2.3.GA/server/default/deploy/jira.war/ org.jboss.deployment.DeploymentException: Failed to parse WEB-INF/jboss-web.xml; - nested throwable: (org.jboss.deployment.DeploymentException: resource-ref jdbc/JiraDS found in jboss-web.xml but not in web.xml)

Cause

The JNDI name for the DataSource connection pool has been declared in the container deployment descriptor but there is no matching resource-ref element in the WEb-INF/web.xml.

Resolution

Refer to the following article on How to Configure the Jira DataSource on JBoss. Make sure to check for spelling mistakes.

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.