Hi Trustin - 

Thanks for the reply. 

I updated from trunk, and see all the new filter-codec-http stuff there -
I'll use that, for sure.

A couple things:

1. The problem that I had was only manifested when I slammed a bunch of GETs
in a row - if I added even a tiny (like, 10ms) delay, then there was no
problem. So I'm okay for now, and will upgrade to the trunk
filter-codec-http stuff when I get a chance.

2. On the maven build from trunk (version 597419), I'm getting test failures
- shown below - just in case it's useful. I'm building on Mac OS X. I am new
to maven (pretty cool) so I'm just using 'mvn install'. Test failures, so
I'm not getting  any jars.

Results :

Failed tests: 
 
testSuspendResumeReadWrite(org.apache.mina.transport.socket.nio.SocketTrafficControlTest)
 
testConnectFutureFailureTiming(org.apache.mina.transport.socket.nio.SocketConnectorTest)

Tests in error: 
 
testExecutorFilterAtTheEnd(org.apache.mina.filter.logging.MdcInjectionFilterTest)
 
testExecutorFilterAtBeginning(org.apache.mina.filter.logging.MdcInjectionFilterTest)
 
testExecutorFilterBeforeProtocol(org.apache.mina.filter.logging.MdcInjectionFilterTest)
  testMultipleFilters(org.apache.mina.filter.logging.MdcInjectionFilterTest)
 
testTwoExecutorFilters(org.apache.mina.filter.logging.MdcInjectionFilterTest)
 
testOnlyRemoteAddress(org.apache.mina.filter.logging.MdcInjectionFilterTest)

Tests run: 123, Failures: 2, Errors: 6, Skipped: 0

Thanks again - very much appreciated.

Cheers,

parki...

--- x8 snip



Trustin Lee wrote:
> 
> On Nov 22, 2007 10:00 AM, parki <[EMAIL PROTECTED]> wrote:
>>
>> hello!
>>
>> I'm working on an async http server, transferring messages either way
>> (ie.
>> not necessarily request response). I'm basing the code on
>> org.apache.mina.example.httpserver.codec.
>>
>> Everything works well, until I slam a bunch of messages to the server
>> (simple GETs).
>>
>> After some digging around, it's clear that there can be more than one
>> complete message in the IoBuffer when decodable/decode is called. I've
>> tried
>> to rework the HttpRequestDecoder to parse up a possible bunch of
>> messages,
>> but running into many twisty little tunnels - something is telling me I
>> might be going down the rabbit hole.
>>
>> It's looking like the contents of the IoBuffer isn't, well, isn't exactly
>> right, and I start to get off-by-one errors trying to find the location
>> of
>> the next message (if there is more than one) and then things go all to
>> hell.
>>
>> Can anyone shed any light on this?
> 
> I'd like to recommend you to try mina-filter-codec-http in our trunk
> instead... :)
> 
> HTH,
> Trustin
> -- 
> what we call human nature is actually human habit
> --
> http://gleamynode.net/
> --
> PGP Key ID: 0x0255ECA6
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Problems-handling-multiple-messages-in-HttpRequestDecoder-tf4853729s16868.html#a13898039
Sent from the Apache MINA Support Forum mailing list archive at Nabble.com.

Reply via email to