You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user reported that when viewing the search results on the production Data Portal when navigating between search result pages, the Data Portal responds with an error message:
I’m doing a quick EDI search to help fill in my estimate of how many lake-years of data we know to be out there. Here’s the query URL. The query returns many pages of results, but every time I try to navigate from one page to the next it throws an error:
An error has occurred in the Data Portal:
For further assistance, please contact the Environmental Data Initiative. Please copy the error message shown above into your email message, along with any other information that might help us to assist you more promptly.
So far, with a lot of browser refreshing and such, I’ve been able to get it to render at least the second page of the results, but haven’t yet had success with the third or any after that. I’m in Firefox on a Windows machine, FWIW.
This issue is reproducible only on the production Data Portal: to reproduce it, you must (1) search for a phrase that returns a large number of results and (2) wait for approximately 1-2 minutes. For this reason, we suspect there is an issue with a "public" user session timeout.
The text was updated successfully, but these errors were encountered:
I have found on production portal where the tomcat9 web.xml (/etc/tomcat9/web.xml) file had the default session changed from 30 minutes to 1 minute. I believe this change was in response to the large number of public sessions that were causing OOMs in portal.
A user reported that when viewing the search results on the production Data Portal when navigating between search result pages, the Data Portal responds with an error message:
This issue is reproducible only on the production Data Portal: to reproduce it, you must (1) search for a phrase that returns a large number of results and (2) wait for approximately 1-2 minutes. For this reason, we suspect there is an issue with a "public" user session timeout.
The text was updated successfully, but these errors were encountered: