cant cache Objects that I read by ORM

[Sinan]

I have a list of object that I read them from database using ORM
when repeater try to read the cached copy of the an error occure saying , IObject scope already closed


Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Telerik.OpenAccess.Exceptions.InvalidOperationException: The 'IObjectScope' is already closed

Source Error:

Line 32: public string Title Line 33: { Line 34: get { return title; } Line 35: set { this.title = value; } Line 36: }

here is the code

  IObjectScope scope = ScopeUtility.GetScope();

            if (HttpContext.Current.Cache["regions"] != null)
                return (List<ProductRegion>)HttpContext.Current.Cache["regions"];

            List<ProductRegion> list = (from fn in scope.Extent<ProductRegion>() select fn).ToList();

            HttpContext.Current.Cache.Insert("regions", list.ToList());
            return list;

[Damyan Bogoev]

Hello Sinan ,

We would like to ask you for additional information regarding what the ScopeUtility.GetScope() method does? A possible problem could be if you are disposing the IObjectScope instance in this method.  We would suggest you to follow our guidelines on object scope management described in those two articles:
Best Practices in web development with OpenAccess Best Practices in web development with OpenAccess - Part Two
Hope you will find this information helpful.


Best wishes,
Damyan Bogoev
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Richard]

I know this is an old thread, but I am having the same error as stated by Sinan. When I cache and object in System.Web.HttpRuntime.Cache.
I am passing the scope down from our basepage.

[Alexander]

Hi Richard,

We found a problem in the Q1 2011 release which could lead to such behavior. I would suggest you to download the latest service pack (version 2011.1 411) which contains the fix for this issue.
If the problem remains, please let us know and provide the code that is causing the exception, so we can investigate further.

Greetings,
Alexander
the Telerik team