Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
From: Anantaneni Harish <anantaneni.harish@vertexsoft.com>
To: Tomcat Users List <users@tomcat.apache.org>
Date: Mon, 31 Oct 2011 18:58:55 -0700
Subject: RE: cannot read complete HTTP request body. It reads only 8192
 characters
Thread-Topic: cannot read complete HTTP request body. It reads only 8192
 characters
Thread-Index: AcyYObI3aTwpC1g0S1mhFSzII2DJ0gAAAhbA
Message-ID: 
 <76A7159F4F167A4680050E6A2B1DB0C1098994B6@SG1RD3XVS451.red003.local>
References: 
 <76A7159F4F167A4680050E6A2B1DB0C10989907B@SG1RD3XVS451.red003.local>
	<3451529724817954742@unknownmsgid>
	<76A7159F4F167A4680050E6A2B1DB0C109899134@SG1RD3XVS451.red003.local>
	<4EA91BB0.9060707@kippdata.de>
	<76A7159F4F167A4680050E6A2B1DB0C109899173@SG1RD3XVS451.red003.local>
	<4EA97B09.5040407@christopherschultz.net>
	<CABzHfVkyRmrG1ck1b6AfFcD=DDQ3hgeVD3c7mJA9=Gi4kPjqBQ@mail.gmail.com>
	<4EAA9B1B.2040605@ice-sa.com>
	<76A7159F4F167A4680050E6A2B1DB0C1098994B0@SG1RD3XVS451.red003.local>
	<CAAKASGyCdbG41VEi-A-RnedXwXuMUez13O-v5HRtx421hiPM8A@mail.gmail.com>
	<76A7159F4F167A4680050E6A2B1DB0C1098994B2@SG1RD3XVS451.red003.local>
 <CAAKASGwyTvyxEp1n9AeeaRs-67FiGB60W3MzE54s+YxZqKtkXg@mail.gmail.com>
In-Reply-To: 
 <CAAKASGwyTvyxEp1n9AeeaRs-67FiGB60W3MzE54s+YxZqKtkXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Dont know :(, must be different.=20

Thanks and Regards,
Harish

-----Original Message-----
From: Igor Cicimov [mailto:icicimov@gmail.com]=20
Sent: Tuesday, November 01, 2011 10:57 AM
To: Tomcat Users List
Subject: RE: cannot read complete HTTP request body. It reads only 8192 cha=
racters

And same kernel network settings?
 On Nov 1, 2011 12:50 PM, "Anantaneni Harish" <
anantaneni.harish@vertexsoft.com> wrote:

> Both environments have the following softwares.
>
> OS      Name    Red Hat Enterprise Linux
>        Version release 5.3 (Tikanga)
> Java    Name    Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
>        Version 1.6.0_13
> Tomcat  Name    apache-tomcat
>        Version 5.5.28
>
> Thanks and Regards,
> Harish
> -----Original Message-----
> From: Igor Cicimov [mailto:icicimov@gmail.com]
> Sent: Tuesday, November 01, 2011 10:47 AM
> To: Tomcat Users List
> Subject: Re: cannot read complete HTTP request body. It reads only 8192
> characters
>
> You never said what is the difference between your environment and the
> customer one or I missed that info. Same OS? Same Java version?
>
> On Tue, Nov 1, 2011 at 12:42 PM, Anantaneni Harish <
> anantaneni.harish@vertexsoft.com> wrote:
>
> >
> > Any thoughts about this?
> >
> > Thanks and Regards,
> > Harish
> > -----Original Message-----
> > From: Anantaneni Harish
> > Sent: Monday, October 31, 2011 11:23 AM
> > To: Tomcat Users List
> > Subject: RE: cannot read complete HTTP request body. It reads only 8192
> > characters
> >
> > String keyValuePair =3D null;
> > String[] arrKeyValue =3D null;
> > BufferedReader in =3D request.getReader();
> > while ((keyValuePair =3D in.readLine()) !=3D null) {
> > arrKeyValue =3D keyValuePair.split("=3D");
> >
> > Above code reads incomplete data(read only 8192 bytes) at my customer's
> > environment, but reads complete data in my environment.
> >
> > String keyValuePair =3D null;
> > String[] arrKeyValue =3D null;
> > BufferedReader in =3D new BufferedReader(new
> > InputStreamReader(request.getInputStream()));
> > while ((keyValuePair =3D in.readLine()) !=3D null) {
> > arrKeyValue =3D keyValuePair.split("=3D");
> >
> > Above code reads complete data in both the environments. *no changes do=
ne
> > to customer's environment.
> >
> > I hope you can help me now by finding the reason for data lost at my
> > customer's environment when using request.getReader().
> >
> > Thanks and Regards,
> > Harish
> >
> > -----Original Message-----
> > From: Andr=E9 Warnier [mailto:aw@ice-sa.com]
> > Sent: Friday, October 28, 2011 9:08 PM
> > To: Tomcat Users List
> > Subject: Re: cannot read complete HTTP request body. It reads only 8192
> > characters
> >
> > Konstantin Kolinko wrote:
> > > 2011/10/27 Christopher Schultz <chris@christopherschultz.net>:
> > >> On 10/27/2011 4:58 AM, Anantaneni Harish wrote:
> > >>> Thanks for the directions the Rainer. Actually the issue is just
> > >>> solved.
> > >>>
> > >>> We have changed from BufferedReader in =3D request.getReader();
> > >>>
> > >>> to
> > >>>
> > >>> BufferedReader in =3D new BufferedReader(new
> > >>> InputStreamReader(request.getInputStream()));
> > >>>
> > >>> Now whole body has been read at my client's environment as well.
> > >>>
> > >>> But would like to know, what causes the issue. Do you have any
> > >>> idea, why same method can read whole data in my environment and
> > >>> does not read whole data at my customer's environment?
> > >> You'll have to provide more information, such as the code you are
> > >> using.
> > >>
> > >> I'm fairly sure Tomcat is not the source of the problem.
> > >>
> > >
> > > +1.
> > >
> > > I think you need to pay more attention on the documentation of the
> > > java.io.Reader#read() method, or maybe look for a tutorial.
> > >
> > > See also documentation for java.io.InputStream#available().
> > >
> > > In short:  the read() method returns a portion of data that is
> > > currently available. If you need more data you must call read()
> > > repeatedly in a loop until it returns -1.
> > >
> >
> > .. and the difference between two systems, may be that on one system, t=
he
> > network is
> > faster (or the system slower, or the buffer bigger) and so by the time
> you
> > do the read,
> > there are more bytes available in the buffer.
> >
> > > If you had provided some of your source code that performs reading, w=
e
> > > would be able to point at the exact error in your code.
> > >
> >
> > ---------------------------------------------------------------------
> > 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