When vault fails because it has been idle too long, it fails

Perry · Post by **Perry** » Tue Jun 21, 2005 8:45 am

When I go to perform an operation in Vault (3.0.7), and I've not done something in it for the last couple of minutes (ie, the client GUI has been sitting there idle, because closing it and reopening it takes too long), then when I try to do something -- eg, check out a file -- the operation fails with a message that the cert has expired, or something.

It then reconnects, makes me hit Ok for the repository choice again, and fails to complete the action I said to do, and in fact also loses my selection in the list control on the right hand side of the GUI (where files are listed).

I'd prefer not to have to hit Ok for the default repository again, and I'd frankly prefer that it just reestablish the connection quietly and successfully, and that it not lose my selection, and that it not fail the operation I was trying to do.

Post by **jclausius** » Tue Jun 21, 2005 9:11 am

Yes this can be annoying, but losing a session should not happen in just a couple of minutes of inactivity.

I'd look at the bigger picture. Is there any reason you are losing your session just after a couple of minutes? A firewall issue perhaps? Check the Vault server, is something restarting the ASP.Net process?

Post by **jclausius** » Tue Jun 21, 2005 9:20 am

I'll log a feature request about this behavior, if your client has been inactive longer than the IIS session timeout.

Perry · Post by **Perry** » Fri Jun 24, 2005 5:54 pm

I don't know why Vault is losing the session, but it isn't its losing the session that annoys me, but it then putting up all those irritating message boxes and then forgetting what I was doing and what I had selected. If it didn't forget all that stuff, I wouldn't mind it losing its session.

Post by **jclausius** » Sat Jun 25, 2005 6:36 am

Understandable. As indicated in my previous post, I've logged an RFE.