Return-Path: Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: (qmail 54424 invoked from network); 10 Aug 2010 12:17:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Aug 2010 12:17:00 -0000 Received: (qmail 18945 invoked by uid 500); 10 Aug 2010 12:16:57 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 18643 invoked by uid 500); 10 Aug 2010 12:16:53 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 18634 invoked by uid 99); 10 Aug 2010 12:16:51 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 12:16:51 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [125.17.121.198] (HELO bgxius-ex01.XIUS-bcgi.ltd) (125.17.121.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Aug 2010 12:16:43 +0000 Received: from bgxius-ex01.XIUS-bcgi.ltd ([10.193.50.60]) by bgxius-ex01.XIUS-bcgi.ltd ([10.193.50.60]) with mapi; Tue, 10 Aug 2010 17:46:20 +0530 From: Karthik Nanjangude To: Tomcat Users List Date: Tue, 10 Aug 2010 17:46:18 +0530 Subject: RE: 2 POST requests to underlying Server Thread-Topic: 2 POST requests to underlying Server Thread-Index: Acs4fdBBc4WwWyjOSkO8FrgMTFyvegABO1nw Message-ID: <22571048298BC44DAF91BE12457E873D8E89C9A9@bgxius-ex01.XIUS-bcgi.ltd> References: <22571048298BC44DAF91BE12457E873D8E89C817@bgxius-ex01.XIUS-bcgi.ltd> <4C612C78.6060705@ice-sa.com> <22571048298BC44DAF91BE12457E873D8E89C92C@bgxius-ex01.XIUS-bcgi.ltd> <4C61354E.4080705@ice-sa.com> In-Reply-To: <4C61354E.4080705@ice-sa.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi >> Have you really traced the browser -> server side to see if the duplicat= e POST request As I have already said by using the TCP Thread dump using command "tcpdump -i bond0 -s 1500 -w / tmp / test.pcap " We are clearly able to see the IP Address of Apache written 2 times POST f= or the JBOSS ( Tomcat built in) being called with in 12 seconds apart. We also made sure there is no traffic /users using the web application duri= ng the tcp dump taken. >> Are they really the same, from the same client, with the same content For simple test case we used 1 simple transaction Page to do the activity For insertion, but the since 2 request to web server ,we see 2 rows inserte= d in DB This has happened in spite of blocking multiple button clicks on jsp page u= sing jscript filter. >> claim that Apache or mod_jk or Tomcat duplicates a POST My Observation as per TCP dump command, we clearly see multiple request bei= ng sent from Apache to web server. With regards KArthik -----Original Message----- From: Andr=E9 Warnier [mailto:aw@ice-sa.com] Sent: Tuesday, August 10, 2010 4:48 PM To: Tomcat Users List Subject: Re: 2 POST requests to underlying Server Karthik Nanjangude wrote: > Hi > >>> (*) do you have any particular reason to use this setting, instead of t= he default ? Or is > it just something you copied from some blog page ? > > > 1) I have not copied the same from any Blog , it is as defined > configuration as is from the N/w team > > 2) Where can I fine the default settings for the same ? In the on-line documentation, at http://tomcat.apache.org/connectors-doc/reference/workers.html > > > 3) As I have already said We have put a Java script filter to disable > multiple Clicks for dual request from the Browser ( IE 7+ / FF 3+ ) > Well, maybe it is not working. Have you really traced the browser -> serve= r side to see if the duplicate POST request originates there ? Plus, in your original message, you do not define very clearly what these 2= POST requests are. Are they really the same, from the same client, with the same content= ? how close to one another do they arrive ? If it was mod_jk resending the same request after the socket_timeout of 10 = s, then the 2 POST requests should be separated by at least 10 s. Are they ? As someone once said : Extraordinary claims require extraordinary proof. In other words : you seem to claim that Apache or mod_jk or Tomcat duplicat= es a POST request. This is not the behaviour experienced by the vast majority of Apa= che + mod_jk + Tomcat installations. So you need data a bit more solid than what you have= supplied so far, before someone will believe that there is another reason than the user= clicking twice. > > > > > With regards > karthik > > > > -----Original Message----- > From: Andr=E9 Warnier [mailto:aw@ice-sa.com] > Sent: Tuesday, August 10, 2010 4:10 PM > To: Tomcat Users List > Subject: Re: 2 POST requests to underlying Server > > Karthik Nanjangude wrote: >> Hi >> >> Spec >> Java 1.5 >> O/s : Linux >> APP Server : JBOSS4.2.1 (Tomcat built with) >> HTTP Server : apache_2.2.11 [ With out SSL ] >> Mod library : mod_jk-1.2.28-httpd-2.2.X.so >> LB 1 Apache : 1 JBOSS:Port of application >> >> >> Question : Some times We have observed that on WEB Application ( clic= k on button in jsp ) >> Apache is sending 2 POST requests to underlying JBOSS (= Tomcat server ). >> >> Note: We even put a Java script filter to disable multiple Clicks for th= e page, >> >> >> How we Observed : Via TCP Thread dump using command "tcpdump -i bond= 0 -s 1500 -w / tmp / test.pcap " >> >> >> Can this configuration "worker.node1.socket_timeout=3D10" got any thing = to do with this multiple request activity? >> > Unlikely, but : > > 1) simple test : remove this setting, and see if the issue still appears = (*) > (By removing the setting, you make the timeout infinite) > > 2) use the mod_jk logging level TRACE, to see exactly what mod_jk is send= ing to Tomcat > > 3) It is unlikely that any Apache or mod_jk or Tomcat component would rep= eat a POST > request, because that kind of violates the HTTP RFC. So chances are, tha= t the double POST > request is /still/ coming from the browser. > > > (*) do you have any particular reason to use this setting, instead of the= default ? Or is > it just something you copied from some blog page ? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org > For additional commands, e-mail: users-help@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org