--
> > The buffer is set at 1024 and i have tried it at 4096 and bigger numbers
> but
> > the same results. It seems the underlying ServletInputStream.readLine()
> > method is running past the end of the buffer.
> >
> > Is this a bug with JServ, or should I continue looking at our
> code? Like
> I
> > say, it works within other environments?
>
> We ran into the same thing. It ignores the "max" parameter as far as
> we could tell. There is also another bug that is stated on sun's site
> about inserting extra "\n" characters every once in awhile. The site
> said they have no plans to fix it last time I looked.
>
> As painful as it is, we had to resort to writing our own readline that
> took care of the buffering and just read a character a time with
> ServletInputStream.in(). We use it regularly with 10MB files and
> bigger with no problems, except it does eat a lot of CPU time.
>
> Write a simple readline replacement this way and see if your
> problem goes away. It did for us.
Thanks for that Frank it is indeed much appreciated. Its times like these
that the Internet is a wonderful place to be. Within 30minutes, I have had
my problem confirmed and on the route to fixing it. FANTASTIC.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]
