Invalid message with signature 18245 is thrown when JIRA applications are behind Apache

Still need help?

The Atlassian Community is here for you.

Ask the community

The content on this page relates to platforms which are not supported for JIRA Applications. Consequently, Atlassian 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 applications are configured behind Apache using AJP protocol and the following appears in the application server log files (UNIX$JIRA_INSTALL/logs/catalina.out, or Windows: $JIRA_INSTALL/logs/stdout and stderr):

Nov 26, 2013 12:09:51 PM org.apache.coyote.ajp.AjpMessage processHeader
SEVERE: Invalid message received with signature 18245
Nov 26, 2013 12:09:51 PM org.apache.coyote.ajp.AjpMessage processHeader
SEVERE: Invalid message received with signature 18245

Also, the following appears on the browser screen:

Cause

This error is caused by incorrect Apache configuration. This is usually related to the VirtualHost configuration section in Apache httpd.conf file.

Resolution

Make sure that the following is inside the VirtualHost, replacing jiraserver with the hostname of the JIRA application server and also modifying the context path accordingly (/issues).

ProxyRequests Off

ProxyPass       /issues ajp://jiraserver:8009/issues
ProxyPassReverse    /issues ajp://jiraserver:8009/issues

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.