tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From breako <>
Subject Re: Problem forward HTTP / Soap request using mod_jk
Date Wed, 04 Nov 2009 17:11:46 GMT

You are correct it is a post and it is missing a body.
However, I used a utility tool TCPMon, to sniff what was being sent to the
Apache Http Server.

This does include a body, wrapped in <XML> tags.  I do not know why Apache
Http Server does not forward this to my tomcat server.

The difference between my Tomcat client <--> Tomcat server set up and my
Tomcat client <--> Apache <--> Tomcat server, is that the former
communicates only over HTTP ports. There is no AJP.  The Tomcat client knows
which HTTP port the Tomcat server is running on.

Whereas, in the later, Apache only knows about the AJP port of the Tomcat
Server (which is 23009). It does not know about the HTTP port  on the Tomcat
Server (which is 23080), I wonder does it need to send PUT http requests
with body?

To answer your specific questions:

"When you have your initial setup, where one Tomcat talks to the other 

Question 1. which port do you use on the "server" Tomcat ? 
(can you show the corresponding <Connector> of your Tomcat server.xml file) 

    <Connector acceptCount="100" connectionTimeout="20000"
disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192"
maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="23080"
   <Connector enableLookups="false" port="23009" protocol="AJP/1.3"

Question 2. how does the "client" Tomcat connect to that port and send a
to it ? 

It is implemented as a Axis2 SOAP service. 

Question 3. is that request then pure HTTP ? (even if inside, there is a
SOAP message) 

I am not sure quite what you mean, by pure HTTP.  In both cases the tomcat
client sends out the same
HTTP message. The only difference is the port is being sent to.

The TCPMon sniffs this as:

POST /docy HTTP/1.1
Content-Type: application/soap+xml; charset=UTF-8; action="urn:saveAsWord"
User-Agent: Axis2
Transfer-Encoding: chunked

<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope

Question 4. 
- and later, when you have changed your setup to have the "client 
Tomcat" now talk to the Apache server, instead of to the "server Tomcat" 
directly, are you using the exact same request from the client Tomcat ? 

Answer: Yes.

Question 5. it would probably be useful to 
compare the mod_jk log between these two cases : when you are requesting 
the URL /HelloWorld and when you are requestion /docy (or whatever), and 
look where the difference is. 

Answer: I have done this. The /HelloWorl comes straight from a web browser
and is a GET request. The Mod_JK shows it sent and then a response back.

again thanks for any help and apologies in the lack of clarity in my

I wonder couild this be something do with Apache only knowing about the
tomcat server's AJP port and not it's http port?

View this message in context:
Sent from the Tomcat - User mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message