Invalid message with signature 18245 is thrown when JIRA applications are behind Apache
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 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):
1
2
3
4
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).
1
2
3
4
ProxyRequests Off
ProxyPass /issues ajp://jiraserver:8009/issues
ProxyPassReverse /issues ajp://jiraserver:8009/issues
Was this helpful?