users@glassfish.java.net

Re: Is there a size limit for data in the request header?

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Tue, 20 May 2008 18:54:27 -0400

Hi,

forget my previous email as I've found a proper/better way for changing
the value. In domain.xml, looks for:

> <connection-pool max-pending-count="4096" queue-size-in-bytes="4096" receive-buffer-size-in-bytes="4096" send-buffer-size-in-bytes="8192"/>

Change the

receive-buffer-size-in-bytes="4096"

to

receive-buffer-size-in-bytes="8192"

and the exception will go away.

Let me know :-)

-- Jeanfrancois

Jeanfrancois Arcand wrote:
> Hi,
>
> glassfish_at_javadesktop.org wrote:
>> I have the same question. Or at least a similar one.
>>
>> The following is output to the logs.
>>
>> java.io.IOException: PWC4662: Request header is too large
>> at
>> org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:723)
>>
>> at
>> org.apache.coyote.http11.InternalInputBuffer.parseHeader(InternalInputBuffer.java:640)
>>
>> at
>> org.apache.coyote.http11.InternalInputBuffer.parseHeaders(InternalInputBuffer.java:526)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.parseRequest(DefaultProcessorTask.java:701)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.doProcess(DefaultProcessorTask.java:566)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.process(DefaultProcessorTask.java:813)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.executeProcessorTask(DefaultReadTask.java:339)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:261)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultReadTask.doTask(DefaultReadTask.java:212)
>>
>> at
>> com.sun.enterprise.web.portunif.PortUnificationPipeline$PUTask.doTask(PortUnificationPipeline.java:361)
>>
>> at
>> com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
>> at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorkerThread.run(SSLWorkerThread.java:106)
>>
>>
>>
>> I am using Apache httpd 2.2.6, with reverse proxy to glassfish V2ur2.
>> I get this to happen when sending a long request URL (~4K). I suspect
>> the proxied http message may contain a large header.
>> It is possible that glassfish throw this when parsing the request line
>> as well.
>
>>
>> What are the size limits for * the request line
>> * any request header line
>> * the entire header
>> ?
>>
>> What configuration, if any, can be used to tweak these limits?
>
> In domain.xml, add the following property under http-service:
>
> <property name="bufferSize" value="8192"/>
>
> The default is 8192, so I recommend you increase the value and see if
> that works.
>
> Let me know what you get.
>
> -- Jeanfrancois
>
>
>
>>
>> Thanks.
>> [Message sent by forum member 'jbelis' (jbelis)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=275603
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>