Salut,
Peter Williams wrote:
> I just answered my own question
>
> It literally means invalid request, so the error message is quite clear.
>
> I wasn't expecting this error at all so I guess I tried to read more
> into it than was really there.
On the client side, you are getting a 404 right? The page might be blank
(we need to customize the error page), but the status must be 404. If
not, this is a bug.
Thanks
-- Jeanfrancois
>
> -Peter
>
> Peter Williams wrote:
>> I get this one from time to time (not random though, as far as I can
>> tell).
>>
>> Is this a bug in the server? If not, how do I find out what happened?
>>
>> Apr 14, 2008 4:50:11 PM com.sun.grizzly.DefaultProtocolChain
>> executeProtocolFilter
>> SEVERE: ProtocolChain exception
>> java.lang.IllegalStateException: Invalid request
>> at
>> com.sun.enterprise.v3.services.impl.HttpUtils.findContextRoot(HttpUtils.java:114)
>>
>> at
>> com.sun.enterprise.v3.services.impl.ContextRootMapper.parseContextRoot(ContextRootMapper.java:168)
>>
>> at
>> com.sun.enterprise.v3.services.impl.ContextRootMapper.map(ContextRootMapper.java:112)
>>
>> at
>> com.sun.enterprise.v3.services.impl.HttpProtocolFilter.execute(HttpProtocolFilter.java:88)
>>
>> at
>> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:124)
>>
>> at
>> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:90)
>>
>> at
>> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:75)
>>
>> at
>> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:54)
>>
>> at
>> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
>>
>> at
>> com.sun.grizzly.util.WorkerThreadImpl.run(WorkerThreadImpl.java:154)
>>
>> This is with a Apr 11 build of V3.
>>
>> -Peter
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>