top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Tomcat: Invalid message received with signature

+2 votes
8,555 views

While doing some testing out of the blue seeing a string of SEVERE messages in catalina.out. Apache is not running and in fact has been uninstalled. The proxyPort directive has been removed from the Tomcat server.xml connector config, and Tomcat has been rebooted. I was using http not ajp.

connectionTimeout="20000"
redirectPort="8445"
org.apache.coyote.ajp.AjpMessage processHeader
SEVERE: Invalid message received with signature xxxx

Any pointer?

posted Dec 5, 2013 by Meenal Mishra

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+2 votes

It would seem that you still have an AJP configured in the server.xml that's actually being used. First, make sure your Tomcat is using the server.xml you're editing (e.g., don't run it under an IDE). If that doesn't resolve the issue, post your entire server.xml here, minus comments and with sensitive fields obfuscated. Also look in all of the Tomcat logs for startup information about the various connectors and listeners that are active.

answer Dec 5, 2013 by Bob Wise
Similar Questions
+1 vote

I am facing an invalid jar index exception in both tomcat 5.5.x and 7.0.39 . After some investigation , we figured out this is because of class loading in tomcat which uses index.list file in jar files. I have two jars with same package names but classes in those package are different. Since the package name are defined or mentioned in the index.list file of every jar for some reason tomcat is showing me an invalid jar index exception even if try to load a simple index.jsp.

0 votes

I am using Tomcat version 7.0.63.
I have registered the dbconnection pool with MBeanServer.
Is there a way to make those methods hot setting? What I mean by this is, for example if I change statement cache size in the jconsole, it should take effect immediately.

Any help is greatly appreciated.

+1 vote

I have a recurring issue, that tomcat caches my jsf webapp pages in a strange manner. Sometimes for multiple days/hours, one
or two explicit pages or the whole webapp is loading very slowly.

My setup is a locally used tomcat 8.0.28 for debugging in Eclipse and a local database. The behavior persists also after browser cache clearing and with different browsers.

Does anyone else have seen this behavior before? Do i miss a specific parameter?

+1 vote

I know Tomcat 5.5 is very old and this is outdated, but we are still using Tomcat 5.5 and we got an issue. Please help.

Problem description:

Recently my client has asked me to add two new clusters in the production, after adding the clusters we found that these two new clusters are not able to handle special characters.

When user copies some data (especially from MS-Word which contains double quote) and paste into the application we have found that double quote becomes junk character, but these problems only persist with newly created clusters not with old clusters.

While creating the new cluster I just copied the old cluster folder and all the clusters are identical except some changes in server.xml.

Could you please help me to resolve this issue?

+2 votes

I have a domain domain.com that points to a server. Now I have a subdomain sub.domain.com that points to another server that has Apache running and Tomcat. I want this subdomain to point to a application deployed on the Tomcat instance through ajp.

I have configured the following in httpd.conf:

   ServerName sub.domain.com 
   ProxyRequests Off
   ProxyPreserveHost On  
   Order deny,allow Allow from all  
   ProxyPass / ajp://localhost:8009/ 
   ProxyPassReverse / ajp://localhost:8009/   

and in Tomcats server.xml:

But when I go to sub.domain.com the url changes to otherdomain.com and shows me a php website running in Apache and declared as following in httpd.conf:

 DocumentRoot /var/www/html/otherdomain.com 
 ServerName otherdomain.com 
 ServerAlias www.otherdomain.com 

I only get it to work when I change the port in the sub.domain.com virtual host declaration to for example 8001. Then when I go to sub.domain.com:8001 it shows my tomcat application (ROOT.war) as expected.

So my question is: what could be going wrong that it doesn't work with the default port 80? I can't find any configuration that is causing this, but I'm probably missing something or is my virtual host configuration wrong?

...