https://issues.apache.org/bugzilla/show_bug.cgi?id=48400

           Summary: HTTP Post Request is set to recoverable on timeout
                    waiting for response from tomcat
           Product: Tomcat Connectors
           Version: 1.2.28
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_jk
        AssignedTo: dev@tomcat.apache.org
        ReportedBy: discoversud...@gmail.com


mod_jk retries http post requests in case of timeout in getting response from
tomcat with default configurations(no retries or recovery_options specified).

AFAIK HTTP Get and Head requests are only considered idempotent, shouldn't post
requests be non-recoverable ?

We are using apache <--> mod_jk-1.2.28 <--AJP13--> tomcat
We also are using DisableReuse flag in mod_jk config

I understand this can be fixed with disabling the recovery option.

Wondering if its a default config issue or a bug in mod_jk.
If it is intentional can someone please explain the intention ?

mod_jk logs :
----------------------------
[Tue Dec 15 05:53:50 2009] [13935:0] [debug] init_ws_service::mod_jk.c (935):
Service protocol=HTTP/1.1 method=POST
ssl=true host=(null) addr=XXXXXXXX name=XXXXXXXXX port=XXXX auth=(null)
user=(null) laddr=XXXXXXXX raddr=XXXXXXXX uri=/XXXXXXXXXXXX-MASKING--XXXX

[Tue Dec 15 05:53:50 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(541): timeout 120 set for socket=43
[Tue Dec 15 05:53:50 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(576): trying to connect socket 43 to
127.0.0.1:8009
[Tue Dec 15 05:53:50 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(602): socket 43 connected to 127.0.0.1:8009
[Tue Dec 15 05:53:50 2009] [13935:0] [debug]
ajp_connection_tcp_send_message::jk_ajp_common.c (1070): sending to ajp13
pos=4 len=2495 max=8192


After 2 mins ........


[Tue Dec 15 05:55:50 2009] [13935:0] [debug] jk_shutdown_socket::jk_connect.c
(681): About to shutdown socket 43
[Tue Dec 15 05:55:52 2009] [13935:0] [debug] jk_shutdown_socket::jk_connect.c
(732): Shutdown socket 43 and read 0
lingering bytes
[Tue Dec 15 05:55:52 2009] [13935:0] [info]
ajp_connection_tcp_get_message::jk_ajp_common.c (1150): (consWorker) can't
receive the response header message from tomcat, network problems or tomcat
(127.0.0.1:8009) is down (errno=11)
[Tue Dec 15 05:55:52 2009] [13935:0] [error] ajp_get_reply::jk_ajp_common.c
(1962): (consWorker) Tomcat is down or
refused connection. No response has been sent to the client (yet)
[Tue Dec 15 05:55:52 2009] [13935:0] [info] ajp_service::jk_ajp_common.c
(2447): (consWorker) sending request to tomcat
failed (recoverable),  (attempt=1)
[Tue Dec 15 05:55:52 2009] [13935:0] [debug] ajp_service::jk_ajp_common.c
(2304): retry 1, sleeping for 100 ms before
retrying
[Tue Dec 15 05:55:53 2009] [13935:0] [debug] ajp_send_request::jk_ajp_common.c
(1501): (consWorker) all endpoints are
disconnected.
[Tue Dec 15 05:55:53 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(452): socket TCP_NODELAY set to On
[Tue Dec 15 05:55:53 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(541): timeout 120 set for socket=43
[Tue Dec 15 05:55:53 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(576): trying to connect socket 43 to
127.0.0.1:8009
[Tue Dec 15 05:55:53 2009] [13935:0] [debug] jk_open_socket::jk_connect.c
(602): socket 43 connected to 127.0.0.1:8009
[Tue Dec 15 05:55:53 2009] [13935:0] [debug]
ajp_connect_to_endpoint::jk_ajp_common.c (931): Connected socket 43 to
(127.0.0.1:8009)
[Tue Dec 15 05:55:53 2009] [13935:0] [debug]
ajp_connection_tcp_send_message::jk_ajp_common.c (1070): sending to ajp13
pos=4 len=2495 max=8192
----------------------------

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org

Reply via email to