Web Order Lock Timeout

Hi,

Ours are also set to 30 minutes; we feel that changing this time depending on whether membership sales or general public sales are open would aggravate our customers (who are a littel resistant to change) and so we decided on 30 mins as a happy medium.

Also, many of our customers book more than one performance at a time (searching for specific seats); and so we felt that 30 minutes would give them enough time to do this.

I just wanted to point out that you can now deal with this programatically, with the new v8.0 AlterTicketExpiration method.  This method allows you to extend (or shorten) the time left on the current connection.  So, for example, you could set your global timeout setting to 10 minutes and then extend each session by 5 minutes whenever something is added to the cart.  That way you don't have to start with a long timeout period but the timeout gets extended every time a shopping action is taken.

Actually, I think there's a bit of confusion in this thread. The "Order Lock Timeout" setting in T_defaults, which Marty's original question was about, I think, is not the setting that controls how long seats are held in a web shopping cart before they time out

That one, which is the one that Chuck's helpful note is about,  is the seat server .config setting:

SessionTimeoutMinutes ="20"

in TessituraSeatServerService80.exe.config.

The "Order Lock Timeout" setting in T_defaults is a bit more obscure, and has to do with locking Orders, not Seats - according to the t_defaults notes it does this:

"When an existing order is loaded into a web cart (typically for a subscription renewal), the order must locked.  To avoid having these orders locked indefinitely (which would happen if the web session was abandoned), this setting allows the order to be loaded again if the original locking web session is over n minutes old.  This setting determines that amount of time.  The default is 720 minutes."

I have a feeling that distinction confuses people - it certainly confused me initially.

Ken McSwain

How this file can be accessed to change the setting?

This is not a setting in a file that you alter--this is a method that allows you to programatically alter the timeout from your web application.  Just like you call web methods to control other aspects of your application.

Our website designed and managed by Datacom. Does that mean this method can be accessed and modified by them only.

The default settings for all sessions is stored in the Seat Server configuration file under the key SessionTimeoutMinutes.  So you can change that setting if you want to affect all web settings.  Please go ahead and open a support ticket if you need more detailed information.

Thanks.

The default settings for all sessions is stored in the Seat Server configuration file under the key SessionTimeoutMinutes.  So you can change that setting if you want to affect all web settings.  Please go ahead and open a support ticket if you need more detailed information.

Thanks.