This question is locked. New answers and comments are not allowed.
Hi,
We are using Telerik Openaccess ORM Q2 2010 Evaluation version. We are using RIA services with Silverlight and have our connection setup with Oracle. Sometimes we get these errors and sometimes we don't. We are running on local machine. The errors are :-
1) Database has been disposed.
2) connection has already been closed.
I don't know why is this happening and why does it dispose my databases. Can you let us know what we are missing.
Thanks.
We are using Telerik Openaccess ORM Q2 2010 Evaluation version. We are using RIA services with Silverlight and have our connection setup with Oracle. Sometimes we get these errors and sometimes we don't. We are running on local machine. The errors are :-
1) Database has been disposed.
2) connection has already been closed.
I don't know why is this happening and why does it dispose my databases. Can you let us know what we are missing.
Thanks.
4 Answers, 1 is accepted
0
Himanshu
Top achievements
Rank 1
Rank 1
answered on 28 Feb 2011, 01:34 PM
We only face this problem when we make many async calls(about 10) at the same time.
0
Hello Himanshu,
Petar
the Telerik team
Is it possible that one of your operation is failing in a specific case and on fail it is disposing the context? Basically the underlying database instance should not be disposed unless all context associated with it are not disposed.
All the best,Petar
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!
0
Himanshu
Top achievements
Rank 1
Rank 1
answered on 02 Mar 2011, 06:13 AM
Hi Peter,
No, no operation is failing. It is a simple get operation i.e we are simply fetching the records from the database (no inserts, no updates, no deletes) . Morever it works sometimes and sometimes it doesn't. However the ratio when it is not working is quiet high. About 40% of the time it doesn't work. As a workaround we are making calls in synchronous manner. So, when the first operation's result are retrieved we make a second call and so on (loosing the benefits of aynchronous operation). This never happens with Entity Framework. But our client has asked us to use this product only. I've tried changing all the settings that are available in update model settings from changing timeouts to changing retry interval etc. But it simply doesn't work.
The rows in the tables are sometimes too high (as much as 40000). Can this be a problem for OpenAccess?
No, no operation is failing. It is a simple get operation i.e we are simply fetching the records from the database (no inserts, no updates, no deletes) . Morever it works sometimes and sometimes it doesn't. However the ratio when it is not working is quiet high. About 40% of the time it doesn't work. As a workaround we are making calls in synchronous manner. So, when the first operation's result are retrieved we make a second call and so on (loosing the benefits of aynchronous operation). This never happens with Entity Framework. But our client has asked us to use this product only. I've tried changing all the settings that are available in update model settings from changing timeouts to changing retry interval etc. But it simply doesn't work.
The rows in the tables are sometimes too high (as much as 40000). Can this be a problem for OpenAccess?
0
Hello Himanshu,
Petar
the Telerik team
Is it possible that you are using pessimistic locking and one of your reads is locking records that another read would attempt to obtain? This might easily lead to timeout.
The amount of data should not be a problem in this case.
Petar
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!