MantisBT - ParaView
View Issue Details
0005164ParaViewBugpublic2007-06-11 12:222016-08-12 09:57
Ken Moreland 
Utkarsh Ayachit 
normalfeaturealways
closedmoved 
 
 
0005164: Save state after server dies
When we (at Sandia) launch a PV server, it is on an allocated job on one of our clusters. The job could die for a variety of reasons, the most common (hopefully) that the allocated time on the job runs out and the scheduler kills the job.

Since PV 3 has the wonderful feature of allowing the client to live on after the server has died, it would be nice if it handled a server crash better. It should be able to detect the crash better (right now you just get a bunch of errors concerning the socket connection to the server). Also, since the client is still active, it should be able to save the state. That way, the user could quickly restore his session once reconnected to the server. Even better, it would be nice if PV would ask the user if he wants to reconnect and automatically reconnect and restore the state.

This feature was brought up while talking with users during the ParaView Summit on 6/5/2007.
No tags attached.
Issue History
2008-04-09 20:55Berk GeveciCategory => 3.6
2009-02-16 15:26Ken MorelandAssigned ToBerk Geveci => Burlen
2009-05-13 13:47Utkarsh AyachitTarget Version => 3.6
2009-08-25 18:37Utkarsh AyachitCategory => Bug
2009-08-25 18:37Utkarsh AyachitTarget Version3.6 => 3.6.2
2009-08-31 16:17Utkarsh AyachitAssigned ToBurlen => Utkarsh Ayachit
2009-09-01 13:00Utkarsh AyachitNote Added: 0017280
2009-09-01 13:00Utkarsh AyachitTarget Version3.6.2 => 3.8
2016-08-12 09:57Kitware RobotNote Added: 0037521
2016-08-12 09:57Kitware RobotStatusexpired => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved

Notes
(0017280)
Utkarsh Ayachit   
2009-09-01 13:00   
I am making this 3.8 bug since this will be easier (and avoid re-fixing) once we add branding changes to CVS.
(0037521)
Kitware Robot   
2016-08-12 09:57   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.