Wow, I was lucky there was a binary version of mod_jk for my httpd version.
Here is the new log output. I can send it to you directly as attachment if you like. I think it would improve readability. In the meantime I'll see what I can do with tcpdump. Cheers, Pete map_uri_to_worker::jk_uri_worker_map.c (513): Attempting to map URI '/axis2/services/binarytest' from 23 maps map_uri_to_worker::jk_uri_worker_map.c (525): Attempting to map context URI '/probe/*' map_uri_to_worker::jk_uri_worker_map.c (525): Attempting to map context URI '/axis2/*' map_uri_to_worker::jk_uri_worker_map.c (539): Found a wildchar match worker2 -> /axis2/* jk_handler::mod_jk.c (1920): Into handler jakarta-servlet worker=worker2 r->proxyreq=0 wc_get_worker_for_name::jk_worker.c (111): found a worker worker2 wc_maintain::jk_worker.c (318): Maintaining worker worker1 ajp_maintain::jk_ajp_common.c (2324): reached pool min size 0 from 10 cache slots ajp_maintain::jk_ajp_common.c (2332): recycled 0 sockets in 0 seconds from 10 pool slots wc_maintain::jk_worker.c (318): Maintaining worker worker2 wc_get_name_for_type::jk_worker.c (287): Found worker type 'ajp13' init_ws_service::mod_jk.c (568): Service protocol=HTTP/1.1 method=POST host=(null) addr=192.168.200.188 name=192.168.200.194 port=8080 auth=(null) user=(null) laddr=213.157.4.28 raddr=192.168.200.188 ajp_get_endpoint::jk_ajp_common.c (2251): acquired connection pool slot=0 ajp_marshal_into_msgb::jk_ajp_common.c (547): ajp marshaling done ajp_service::jk_ajp_common.c (1734): processing worker2 with 5 retries jk_open_socket::jk_connect.c (334): socket TCP_NODELAY set to On jk_open_socket::jk_connect.c (347): socket SO_KEEPALIVE set to On jk_open_socket::jk_connect.c (432): trying to connect socket 12 to 192.168.200.194:8009 jk_open_socket::jk_connect.c (458): socket 12 connected to 192.168.200.194:8009 ajp_connect_to_endpoint::jk_ajp_common.c (846): Connected socket 12 to (192.168.200.194:8009) ajp_connection_tcp_send_message::jk_ajp_common.c (892): sending to ajp13 pos=4 len=446 max=8192 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0000 12 34 01 BA 02 04 00 08 48 54 54 50 2F 31 2E 31 - .4......HTTP/1.1 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0010 00 00 1A 2F 61 78 69 73 32 2F 73 65 72 76 69 63 - .../axis2/servic ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0020 65 73 2F 62 69 6E 61 72 79 74 65 73 74 00 00 0F - es/binarytest... ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0030 31 39 32 2E 31 36 38 2E 32 30 30 2E 31 38 38 00 - 192.168.200.188. ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0040 FF FF 00 0F 31 39 32 2E 31 36 38 2E 32 30 30 2E - ....192.168.200. ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0050 31 39 34 00 1F 90 00 00 06 00 0A 53 4F 41 50 41 - 194........SOAPA ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0060 63 74 69 6F 6E 00 00 19 22 75 72 6E 3A 61 78 77 - ction..."urn:axw ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0070 73 2E 62 69 6E 61 72 79 2F 67 65 74 46 69 6C 65 - s.binary/getFile ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0080 22 00 A0 0E 00 05 41 78 69 73 32 00 A0 0B 00 14 - ".....Axis2..... ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0090 31 39 32 2E 31 36 38 2E 32 30 30 2E 31 39 34 3A - 192.168.200.194: ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00a0 38 30 38 30 00 00 10 50 72 6F 78 79 2D 43 6F 6E - 8080...Proxy-Con ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00b0 6E 65 63 74 69 6F 6E 00 00 0A 4B 65 65 70 2D 41 - nection...Keep-A ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00c0 6C 69 76 65 00 00 11 54 72 61 6E 73 66 65 72 2D - live...Transfer- ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00d0 45 6E 63 6F 64 69 6E 67 00 00 07 63 68 75 6E 6B - Encoding...chunk ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00e0 65 64 00 A0 07 00 D5 6D 75 6C 74 69 70 61 72 74 - ed.....multipart ajp_connection_tcp_send_message::jk_ajp_common.c (892): 00f0 2F 72 65 6C 61 74 65 64 3B 20 62 6F 75 6E 64 61 - /related;.bounda ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0100 72 79 3D 4D 49 4D 45 42 6F 75 6E 64 61 72 79 75 - ry=MIMEBoundaryu ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0110 72 6E 5F 75 75 69 64 5F 41 45 37 38 33 39 35 38 - rn_uuid_AE783958 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0120 35 38 43 32 41 41 35 43 42 46 31 31 36 35 35 37 - 58C2AA5CBF116557 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0130 30 31 38 32 39 38 34 31 3B 20 74 79 70 65 3D 22 - 01829841;.type=" ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0140 61 70 70 6C 69 63 61 74 69 6F 6E 2F 78 6F 70 2B - application/xop+ ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0150 78 6D 6C 22 3B 20 73 74 61 72 74 3D 22 3C 30 2E - xml";.start="<0. ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0160 75 72 6E 3A 75 75 69 64 3A 41 45 37 38 33 39 35 - urn:uuid:AE78395 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0170 38 35 38 43 32 41 41 35 43 42 46 31 31 36 35 35 - 858C2AA5CBF11655 ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0180 37 30 31 38 32 39 38 34 32 40 61 70 61 63 68 65 - [EMAIL PROTECTED] ajp_connection_tcp_send_message::jk_ajp_common.c (892): 0190 2E 6F 72 67 3E 22 3B 20 73 74 61 72 74 2D 69 6E - .org>";.start-in ajp_connection_tcp_send_message::jk_ajp_common.c (892): 01a0 66 6F 3D 22 74 65 78 74 2F 78 6D 6C 22 3B 20 63 - fo="text/xml";.c ajp_connection_tcp_send_message::jk_ajp_common.c (892): 01b0 68 61 72 73 65 74 3D 55 54 46 2D 38 00 FF 00 00 - harset=UTF-8.... ajp_send_request::jk_ajp_common.c (1261): request body to send 0 - request body to resend 0 ajp_connection_tcp_get_message::jk_ajp_common.c (1028): received from ajp13 pos=0 len=3 max=8192 ajp_connection_tcp_get_message::jk_ajp_common.c (1028): 0000 06 1F FA 00 00 00 00 00 00 00 00 00 00 00 00 00 - ................ > -----Ursprüngliche Nachricht----- > Von: Rainer Jung [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 8. Dezember 2006 10:24 > An: Tomcat Users List > Betreff: Re: AW: Web Service Request not passing through Mod_Jk > > Under Linux you can use tcpdump to sniff network packets. > > It looks like your mod_jk is pretty old? The log messages don't fit to > newer versions. We improved logging and overall maintainability in the > meantime. Please switch to 1.2.19 to make debugging easier. > > Regards, > > Rainer > > Peter Neu schrieb: > > Hi, > > > > the problem is that a web service request coming from external client > > fails with a timeout exception while the same client on the proxy host > > works. > > I only see the java.net.SocketTimeout exception in my java stack trace. > My > > assumption is that the tomcat server does receive nothing at all because > I > > write some log messages to the Catalina.out when the axis service gets > > called. > > > > Please tell what kind of network sniffer you would propose. OS running > > below the tomcat server is SUSE ES 9. > > > > Below you find the full log information. > > > > Cheers, > > Pete > > > > [jk_uri_worker_map.c (486)]: Into jk_uri_worker_map_t::map_uri_to_worker > > [jk_uri_worker_map.c (500)]: Attempting to map URI > > '/axis2/services/binarytest' > > [jk_uri_worker_map.c (524)]: jk_uri_worker_map_t::map_uri_to_worker, > Found a > > context match worker2 -> /axis2/ > > [mod_jk.c (1717)]: Into handler r->proxyreq=0 r->handler=jakarta-servlet > > r->notes=137092600 worker=worker2 > > [jk_worker.c (132)]: Into wc_get_worker_for_name worker2 > > [jk_worker.c (136)]: wc_get_worker_for_name, done found a worker > > [mod_jk.c (505)]: agsp=8080 agsn=192.168.200.194 hostn=192.168.200.194 > > shostn=daten.ktbl.de cbsport=0 sport=0 > > [jk_ajp_common.c (1693)]: Into jk_worker_t::get_endpoint > > [jk_ajp_common.c (1737)]: In jk_endpoint_t::ajp_get_endpoint, time > elapsed > > since last request = 93 seconds > > [jk_ajp_common.c (1326)]: Into jk_endpoint_t::service > > [jk_ajp_common.c (298)]: Into ajp_marshal_into_msgb > > [jk_ajp_common.c (466)]: ajp_marshal_into_msgb - Done > > [jk_ajp_common.c (777)]: sending to ajp13 #446 > > [jk_ajp_common.c (1071)]: ajp_send_request 2: request body to send 0 - > > request body to resend 0 > > [jk_ajp_common.c (888)]: received from ajp13 #3 > > [jk_uri_worker_map.c (486)]: Into jk_uri_worker_map_t::map_uri_to_worker > > // end here -- already the next request > > [jk_uri_worker_map.c (500)]: Attempting to map URI > > '/energy/style/styleguide.css' > > > >> -----Ursprüngliche Nachricht----- > >> Von: Rainer Jung [mailto:[EMAIL PROTECTED] > >> Gesendet: Freitag, 8. Dezember 2006 09:47 > >> An: Tomcat Users List > >> Betreff: Re: Web Service Request not passing through Mod_Jk > >> > >> Hello, > >> > >> Peter Neu schrieb: > >>> Hello, > >>> > >>> I have a strange problem with mod_jk. Until now I never had trouble > with > >>> mod_jk but lately I need to pass web service requests through to an > Axis > >>> server running on tomcat (5.5.9). > >> So what's the problem? There is no line in your post, telling us what > >> the real problem is. It sounds like the forwarded requests do not reach > >> tomcat? > >> > >> - What response do you get from apache? > >> - How does the mod_jk log proceed? Your copy&paste stopps, where it > >> starts to get interesting > >> - Can you see correspoding network traffic on the tomcat side, using a > >> network sniffer? > >> > >> Regards, > >> > >> Rainer > >> > >>> The strange thing is the pass-through works if the web service client > >>> resides on the same machine as apache httpd. > >>> But this is not a real use case. ;o) > >>> > >>> My first thought was this must be the firewall. But I opened all > >> possible > >>> ports on the firewall and still got the same result. Besides this > >> shouldn't > >>> be of any concern since axis uses the same http ports and it should be > >> no > >>> difference if the request comes from a browser or a web service client > >> using > >>> common http client. > >>> > >>> Error message I get are the usual java.net.SocketTimeout Exceptions. > In > >> the > >>> access.log of apache httpd I can see all requests coming either from > >>> localhost or the external client so no firewall problem possible. I > set > >>> mod_jk log level to debug and see it's passing everything through even > >> the > >>> request from the external client. > >>> > >>> I already asked at axis & httpd mailings list. Nobody knew how to > solve > >>> this. > >>> > >>> Cheers, > >>> Pete > >>> > >>> Attempting to map URI '/axis2/services/binarytest' > >>> [jk_uri_worker_map.c (524)]: jk_uri_worker_map_t::map_uri_to_worker, > >> Found a > >>> context match worker2 -> /axis2/ > >>> [mod_jk.c (1717)]: Into handler r->proxyreq=0 r->handler=jakarta- > servlet > >>> r->notes=136973856 worker=worker2 > >>> jk_worker.c (132)]: Into wc_get_worker_for_name worker2 > >>> [jk_worker.c (136)]: wc_get_worker_for_name, done found a worker > >>> [mod_jk.c (505)]: agsp=8080 agsn=192.168.200.194 hostn=192.168.200.194 > >>> shostn=my.proxy.de cbsport=0 sport=0 > >>> [jk_ajp_common.c (1693)]: Into jk_worker_t::get_endpoint > >>> [jk_ajp_common.c (1737)]: In jk_endpoint_t::ajp_get_endpoint, time > >> elapsed > >>> since last request = 10 seconds > >>> [jk_ajp_common.c (1326)]: Into jk_endpoint_t::service > >>> [jk_ajp_common.c (298)]: Into ajp_marshal_into_msgb > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To start a new topic, e-mail: users@tomcat.apache.org > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >> --------------------------------------------------------------------- > >> To start a new topic, e-mail: users@tomcat.apache.org > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To start a new topic, e-mail: users@tomcat.apache.org > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To start a new topic, e-mail: users@tomcat.apache.org > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
