Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates
 212.85.38.229 as permitted sender)
Message-ID: <52CAE865.4020400@ice-sa.com>
Date: Mon, 06 Jan 2014 18:31:17 +0100
From: =?ISO-8859-1?Q?Andr=E9_Warnier?= <aw@ice-sa.com>
Reply-To: Tomcat Users List <users@tomcat.apache.org>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Re: Packet misses in Tomcat
References: 
 <9b348a313687449081af93ae19b16906@SINPR04MB220.apcprd04.prod.outlook.com>
 <CAG6aRdWMRs2Q7ave=seTBnYU8svDJ+6=bD-XNpHBWYcphW7zpQ@mail.gmail.com>
 <355541b43da54d70b2c7fad4c89e3e59@SIXPR04MB223.apcprd04.prod.outlook.com>
In-Reply-To: 
 <355541b43da54d70b2c7fad4c89e3e59@SIXPR04MB223.apcprd04.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Divyaprakash Y wrote:
>> Issue: Few packets do not reach the application servlet but tomcat receives them. The missing packets reach the HTTP layer and thereafter they disappear.
>>
>> This issue is not frequent but occasionally consistent. For the POSTs of missing packet I am not able to find the entry in localhost_access_log.
> 
>> How do you know that the packet reaches tomcat if there is no matching entry in localhost_access.log? Does all other access appear in this file?
> 
> 
> I could see the packet in the wireshark capture and it has reached HTTP layer so I thought it has reached Tomcat; I may be wrong here. Also, as far as my observation, every hit to the application URLs was getting logged in local access log.
> 

And is there anything in the Tomcat error logs ?
(Or the Windows Event logs)

A HTTP request might be discarded by Tomcat for various reasons (*) before it is ever 
mapped to an application.
In such a case, there is probably also no log of the request in the Access log.
But I would expect some error message in the Tomcat error logs.

(*) Invalid HTTP request, incomplete request, etc..
If there are really packets being lost somewhere, then for POST requests the request size 
would not match the Content-length header, and that may be one of these cases.

I must say that the "packets lost" hypothesis sound a bit iffy to me.
This is TCP, which should detect missing packets and cause a client connection abort if it 
was the case.  The invalid HTTP request being rejected by Tomcat sounds more probable to me.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org