CDD ServiceNow plugin 2.3-12 Connectivity test failures

Products

• Continuous Delivery Director SAAS

Issue/Introduction

New version of ServiceNow plugin 2.3-12 has connectivity issues. 

Local host access logs

 - - [02/Mar/2026:15:29:28 -0500] "POST /cdd-servicenow-plugin/api/connectivity-test/connect HTTP/1.1" 404 815

Failed to execute connectivity test. error was [Got http-error:[404 NOT_FOUND] body:HTTP Status 404 – Not Found

HTTP Status 404 – Not Found

Type: Status Report

Message: The requested resource [/cdd-servicenow-plugin/api/connectivity-test/connect] is not available

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/9.0.109

Environment

ServiceNow plugin version: 2.3-12

Java version: OpenJDK21

Apache Tomcat : 9.0.109

Resolution

Root Cause Analysis
The logs indicate that the on-prem host is running Apache Tomcat/9.0.109.

The current version of our ServiceNow plugin has been migrated to Java 17 / Jakarta EE, which requires Tomcat 10 or later. Here is the technical breakdown:

• Namespace Mismatch: Tomcat 9 uses the legacy javax.* namespace (Java EE). Tomcat 10+ uses the jakarta.* namespace.
• Dependency Conflict: Since the plugin now relies on jakarta.servlet-api 6.0.0 and RESTEasy 6.2.6.Final, the REST servlet cannot initialize on Tomcat 9.
• Observed Behavior:
  • The Plugin Manifest is reachable because it is a static file.
  • API Endpoints (e.g., /api/connectivity-test/connect) return 404 because the servlet fails to register in the incompatible runtime.

Recommended Action
To resolve this, the on-prem host must be upgraded to Tomcat 10.1.x (or newer) to support the Jakarta EE stack.