search

google-code-export / ords

Automatically exported from code.google.com/p/ords
1 stars 0 forks source link

Session time-out causes crash when uploading large database #628

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Attempt to upload a large database - an action that takes more than (30 mins 
/ 1 hour?) to complete
2. Notice that whilst eh 1% - 100% count in the corner of the screen is 
continuing, there is nothing untowards to see.
3. Note that once the upload count reaches 100% - the point at which the email 
alert is sent the the system starts actually process the database, the 
following crash report is generated: 

HTTP Status 500 - setAttribute: Session 
[65D423E9BA56EA43BD82242C5C159D78.node-03] has already been invalidated
________________________________________
type Exception report
message setAttribute: Session [65D423E9BA56EA43BD82242C5C159D78.node-03] has 
already been invalidated
description The server encountered an internal error (setAttribute: Session 
[65D423E9BA56EA43BD82242C5C159D78.node-03] has already been invalidated) that 
prevented it from fulfilling this request.
exception
java.lang.IllegalStateException: setAttribute: Session 
[65D423E9BA56EA43BD82242C5C159D78.node-03] has already been invalidated
        org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1437)
        org.apache.catalina.session.StandardSession.setAttribute(StandardSession.java:1402)
        org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:156)
        uk.ac.ox.oucs.ords.ordsProjectNode.servlets.DatabaseWork.doPost(DatabaseWork.java:435)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:641)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
        uk.ac.ox.oucs.ords.servlets.filters.ParamFilter.doFilter(ParamFilter.java:24)
note The full stack trace of the root cause is available in the Apache 
Tomcat/7.0.28 logs.
________________________________________
Apache Tomcat/7.0.28

Please note that the time-out does NOT affect the actual import or processing 
of the database, which carries on just fine in the background. A user probably 
wont realize this, however.

What is the expected output? What do you see instead?
Might be nice to increase the time-out length whilst uploading big databases. 
Plus the system should fail more elegantly if a time-out does occur.

Please use labels and text to provide additional information.
Chrome Staging 1.0.9.

Original issue reported on code.google.com by jajwil...@gmail.com on 10 Mar 2015 at 4:06