Hi Mark, a bit more follow-up on accessing the servlet InputStream:
You advised "You'd be better off dropping the call to in.ready() and doing
a blocking
read on the socket.If you remove the call to
in.ready(), I'm fairly sure you'll see the warnings disappear."
I just thought I'd let you kno
Appreciate this a lot Mark.
I'm pretty sure my previous code had a short sleep in each loop but
thankfully, in-coming data rarely exceeds the Servlet InputBuffer size of
8192 so looping is rare.
I have been trying to get to grips with the asynchronous stuff but have not
got it going yet. The conc
On 28/08/2013 09:41, Mark Thomas wrote:
> On 27/08/2013 03:40, Vince Stewart wrote:
>> hi all,
>> thought I would add some progress on this topic.
>> I have changed my method for reading from the HttpServletRequest object but
>> the same warning message is thrown for every 8192 bytes read. I no lon
On 27/08/2013 03:40, Vince Stewart wrote:
> hi all,
> thought I would add some progress on this topic.
> I have changed my method for reading from the HttpServletRequest object but
> the same warning message is thrown for every 8192 bytes read. I no longer
> regard my code to be suspect though am h
hi all,
thought I would add some progress on this topic.
I have changed my method for reading from the HttpServletRequest object but
the same warning message is thrown for every 8192 bytes read. I no longer
regard my code to be suspect though am happy to be corrected. The
application operates compl
greetings all,
since commencing with version 8 (embedded) I have encountered no problems
except when the HttpServletRequest object receives a message bigger than
16384 k. In that circumstance a warning(below) is repeated X times for
messages bigger than 8192+(X*8192).
I notice in the InternalNioInp
