Closed glassfishrobot closed 11 years ago
glassfishrobot
commented
6 years ago glassfishrobot
commented
11 years ago @glassfishrobot Commented @shingwaichan said:
What is the impact on the customer of the bug? Cannot configure the MaxSavePostSize. The default is 4*1024.
What is the cost/risk of fixing the bug? Just get the value from config and set it to connector. I have already fixed a fix locally.
Is there an impact on documentation or message strings? Yes, please add the information about this attribute.
Which tests should QA (re)run to verify the fix did not destabilize GlassFish? SQE pe/web
Which is the targeted build of 4.0 for this fix? 4.0_b85
If this an integration of a new version of a component from another project, what are the changes that are being brought in? This might be list of Jira issues from that project or a list of revision messages. N/A
glassfishrobot
commented
11 years ago @glassfishrobot Commented @shingwaichan said: Sending web-glue/src/main/java/com/sun/enterprise/web/connector/coyote/PECoyoteConnector.java Transmitting file data . Committed revision 61167.
glassfishrobot
commented
7 years ago @glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-20163
glassfishrobot
commented
11 years ago @glassfishrobot Commented Reported by @shingwaichan
glassfishrobot
commented
11 years ago @glassfishrobot Commented Marked as fixed on Thursday, April 4th 2013, 9:09:08 am
The maxSavePostSize is introduced to configure the max save post size internally. The Grizzly configure max-save-post-size-bytes in 2.3.
We suppose to configure it as follows: asadmin set configs.config.server-config.network-config.protocols.protocol.http-listener-1.http.max-save-post-size-bytes=5000
And the above Grizzly code has been integrated April 2 evening. The web container has not invoke the setter in the backend even though it is set in asadmin.