Applies to: Ephesoft Transact 2020.1.06 and above.
Issue
You may receive an error message for unauthorized or misconfigured AJP connections, such as:
ERROR org.apache.coyote.ajp.AjpMessage- Invalid message received with signature
Root Cause
Updated Tomcat server in this Transact release brings tightened security around AJP protocol usage. An incorrectly configured or unauthorized system with invalid AJP messaging may be sending messages to your Tomcat server.
Solution
If you do not need AJP messaging, disable the AJP protocol in Tomcat. For instructions on this, see How to Disable the AJP Protocol in Tomcat.
Connections to the Tomcat AJP endpoint may need to be reconfigured properly to align with the updated Tomcat AJP specifications. If you are using AJP messaging, ensure your AJP Connector secret is valid with both Tomcat and the front-end web server (Apache, Nginx, IIS). This may require you to upgrade the front-end web server to a version that supports the revised AJP Connector options.
If you are using Apache bundled with Transact, we recommend transitioning to a separate front-end web server that meets your needs or using Tomcat to provide direct access to Transact.
Note: AJP connections are not typically needed for Transact by default. These connections are sometimes used when web servers or load balancers are requirements for integration.
For more information, see Apache Tomcat 8 Configuration Reference: The AJP Connector.
The post AJP Protocol Error – “Invalid Message Received” appeared first on Ephesoft Docs.