dashCommerce

I have found that dashcommerce keeps requiring me to login whislt playing around in the admin section. There is a very little period of inactivity, if at all. Anyone come across this before???

 Are you sure it's dc? It sounds like you have session timout set too low.

Yeah that would be a setting on the server, by default its 20minutes.

hey guys thanks for your responses. the login expires whilst im using dc...no way is it in an idle state.

ive changed the sessionState mode="StateServer" and timeout=20 in the web.config file and made base classes dashcommercemasterpage and dashcommercepage classes serializable. despite those changes, it still happens. Im using ie8. the hosting company says the sessions are storing correctly.

Ive reproduced the issue now on an earlier version of ie. I've contacted my web host and they only allow 64mb for my app domain. They said "we were trying to reproduce the session issue and found that once sessions are expired, the trace log is being erased. The trace log usuallly is being erased when the application pool memory gets overloaded and application restarts (application pool recycles)." They suggested that theres a memory leak...

Has anyone come across this before? What kind of memory usage does dc typically use? Any ways i can reduce memory usage of dc...

 The issue usually only occurs in the admin section. Thanks in advance for any replies - they are much appreciated!

I've had this problem through several versions of dashCommerce and IE, Firefox and Safari - so it's ongoing and not browser-related.  What helped was to get more memory designated by the hosting provider, but I see that you are limited.  I also thought that my site being hosted on a clustered server might contribute, but I've never investigated or confirmed that.  Just thought I'd add more information.

Hi techsage - apologies for not updating you guys earlier, i completely forgot about my post. You're correct. I had my site in a dedicated app pool that was restricted to 64mb. Once i removed it from the dedicated app pool and moved to shared, where there is more memory available, the issue no longer occured.

Thanks,
Ernie