eurotrans-Verlag wrote:
However, when I switch to AJP BIO, it seems that the errors go away.
Although I now switched to AJP-BIO (by deleting/renaming tcnative-1.dll),
today morning I got an error again in the ISAPI log:
[Tue Jul 12 06:04:49.812 2011] [4124:2444] [error]
ajp_connection_tcp_get_message::jk_ajp_common.c (1296): wrong message format
0xdaed from 127.0.0.1:8019
[Tue Jul 12 06:04:49.825 2011] [4124:2444] [error]
ajp_get_reply::jk_ajp_common.c (2148): (worker1) Tomcat is down or network
problems. Part of the response has already been sent to the client
This is how the AJP connector is configured in Tomcat:
<Connector port="8019" protocol="AJP/1.3" redirectPort="8743"
URIEncoding="UTF-8" maxThreads="1024" />
Any idea what could cause this errors?
I don't know it that matters, but with one webapp, I'm using COM4J to access
COM objects on the Windows system (but I want to get rid of it in the
future).
Can you take a part of this setup out of the equation ?
For example, at the moment you have
browser <-> IIS <-> isapi_redir. <-> AJP Connector:8019 <-> Tomcat+webapp
Could you eliminate the IIS + Isapi_redir part, having Tomcat listen on port 80/HTTP, like
this :
browser <-> HTTP Connector:80 <-> Tomcat+webapp
?
or like this, by using Apache httpd instead of IIS :
browser <-> Apache <-> mod_jk <-> AJP Connector:8019 <-> Tomcat+webapp
This may help pinpointing where the problem is, since you mentioned earlier that you can
reproduce the problem by pressing F5 in Firefox.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
