-
Notifications
You must be signed in to change notification settings - Fork 60
Streaming data via AJP causes OOME #1787
Comments
Reported by payara_steve |
@rlubke said: |
@rlubke said: |
@rlubke said: I've made a quick change to the aforementioned mentioned class and it appears to have resolved the problem. We can provide a drop-in replacement JAR for the Grizzly runtime within GlassFish for you to test/confirm with in your environment, but we'll need to know what version of GlassFish you're using. |
payara_steve said: |
@rlubke said: |
File: grizzly-http-ajp-2.3.19.jar |
@rlubke said: You should be able to replace the existing 2.3.19 jar in your local maven repo and re-build your custom GF server to pick the JAR up. |
payara_steve said: BTW your repo synch to github seems to have stopped https://github.com/GrizzlyNIO/grizzly-mirror |
@rlubke said: As to the mirror, you're right. Thanks for pointing that out. We'll look into it. |
@rlubke said: |
Marked as fixed on Tuesday, June 30th 2015, 9:34:42 am |
This issue was imported from java.net JIRA GRIZZLY-1787 |
Streaming data via AJP without setting a Content-Length header results in the data accumulating in-memory resulting in an eventual OutOfMemoryError.
See payara/Payara#350 for detailed diagnostics and reproducer
Affected Versions
[2.3.19]
The text was updated successfully, but these errors were encountered: