You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Yasser <ya...@gmail.com> on 2012/08/06 23:39:56 UTC
AjpNio Invalid message received on header
I am using Tomcat 7.0.29 fronted with Apache 2.2.22 modproxy.
Configured Ajp as the protocol in httpd.conf and AjpNioProtocol in
server.xml.
After the server starts, the logs are filled with the following message:
*Severe: Invalid message received with signature 20599
com.apache.coyote.ajp.AjpMessage processHeader*
There are no requests sent to the web or tomcat server and it still throws
that error at an interval of 20 seconds. Access logs in tomcat and apache
show that no request is coming in. What is causing the invalid message
error ?
Here is the configuration :
httpd.conf
ProxyPass /wl http:// ip : port /wl
ProxyPassReverse /wl http:// ip : port /wl
server.xml
<Connector port="port" protocol="org.apache.coyote.ajp.AjpNioProtocol"
connectionTimeout="20000" acceptorThreadCount="2" maxThreads="600"
redirectPort="8443" />
Re: AjpNio Invalid message received on header
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yasser,
On 8/7/12 12:35 PM, Yasser wrote:
> Sniffer on the network didn't find anything talking to the ajp
> port, but there was traffic within the app server box. I changed
> the port number and that got rid of the error. I will have to do
> some cleanup on the box.
>
> Thanks for your help Rainer.
It sounds like you have something connecting to that port that
shouldn't be. Maybe another misconfigured service?
It should be fairly easy to locate the offending process using
tcpdump, et.
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAlAhRiAACgkQ9CaO5/Lv0PBaRgCeMty8tpWgZS4zZzN4eqJwXB/g
86EAoLY2+nW1uwdOOzPlWOfvjKkriPIR
=v/uI
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: AjpNio Invalid message received on header
Posted by Yasser <ya...@gmail.com>.
Sniffer on the network didn't find anything talking to the ajp port, but
there was traffic within the app server box. I changed the port number and
that got rid of the error. I will have to do some cleanup on the box.
Thanks for your help Rainer.
On Mon, Aug 6, 2012 at 6:05 PM, Rainer Jung <ra...@kippdata.de> wrote:
> On 06.08.2012 23:39, Yasser wrote:
>
>> I am using Tomcat 7.0.29 fronted with Apache 2.2.22 modproxy.
>> Configured Ajp as the protocol in httpd.conf and AjpNioProtocol in
>> server.xml.
>> After the server starts, the logs are filled with the following message:
>> *Severe: Invalid message received with signature 20599
>> com.apache.coyote.ajp.**AjpMessage processHeader*
>>
>
> It could be anything trying to talk to your AJP port. 20599 should mean,
> that the first two bytes of the package are P (=80) and w (=119), because
> 80*256 + 119 = 20599.
>
> It seem syou need to sniff your AJP port and see, from which system the
> packets come. You could also check
>
> netstat -an
>
> for connections to your AJP port and check whether there are connections
> coming from some unexpected system. Sniffing would be more reliable though.
>
>
> There are no requests sent to the web or tomcat server and it still throws
>> that error at an interval of 20 seconds. Access logs in tomcat and apache
>> show that no request is coming in. What is causing the invalid message
>> error ?
>>
>
> If even the first packet doesn't make sense, then there will be no access
> log entry.
>
>
> Here is the configuration :
>> httpd.conf
>> ProxyPass /wl http:// ip : port /wl
>> ProxyPassReverse /wl http:// ip : port /wl
>>
>> server.xml
>> <Connector port="port" protocol="org.apache.coyote.**ajp.AjpNioProtocol"
>> connectionTimeout="20000" acceptorThreadCount="2" maxThreads="600"
>> redirectPort="8443" />
>>
>
> Regards,
>
> Rainer
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.**apache.org<us...@tomcat.apache.org>
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: AjpNio Invalid message received on header
Posted by Rainer Jung <ra...@kippdata.de>.
On 06.08.2012 23:39, Yasser wrote:
> I am using Tomcat 7.0.29 fronted with Apache 2.2.22 modproxy.
> Configured Ajp as the protocol in httpd.conf and AjpNioProtocol in
> server.xml.
> After the server starts, the logs are filled with the following message:
> *Severe: Invalid message received with signature 20599
> com.apache.coyote.ajp.AjpMessage processHeader*
It could be anything trying to talk to your AJP port. 20599 should mean,
that the first two bytes of the package are P (=80) and w (=119),
because 80*256 + 119 = 20599.
It seem syou need to sniff your AJP port and see, from which system the
packets come. You could also check
netstat -an
for connections to your AJP port and check whether there are connections
coming from some unexpected system. Sniffing would be more reliable though.
> There are no requests sent to the web or tomcat server and it still throws
> that error at an interval of 20 seconds. Access logs in tomcat and apache
> show that no request is coming in. What is causing the invalid message
> error ?
If even the first packet doesn't make sense, then there will be no
access log entry.
> Here is the configuration :
> httpd.conf
> ProxyPass /wl http:// ip : port /wl
> ProxyPassReverse /wl http:// ip : port /wl
>
> server.xml
> <Connector port="port" protocol="org.apache.coyote.ajp.AjpNioProtocol"
> connectionTimeout="20000" acceptorThreadCount="2" maxThreads="600"
> redirectPort="8443" />
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org