DSpace 6.3 Tomcat 404 error with JSPUI

[Daniel Henderson]

Hi folks,

I recently inherited a DSpace installation, and we've been having issues with running it inside a Docker container. Additionally we attempted to migrate Dspace to a new Kubernetes cluster.

Currently, we run Dspace 6.3 with the following modules enabled:

• JSPUI
• Swordv2
• SOLR
• OAI-PMH
• REST API

This currently runs without issue on our old Kubernetes cluster (1.12). However, we recently migrated to a new Kubernetes cluster from an existing one, and it has broken something to do with the JSPUI functionality.

On the new cluster (running kubernetes 1.14), Dspace has the following modules enabled. It's still 6.3 and nothing has changed:

• JSPUI - which returns a Tomcat 404 error stating "Not Found" in the Message field when this is run on a new cluster OR locally. JSPUI is on the root domain (ie, localhost:8080)
• Swordv2 - which works (authentication required though)
• OAI-PMH - which works
• Dspace REST API - which works
• Solr - not directly accessible via the browser, but is running in the background and the REST api can communicate with it.

It seems to point to a configuration or permissions issue, but there are no errors being returned in the logs inside the container.   

Tomcat error message for jspui (as it's root):

HTTP Status 404 – Not Found

Type Status Report

Message Not found

Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Apache Tomcat/8.5.41  

The dockerfile used to build the installation has not changed, aside from updating a link to Ant. That dockerfile also deployed successfully to the old cluster.

Any clues as to where to look to troubleshoot this? We have tried:

• Checking deployment settings on the new cluster (every other application we have deployed there has started up with no issue, it's only Dspace having issues)
• Checked the error logs (Tomcat, Catalina and Dspace error logs) - no errors appear in Dspace.log, Tomcat reports 404
• Checked the permissions of the JSPUI folder - it's there, everything's readable by Tomcat.
• Testing a local deployment on another PC - it works there.

Thanks in advance.

[Daniel Henderson]

Hi, just following up on this - any ideas?