You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/06/22 11:39:30 UTC

DO NOT REPLY [Bug 35461] New: - bad request http 400 using mod_jk 1.2.13. After downgrading to 1.3.33 and mod_jk 1.2.5 the problems have gone. Problems occur again after using the combination Apache Webserver 1.3.33 and mod_jk 1.2.10

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=35461>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=35461

           Summary: bad request http 400 using mod_jk 1.2.13. After
                    downgrading to 1.3.33 and mod_jk 1.2.5 the problems have
                    gone. Problems occur again after using the combination
                    Apache Webserver 1.3.33 and mod_jk 1.2.10
           Product: Apache httpd-2.0
           Version: 2.0.54
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: Other Modules
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: joerg.cebulla@bertelsmann.de


We were running Apache 2.0.54 which forwards requests to tomcat
5.0.28 server using mod_jk/ajp13 and its loadbalancing features.

Running this combination we were getting a lot of http status 400 error 
messages in our webservers access logs. The errors are not deterministic. They 
are not caused by calling a special url but are caused by many different calls.

Here is an example:

[21/Jun/2005:11:49:14 +0200] "GET /content/abo_formular_agb_content.jsp 
HTTP/1.0" 400 
16376 "http://www.premiere.de/content/abo_formular_agb_popup.jsp" "Mozilla/4.0 
(compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)"

Monitoring the logfile of the mod_jk you can see the following error messages:

 [info]  service::jk_lb_worker.c (642): unrecoverable error 400, request 
failed. Client failed in the middle of request, we can't recover to another 
instance.

After getting the bad request the tomcat server produces a rather long stack 
trace. Here is an example:

2005 12:02:55 org.apache.jk.common.HandlerRequest invoke
SCHWERWIEGEND: Error decoding request
java.net.SocketTimeoutException: Read timed out
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:313)
        at org.apache.jk.common.ChannelSocket.read(ChannelSocket.java:598)
        at org.apache.jk.common.ChannelSocket.receive(ChannelSocket.java:535)
        at org.apache.jk.common.JkInputStream.receive(JkInputStream.java:247)
        at org.apache.jk.common.HandlerRequest.decodeRequest
(HandlerRequest.java:500)
        at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:352)
        at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:743)
        at org.apache.jk.common.ChannelSocket.processConnection
(ChannelSocket.java:675)
        at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:866)
        at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run
(ThreadPool.java:683)
        at java.lang.Thread.run(Thread.java:595)
12 34 03 53 02 04 00 08 48 54 54 50 2f 31 2e 31  | .4.S....HTTP/1.1
00 00 2b 2f 63 6f 6d 6d 6f 6e 2f 63 75 73 74 6f  | ..+/common/custom
6d 65 72 2f 62 6f 75 6e 64 61 72 79 2f 6c 6f 67  | mer/boundary/log
69 6e 5a 69 70 63 6f 64 65 52 48 2e 64 6f 00 00  | inZipcodeRH.do..
0d 31 39 35 2e 39 33 2e 36 30 2e 31 30 35 00 ff  | .195.93.60.105.?
ff 00 0f 77 77 77 2e 70 72 65 6d 69 65 72 65 2e  | ?..www.premiere.
64 65 00 00 50 00 00 0d 00 0d 43 61 63 68 65 2d  | de..P.....Cache-
43 6f 6e 74 72 6f 6c 00 00 08 6e 6f 2d 63 61 63  | Control...no-cac
68 65 00 00 03 56 69 61 00 00 6d 48 54 54 50 2f  | he...Via..mHTTP/
31 2e 31 20 28 56 65 6c 6f 63 69 74 79 2f 31 2e  | 1.1 (Velocity/1.
31 2e 31 20 5b 75 53 63 4d 73 20 66 20 70 20 65  | 1.1 [uScMs f p e
4e 3a 74 20 63 43 4d 70 20 73 20 5d 29 2c 20 48  | N:t cCMp s ]), H
54 54 50 2f 31 2e 30 20 66 72 72 2d 61 64 30 33  | TTP/1.0 frr-ad03
5b 43 33 35 44 33 43 36 39 5d 20 28 54 72 61 66  | [C35D3C69] (Traf
66 69 63 2d 53 65 72 76 65 72 2f 35 2e 33 2e 38  | fic-Server/5.3.8
20 5b 75 53 63 4d 5d 29 00 a0 03 00 0d 67 7a 69  |  [uScM]).?...gzi
70 2c 20 64 65 66 6c 61 74 65 00 a0 09 00 44 4a  | p, deflate.?..DJ
53 45 53 53 49 4f 4e 49 44 3d 38 36 37 45 30 38  | SESSIONID=867E08
33 41 41 32 32 44 34 30 30 38 35 41 46 39 43 35  | 3AA22D40085AF9C5
43 41 33 32 37 44 39 32 41 46 2e 41 53 54 50 50  | CA327D92AF.ASTPP
52 4d 31 39 3b 20 63 6f 6f 6b 69 65 63 68 65 63  | RM19; cookiechec
6b 3d 31 00 a0 0c 00 08 6e 6f 2d 63 61 63 68 65  | k=1.?...no-cache
00 a0 08 00 03 31 36 32 00 a0 0e 00 53 4d 6f 7a  | .?...162.?..SMoz
69 6c 6c 61 2f 34 2e 30 20 28 63 6f 6d 70 61 74  | illa/4.0 (compat
69 62 6c 65 3b 20 4d 53 49 45 20 36 2e 30 3b 20  | ible; MSIE 6.0;
41 4f 4c 20 39 2e 30 3b 20 57 69 6e 64 6f 77 73  | AOL 9.0; Windows
20 4e 54 20 35 2e 31 3b 20 53 56 31 3b 20 2e 4e  |  NT 5.1; SV1; .N
45 54 20 43 4c 52 20 31 2e 31 2e 34 33 32 32 29  | ET CLR 1.1.4322)
00 00 0f 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ...~~~~~~~~~~~~~
7e 7e 00 00 0d 7e 7e 7e 7e 7e 20 7e 7e 7e 7e 7e  | ~~...~~~~~ ~~~~~
7e 7e 00 a0 07 00 21 61 70 70 6c 69 63 61 74 69  | ~~.?..!applicati
6f 6e 2f 78 2d 77 77 77 2d 66 6f 72 6d 2d 75 72  | on/x-www-form-ur
6c 65 6e 63 6f 64 65 64 00 a0 04 00 02 64 65 00  | lencoded.?...de.
00 07 7e 7e 7e 7e 7e 7e 7e 00 00 6f 7e 7e 7e 7e  | ..~~~~~~~..o~~~~
3a 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | :~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ~~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ~~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ~~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ~~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e  | ~~~~~~~~~~~~~~~~
7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 7e 00 a0 01 00 a4  | ~~~~~~~~~~~.?..?
69 6d 61 67 65 2f 67 69 66 2c 20 69 6d 61 67 65  | image/gif, image
2f 78 2d 78 62 69 74 6d 61 70 2c 20 69 6d 61 67  | /x-xbitmap, imag
65 2f 6a 70 65 67 2c 20 69 6d 61 67 65 2f 70 6a  | e/jpeg, image/pj
70 65 67 2c 20 61 70 70 6c 69 63 61 74 69 6f 6e  | peg, application
2f 78 2d 73 68 6f 63 6b 77 61 76 65 2d 66 6c 61  | /x-shockwave-fla
73 68 2c 20 61 70 70 6c 69 63 61 74 69 6f 6e 2f  | sh, application/
76 6e 64 2e 6d 73 2d 65 78 63 65 6c 2c 20 61 70  | vnd.ms-excel, ap
70 6c 69 63 61 74 69 6f 6e 2f 76 6e 64 2e 6d 73  | plication/vnd.ms
2d 70 6f 77 65 72 70 6f 69 6e 74 2c 20 61 70 70  | -powerpoint, app
6c 69 63 61 74 69 6f 6e 2f 6d 73 77 6f 72 64 2c  | lication/msword,
20 2a 2f 2a 00 a0 0b 00 0f 77 77 77 2e 70 72 65  |  */*.?...www.pre
21.06.2005 12:02:55 org.apache.jk.common.ChannelSocket processConnection
WARNUNG: processCallbacks status 2
21.06.2005 12:02:58 org.apache.jk.common.ChannelSocket processConnection
INFO: connection timeout reached

After downgrading our webservers to 1.3.33 and using mod_jk 1.2.5 the problems 
have gone. After we changed our webservers to run the combination 1.3.33 and 
mod_jk 1.2.10 we meet the problems again.

So I would conclude that the problems result from newer versions of the mod_jk 
module.

Your help solving this problem would be appreciated.

Regards
J�rg Cebulla

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

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org