[jira] Created: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
|
View:
New views
11 Messages
—
Rating Filter:
Alert me
|
 |
[jira] Created: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
----------------------------------------------------------------------- Key: MRM-1197 URL: http://jira.codehaus.org/browse/MRM-1197 Project: Archiva Issue Type: Bug Affects Versions: 1.2.1, 1.2 Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 Reporter: Chris Van Vlack When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 Detailed HTTP Request/Response: PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 User-Agent: Java/1.5.0_16 Host: maven.local Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Authorization: Basic YmFtYm9vOmJAbWIwbw== Content-Length: 32 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request Date: Tue, 02 Jun 2009 20:20:36 GMT Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva last-modified: Tue, 02 Jun 2009 15:04:37 GMT Content-Type: text/html;charset=utf-8 Content-Length: 1085 Connection: close <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> When the actual packets are examined they look like this: 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=179182#action_179182 ] Chris Van Vlack commented on MRM-1197: -------------------------------------- Found that this error can be thrown on line 310: http://svn.apache.org/viewvc/archiva/trunk/archiva-modules/archiva-web/archiva-webdav/src/main/java/org/apache/maven/archiva/webdav/ArchivaDavResource.java?view=annotate > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Updated: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Van Vlack updated MRM-1197: --------------------------------- Attachment: archivia-put-success.pcap archivia-400-error.pcap pcap of an error and success packet from maven to archiva > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Updated: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-1197: ---------------------------------- Fix Version/s: 1.2.2 > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180590#action_180590 ] Andrew Mitchell commented on MRM-1197: -------------------------------------- I'm also getting random 400 errors using Archiva 1.2.1 and Maven 2.0.8 & 2.0.9. Both the http and dav connectors to my snapshot repository occasionally fail when deploying snapshots. Interestingly most failures (possibly all) occur when the snapshot repository was being scanned by Archiva. Reduced the scanning frequency using the archiva web ui appears to help. > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Assigned: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching reassigned MRM-1197: ------------------------------------- Assignee: Maria Odea Ching > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184179#action_184179 ] Andreas Christoforides commented on MRM-1197: --------------------------------------------- We are noticing the same issue quite often when we uploaded artifacts, * It is not on the same artifact everytime. * I checked and all of our repository scanning including the database scanning is performed once a day and not during the times that the error has occurred > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184191#action_184191 ] Maria Odea Ching commented on MRM-1197: --------------------------------------- The current workaround for this is to disable both the metadata-updater and create-missing-checksums consumers. > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184527#action_184527 ] Andreas Christoforides commented on MRM-1197: --------------------------------------------- I disabled both the metadata-updater and the create-missing-checksums even though no repository scanning was scheduled to run when this issue occurs. Disabling them did not seem to help. 50% of the upload attempts fail! What is the underlying cause for this issue? > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Closed: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching closed MRM-1197. --------------------------------- Resolution: Fixed This is fixed by the changes made in MRM-1212. > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
|
|
[jira] Commented: (MRM-1197) Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1
by JIRA jira@codehaus.org
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://jira.codehaus.org/browse/MRM-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185062#action_185062 ] Maria Odea Ching commented on MRM-1197: --------------------------------------- Hi Andreas, the main cause of this was that the checksums were being created and the metadata updated after each artifact deployment as the consumers were executed. So when the actual checksums and metadata is deployed by Maven to the repository, it might be that the consumers were still executing thereby causing the intermittent error 400. As for disabling the consumers, you might need to restart Archiva after disabling them from the webapp. This is a known bug in Archiva which still needs to be fixed as well. > Random 400 Error when uploading maven-metadata.xml to Archiva 1.2/1.2.1 > ----------------------------------------------------------------------- > > Key: MRM-1197 > URL: http://jira.codehaus.org/browse/MRM-1197 > Project: Archiva > Issue Type: Bug > Affects Versions: 1.2, 1.2.1 > Environment: RHEL5.2, tomcat6-6.0.18-6.jpp5, Sun Java 1.5.0_16, Maven 2.0.9, Archiva 1.2.1, Apache httpd-2.2.3-11.el5_2.4 > Reporter: Chris Van Vlack > Assignee: Maria Odea Ching > Fix For: 1.2.2 > > Attachments: archivia-400-error.pcap, archivia-put-success.pcap > > > When maven tries to deploy a new/updated maven-metadata.xml or its md5/sha, occasionally a HTTP 400 - Bad Request is returned from Archiva. The following message is returned from Archiva: Content Header length was 32 but was 0 > Detailed HTTP Request/Response: > PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 > User-Agent: Java/1.5.0_16 > Host: maven.local > Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 > Connection: keep-alive > Authorization: Basic YmFtYm9vOmJAbWIwbw== > Content-Length: 32 > 24877de78f50a1cdb8bd71e2dfa933cfHTTP/1.1 400 Bad Request > Date: Tue, 02 Jun 2009 20:20:36 GMT > Set-Cookie: JSESSIONID=77ECDD66382B0B02356E1027D344D5FF; Path=/archiva > last-modified: Tue, 02 Jun 2009 15:04:37 GMT > Content-Type: text/html;charset=utf-8 > Content-Length: 1085 > Connection: close > <html><head><title>Apache Tomcat/6.0.18 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - Content Header length was 32 but was 0</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>Content Header length was 32 but was 0</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect (Content Header length was 32 but was 0).</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/6.0.18</h3></body></html> > When the actual packets are examined they look like this: > 1 0.000000 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [SYN] Seq=0 Win=32792 Len=0 MSS=16396 TSV=21157988 TSER=0 WS=7 > 2 0.000024 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [SYN, ACK] Seq=0 Ack=1 Win=32768 Len=0 MSS=16396 TSV=21157988 TSER=21157988 WS=7 > 3 0.000040 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=1 Ack=1 Win=32896 Len=0 TSV=21157988 TSER=21157988 > 4 0.000539 192.168.102.68 -> 192.168.102.68 HTTP PUT /archiva/repository/releases/components/gui-project/maven-metadata.xml.md5 HTTP/1.1 (packet with headers) > 5 0.000561 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=315 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 6 0.000591 192.168.102.68 -> 192.168.102.68 HTTP Continuation or non-HTTP traffic (packet with the 32 bytes of content) > 7 0.000603 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1 Ack=347 Win=33920 Len=0 TSV=21157988 TSER=21157988 > 8 0.055038 192.168.102.68 -> 192.168.102.68 HTTP HTTP/1.1 400 Bad Request (text/html) (packet with 400 error) > 9 0.055066 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [ACK] Seq=347 Ack=1349 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 10 0.055083 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [FIN, ACK] Seq=1349 Ack=347 Win=33920 Len=0 TSV=21158002 TSER=21158002 > 11 0.055892 192.168.102.68 -> 192.168.102.68 TCP 42242 > http [FIN, ACK] Seq=347 Ack=1350 Win=35584 Len=0 TSV=21158002 TSER=21158002 > 12 0.055910 192.168.102.68 -> 192.168.102.68 TCP http > 42242 [ACK] Seq=1350 Ack=348 Win=33920 Len=0 TSV=21158002 TSER=21158002 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
| Free embeddable forum powered by Nabble | Forum Help |
