-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service Stability: Long lived objects eventually cause repeated stop-the-world gc. #2013
Comments
We're trying this because if we download via Apache going through AJP we are seeing this for large files (>2 GB): [2015-04-16T10:31:52.532-0400] [glassfish 4.1] [WARNING] [] [org.glassfish.grizzly.filterchain.DefaultFilterChain] [tid: _ThreadID=251 _ThreadName=jk-connector(3)] [timeMillis: 1429194712532] [levelValue: 900] [[ GRIZZLY0013: Exception during FilterChain execution java.lang.OutOfMemoryError: Java heap space ]]
FYI - We're still having once in a while Service temporarily unavailable: PROBLEM: HTTPS-dvn is CRITICAL on host dataverse.harvard.edu Service: HTTPS-dvn Additional Information: HTTP CRITICAL: HTTP/1.1 503 Service Temporarily Unavailable - 582 bytes in 30.697 second response time |
Adding the |
Passing to QA. |
Tested the original test case: Downloading a specific large datafile, >2GB immediately caused the 503 error. This no longer happens. Used a direct to glassfish, port 8181 with apache rewrite rules to bypass apache for downloading. Closing. |
The recent instability in service today seems to mostly be due to continuous stop-the-world gc.
I know this because each time there was a failure I checked:
jstat gcutil and
jmap -heap
Increasing the heap size helped but it's still happening.
Suggestions are to look at the access log and run the memory profiler on the app, looking for large object hierarchies being created and not freed on the most common pages, such as the homepage.
The text was updated successfully, but these errors were encountered: