Issue Details (XML | Word | Printable)

Key: JRA-6870
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Jeff Turner [Atlassian]
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
JIRA

Session timeout when migrating many issues

Created: 02/Jun/05 02:33 AM   Updated: 30/Jul/06 07:35 PM
Component/s: None
Affects Version/s: 3.2
Fix Version/s: 3.2.1

Time Tracking:
Not Specified

Participants: Jeff Turner [Atlassian]
Since last comment: 3 years, 26 weeks, 3 days ago
Resolution Date: 03/Jun/05 12:03 AM
Labels:


 Description  « Hide
A user reports getting a session timeout when migrating many issues:

2005-05-25 10:34:47,953 ERROR [action.admin.workflow.WorkflowMigrationManager] Error occurred creating change log: java.lang.IllegalStateException: getAttribute: Session already invalidated
java.lang.IllegalStateException: getAttribute: Session already invalidated
at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:953)
at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:171)
at webwork.action.factory.SessionMap.get(SessionMap.java:92)
at com.atlassian.jira.web.action.admin.workflow.WorkflowMigrationManager.getRemoteUser(WorkflowMigrationManager.java:211)
at com.atlassian.jira.web.action.admin.workflow.WorkflowMigrationManager.createChangeLog(WorkflowMigrationManager.java:195)
at com.atlassian.jira.web.action.admin.workflow.WorkflowMigrationManager.migrate(WorkflowMigrationManager.java:163)
at com.atlassian.jira.web.action.admin.workflow.scheme.SelectProjectWorkflowSchemeStep2.doExecute(SelectProjectWorkflowSchemeStep2.java:64)
at webwork.action.ActionSupport.execute(ActionSupport.java:153)
at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:46)
at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:131)
at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:142)
at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:58)

Having the session time out in such a way can be quite disastrous for the consistency of the database.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] added a comment - 03/Jun/05 12:03 AM
Fixed - session timeouts no longer affect the successful completion of workflow migrations.